- Users - libvirt List Archives

Permission Denied error when I try to open the image file stored on the ZFS disk accessed through sshfs from another machine...
by marietto2008＠gmail.com 29 Nov '23

29 Nov '23

Hello to everyone. I would like to boot the FreeBSD 13.2 image file using Libvirt + virt-manager. I have stored the image on the external hard drive,"formatted" with ZFS while I'm using Devuan 5 installed on my ARM (32 bit) Chromebook,where I have access to the ZFS disk using sshfs using this command : sshfs -o Compression=no -o allow_root -o transform_symlinks -o password_stdin root@192.168.1.2:/mnt/zroot2/zroot2 /mnt/zroot2/zroot2 <<< 'pass' This is the error I get when I try to boot the image file using virt-manager : error : qemuProcessReportLogError:1990 : internal error: process exited while connecting to monitor: 2023-11-28T20:53:46.882586Z qemu-system-arm: -blockdev {"driver":"file","filename":"/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/FreeBSD-13.2-RELEASE-armv7.img': Permission denied According with this post : https://forum.manjaro.org/t/virt-manager-doesnt-work-permission-denied/1081… I tried to do the following : root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# getfacl /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ getfacl: Removing leading '/' from absolute path names # file: mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ # owner: root # group: root user::rwx group::rwx other::rwx root@devuan-bunsen:/mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm# setfacl -m user:libvirt-qemu:--x /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/ setfacl: /mnt/zroot2/zroot2/OS/Chromebook/FreeBSD-guestOS/freebsd-kvm/: Operation not supported Can someone help me to understand where the error is and how to fix it ? thanks.

3 4

Mentor moja global at CodePeak 2023!
by gautam.sharma＠iitg.ac.in 28 Nov '23

28 Nov '23

1 0

Enabling libiscsi with libvirt on Rocky 9
by will.gorman＠joyent.com 23 Nov '23

23 Nov '23

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

3 2

Enabling libiscsi with libvirt on Rocky 9
by Will Gorman 20 Nov '23

20 Nov '23

I am running into a problem attaching an iscsi disk to a VM in libvirt using "virsh attach-device" on Rocky 9 with the following error: "unable to execute QEMU command 'blockdev-add': Unknown driver 'iscsi'". I've found some indications that libiscsi is being removed from RHEL 9, like https://bugzilla.redhat.com/show_bug.cgi?id=1967133 but it's not clear to me what alternatives might be available for libvirt users that depend on the libiscsi-based block device driver. Are there alternate packages that can be installed to re-enable the iscsi block device driver for qemu on RHEL 9 based systems? Or would it be necessary to rebuild libvirt/qemu to get this block device driver to work again? Thanks, Will Gorman

1 0

Libvirt and Ceph: libvirtd tries to open random RBD images
by Jayanth Reddy 20 Nov '23

20 Nov '23

Hello Users, We're using libvirt with KVM and the orchestrator is Cloudstack. I raised the issue already at Cloudstack at https://github.com/apache/cloudstack/issues/8211 but appears to be at libvirtd. Below is our environment & issue description: It appears that one of our Cloudstack KVM clusters having 8 hosts is having the issue. We have HCI on these 8 hosts and there are approximately 700+ VMs running. But strange enough, there are these logs like below on hosts. Oct 25 13:38:11 hv-01 libvirtd[9464]: failed to open the RBD image '087bb114-448a-41d2-9f5d-6865b62eed15': No such file or directory Oct 25 20:35:22 hv-01 libvirtd[9464]: failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory Oct 26 09:48:33 hv-01 libvirtd[9464]: failed to open the RBD image 'a3fe82f8-afc9-4604-b55e-91b676514a18': No such file or directory Oct 26 10:38:17 hv-01 libvirtd[9464]: End of file while reading data: Input/output error We've got DNS servers on which there is an`A` record resolving to all the IPv4 Addresses of 8 monitors and there have not been any issues with the DNS resolution. But the issue of "failed to open the RBD image 'ccc1168a-5ffa-4b6d-a953-8e0ac788ebc5': No such file or directory" gets more weird because the VM that is making use of that RBD image lets say "087bb114-448a-41d2-9f5d-6865b62eed15" is running on altogether different host like "hv-06". On further inspection of that specific Virtual Machine, it has been running on that host "hv-06" for more than 4 months or so (looked at "Last updated" field). Fortunately, the Virtual Machine has no issues and has been running since then. Thanks, Jayanth

2 2

Problem setting up SGX domain
by Wojtek Porczyk 16 Nov '23

16 Nov '23

Hi, users@, I'm attempting to set up domain with SGX EPC memory. When starting it, I get this error: # virsh start astoria-test-1 error: Failed to start domain 'astoria-test-1' error: internal error: process exited while connecting to monitor: libnuma: Warning: /sys not mounted or invalid. Assuming one node: Permission denied 2023-11-16T14:04:26.919285Z qemu-system-x86_64: The nodes select no CPUs When removing <memory model='sgx-epc'> node from XML, the domain starts fine. I've attached is domain.xml for it, with the section commented. Also there are logs from happy and sad case. The libnuma error seems to stem from this place: https://github.com/numactl/numactl/blob/fc999282e6663d6844773e6065bbee3270f… This makes no sense to me, because the file is there and available: # sudo -u libvirt-qemu cat /sys/devices/system/node/node0/cpumap fff I also don't understand why qemu says "The nodes select no CPUs" (https://gitlab.com/qemu-project/qemu/-/blob/34a5cb6d8434303c170230644b2a7c1…) DDG has failed me in all cases. I've also tried to follow the recommendation from https://libvirt.org/formatdomaincaps.html#sgx-capabilities: For more details on the SGX feature, please follow resources in the SGX developer's document store. ...and the only think that I've found relevant to libvirt was this document: https://www.intel.com/content/www/us/en/developer/articles/technical/virtua… which suggests to play with <qemu:commandline> instead. host: Debian 12, libvirt 9.0.0, QEMU 7.2, virtinst 4.1 (see dpkg-l attachment) guest: Ubuntu 22.04 (jammy) cloud image The domain in quesion was defined using virt-install with cloud-init, then I was editing XML with `virsh edit`. Relevant snippet from `virsh domcapabilities`: <sgx supported='yes'> <flc>yes</flc> <sgx1>yes</sgx1> <sgx2>no</sgx2> <section_size unit='KiB'>95744</section_size> <sections> <section node='0' size='95744' unit='KiB'/> </sections> </sgx> System-wide logs do not contain anything relevant. I'm happy to provide additional info if needed. Anyone can point me to a solution? -- pozdrawiam / best regards Wojtek Porczyk Gramine / Invisible Things Lab I do not fear computers, I fear lack of them. -- Isaac Asimov

1 0

windows install fails with error 0x80070001
by daggs 09 Nov '23

09 Nov '23

Greetings, following an issue with my windows install, I've had to reinstall windows 11 on kvm. I start the vm and the install starts, the install process starts, I add the virtio scsi controller and the hdd gets detected. next I start the install and get the same error as see here: https://howfix.net/computer/0x80070001/ on when getting to the "Getting files ready for installation" stage. I suspect that there is a bug with the windows scsi virtio driver when using hdd pass-through this is the vm's xml: https://bpa.st/63RA my host system is based on qemu-8.1.2, libvirt-9.8.0, virtiofsd-1.8.0, virtio-win-0.1.229.1 and kernel-6.6.0. what can I do?

1 1

unsubscribe
by Miguel Ping 08 Nov '23

08 Nov '23

1 0

[FOSDEM] Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2024
by Piotr Kliczewski 08 Nov '23

08 Nov '23

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 Submit Your Proposal All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org

1 0

Passing through a YubiKey to a Windows VM for physical touch activation
by Michael Kjörling 06 Nov '23

06 Nov '23

I have a need to pass through a YubiKey to a Windows (10) VM guest such that Windows in the guest will let me use it with physical touch activation for 2FA. For those times, I am physically at the VM host, so I don't need _remote_ redirection into the guest, and I'm fine with plugging and unplugging the YubiKey physically on an as-needed basis. If I simply redirect the USB device through the virt-manager GUI, my experience is that it has at best worked very much unreliably, and often not at all. Searching the web hasn't helped. Does anyone have a recipe for that to work _reliably_? -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”

3 4

Clocks and Timers
by Simon Fairweather 05 Nov '23

05 Nov '23

Hi, If I have the following XML section does this imply that presence is default of on for rtc and pit? <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> Are there any other reference guides to best setup of timers apart from the XML document for different OS types? Regards Simon.

1 0

Re: hdd kills vm
by daggs 04 Nov '23

04 Nov '23

> Sent: Thursday, October 26, 2023 at 9:50 AM > From: "Martin Kletzander" <mkletzan(a)redhat.com> > To: "daggs" <daggs(a)gmx.com> > Cc: libvir-list(a)redhat.com > Subject: Re: hdd kills vm > > On Wed, Oct 25, 2023 at 03:06:55PM +0200, daggs wrote: > >> Sent: Tuesday, October 24, 2023 at 5:28 PM > >> From: "Martin Kletzander" <mkletzan(a)redhat.com> > >> To: "daggs" <daggs(a)gmx.com> > >> Cc: libvir-list(a)redhat.com > >> Subject: Re: hdd kills vm > >> > >> On Mon, Oct 23, 2023 at 04:59:08PM +0200, daggs wrote: > >> >Greetings Martin, > >> > > >> >> Sent: Sunday, October 22, 2023 at 12:37 PM > >> >> From: "Martin Kletzander" <mkletzan(a)redhat.com> > >> >> To: "daggs" <daggs(a)gmx.com> > >> >> Cc: libvir-list(a)redhat.com > >> >> Subject: Re: hdd kills vm > >> >> > >> >> On Fri, Oct 20, 2023 at 02:42:38PM +0200, daggs wrote: > >> >> >Greetings, > >> >> > > >> >> >I have a windows 11 vm running on my Gentoo using libvirt (9.8.0) + qemu (8.1.2), I'm passing almost all available resources to the vm > >> >> >(all 16 cpus, 31 out of 32 GB, nVidia gpu is pt), but the performance is not good, system lags, takes long time to boot. > >> >> > >> >> There are couple of things that stand out to me in your setup and I'll > >> >> assume the host has one NUMA node with 8 cores, each with 2 threads as, > >> >> just like you set it up in the guest XML. > >> >thats correct, see: > >> >$ lscpu | grep -i numa > >> >NUMA node(s): 1 > >> >NUMA node0 CPU(s): 0-15 > >> > > >> >however: > >> >$ dmesg | grep -i numa > >> >[ 0.003783] No NUMA configuration found > >> > > >> >can that be the reason? > >> > > >> > >> no, this is fine, 1 NUMA node is not a NUMA, technically, so that's > >> perfectly fine. > >thanks for clarifying it for me > > > >> > >> >> > >> >> * When you give the guest all the CPUs the host has there is nothing > >> >> left to run the host tasks. You might think that there "isn't > >> >> anything running", but there is, if only your init system, the kernel > >> >> and the QEMU which is emulating the guest. This is definitely one of > >> >> the bottlenecks. > >> >I've tried with 12 out of 16, same behavior. > >> > > >> >> > >> >> * The pinning of vCPUs to CPUs is half-suspicious. If you are trying to > >> >> make vCPU 0 and 1 be threads on the same core and on the host the > >> >> threads are represented as CPUs 0 and 8, then that's fine. If that is > >> >> just copy-pasted from somewhere, then it might not reflect the current > >> >> situation and can be source of many scheduling issues (even once the > >> >> above is dealt with). > >> >I found a site that does it for you, if it is wrong, can you point me to a place I can read about it? > >> > > >> > >> Just check what the topology is on the host and try to match it with the > >> guest one. If in doubt, then try it without the pinning. > >I can try to play with it, what I don't know is what should be the mapping logic? > > > > Threads on the same core in the guest should map to threads on the same > core in the host. Since there is no NUMA that should be enough to get > the best performance. But even misconfiguration of this will not > introduce lags in the system if it has 8 CPUs. So that's definitely not > the root cause of the main problem, it just might be suboptimal. > > >> > >> >> > >> >> * I also seem to recall that Windows had some issues with systems that > >> >> have too many cores. I'm not sure whether that was an issue with an > >> >> edition difference or just with some older versions, or if it just did > >> >> not show up in the task manager, but there was something that was > >> >> fixed by using either more sockets or cores in the topology. This is > >> >> probably not the issue for you though. > >> >> > >> >> >after trying a few ways to fix it, I've concluded that the issue might be related to the why the hdd is defined at the vm level. > >> >> >here is the xml: https://bpa.st/MYTA > >> >> >I assume that the hdd sits on the sata ctrl causing the issue but I'm not sure what is the proper way to fix it, any ideas? > >> >> > > >> >> > >> >> It looks like your disk is on SATA, but I don't see why that would be an > >> >> issue. Passing the block device to QEMU as VirtIO shouldn't cause that > >> >> much of a difference. Try measuring the speed of the disk on the host > >> >> and then in the VM maybe. Is that SSD or NVMe? I presume that's not > >> >> spinning rust, is it. > >> >as seen, I have 3 drives, 2 cdroms as sata and one hdd pt as virtio, I read somewhere that if the controller of the virtio > >> >device is sata, than it doesn't uses the virtio optimally. > >> > >> Well it _might_ be slightly more beneficial to use virtio-scsi or even > >> <disk type='block' device='lun'>, but I can't imagine that would make > >> the system lag. I'm not that familiar with the details. > >configure virtio-scsi and sata-scai at the same time? > > > > Yes, forgot that, sorry. Try virtio-scsi. You could also go farther > and pass through the LUN or the whole HBA (if you don't need to access > any other disk on it) to the VM. Try the information presented here: > > https://libvirt.org/formatdomain.html#usb-pci-scsi-devices > > >> > >> >it is a spindle, nvmes are too expensive where I live, frankly, I don't need lightning fast boot, the other BM machines running windows on spindle > >> >run it quite fast and they aren't half as fast as this server > >> > > >> > >> That might actually be related. The guest might think it is a different > >> type of disk and use completely suboptimal scheduling. This might > >> actually be solved by passing it as <disk device='lun'..., but at this > >> point I'm just guessing. > >I'll look into that, thanks. so bottom line, you suggest the following: 1. remove the manual cpu pin, let qemu sort that out. 2. add a virtio scsi controller and connect the os hdd to it 3. pass the hss via scsi pt and not dev node 4. if I able to do #3, no need to add device='lun' as it won't use the disk option Dagg.

2 9

ANNOUNCE: Mailing list move complete
by Daniel P. Berrangé 01 Nov '23

01 Nov '23

This is an announcement to the effect that the mailing list move is now complete. TL;DR the new list addresses are: * announce(a)lists.libvirt.org (formerly libvirt-announce(a)redhat.com) Low volume, announcements of releases and other important info * users(a)lists.libvirt.org (formerly libvirt-users(a)redhat.com) End user questions and discussions and collaboration * devel(a)lists.libvirt.org (formerly libvir-list(a)redhat.com) Patch submission for development of main project * security(a)lists.libvirt.org (formerly libvir-security(a)redhat.com) Submission of security sensitive bug reports The online archive and membership mgmt interface is https://lists.libvirt.org In my original announcement[1] I mentioned that people would need to manually re-subscribe. Due to a mixup in communications, our IT admins went ahead and migrated across the existing entire subscriber base for all lists. Thus there is NO need to re-subscribe to any of the lists. If you were doing filtering of mail, you may need to update filters for the new list ID matches. With the new list server, HyperKitty is providing the web interface. Thus if you wish to interact with the lists entire via the browser this is now possible. Note that it requires you to register for an account and set a password, even if you are already a list subscriber. If you mistakenly send to the old lists you should receive an auto-reply about the moved destinations. Note, we had some technical issues on Thursday/Friday, so if you sent mails on those two days they probably will not have reached any lists, and so you may wish to re-send them. With regards, Daniel [1] https://listman.redhat.com/archives/libvirt-announce/2023-October/000650.ht… -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

3 4

Activate storage during domain migration
by e-m＠mailbox.org 26 Oct '23

26 Oct '23

Hi, I have a block storage which I only want to be mounted on a single node. I know that there are many possibilities for shared storage usage but I want to know if the following is possible (using the API). - Have a domain running on node-A - Initialize a migration for that domain to node-B - Run a hook or something just before the domain starts on node-B to: - unmount storage on node-A - mount/prepare storage on node-B Thanks and best regards, Etienne

3 2

Libvirt
by Gk Gk 26 Oct '23

26 Oct '23

Hi All, I am trying to collect memory, disk and network stats for a VM on kvm host. It seems that the statistics are not matching what the OS inside the VM is reporting. Why is this discrepancy ? Is this a known bug of libvirt ? Also I heard that libvirt shows cumulative figures for these measures ever since the VM was created. Also I tested by creating a new vm and comparing the stats without a reboot . Even in this case, the stats dont agree. Can someone help me here please ? Thanks Kumar

2 5

help,virsh start vm failed
by 展荣臻（信泰） 26 Oct '23

26 Oct '23

Hello,all I start vm failed as show below: ()[root@com1 tmp]# virsh start centos error: Failed to start domain centos error: Start job for unit machine-qemu\x2d1\x2dcentos.scope failed with 'failed' as the same time error "2021-02-27 08:58:31.688+0000: 22: error : virSystemdCreateMachine:361 : Start job for unit machine-qemu\x2d4\x2dcentos.scope failed with 'failed' " in libvirt.log. How I dig into this question.thanks

1 0

Can't start vm with enc backing files, No secret with id 'sec0' ?
by 18781374080 26 Oct '23

26 Oct '23

Hey, guys I've been working on whether libvirt supports encrypted snapshots,Here are my versions of libvirt and qemu [root@xx ~]# libvirtd -V libvirtd (libvirt) 4.5.0 [root@xx ~]# qemu-img -V qemu-img version 2.12.0 (qemu-kvm-ev-2.12.0-33.1.el7_7.4) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers 1. assign $MYSECRET to libvirt secret using the secret-define and secret-set-value commands,and $MYSECRET is in base64 format MYSECRET=`printf %s "123456" | base64` 2. created a disk encrypted in luks format qemu-img create --object secret,id=sec0,data=$MYSECRET,format=base64 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 enc.qcow220G 3. The encrypted disk is defined in the XML configuration file, as shown below.Then I successfully started the virtual machine. <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/root/enc.qcow2'/> <backingStore/> <target dev='hda' bus='ide'/> <encryption format='luks'> <secret type='passphrase' uuid='694bdf38-214e-48d3-8c4c-9dbbcf0f5fa0'/> </encryption> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> 4. According to the qemu documentation, an encrypted snap.qcow2 disk was created with enc.qcow2 as backing qemu-img create -f qcow2 -F qcow2 --object secret,id=sec0,data=$MYSECRET,format=base64 --object secret,id=sec1,data=$MYSECRET,format=base64 -o encrypt.format=luks,encrypt.key-secret=sec1 -b 'json:{"encrypt.key-secret": "sec0", "driver": "qcow2", "file": {"driver": "file", "filename": "/root/enc/enc.qcow2"}}' snap.qcow2 I used the same $MYSECRET as the password data for the disk. Here is the disk information for snap.qcow2 image: snap.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 480K encrypted: yes cluster_size: 65536 backing file: json:{"encrypt.key-secret": "sec0", "driver": "qcow2", "file": {"driver": "file", "filename": "/root//enc.qcow2"}} backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 encrypt: ivgen alg: plain64 hash alg: sha256 cipher alg: aes-256 uuid: ab0e3f87-35e7-40cb-9888-9fe9bb54e981 format: luks cipher mode: xts slots: [0]: active: true iters: 115582 key offset: 4096 stripes: 4000 [1]: active: false key offset: 262144 [2]: active: false key offset: 520192 [3]: active: false key offset: 778240 [4]: active: false key offset: 1036288 [5]: active: false key offset: 1294336 [6]: active: false key offset: 1552384 [7]: active: false key offset: 1810432 payload offset: 2068480 master key iters: 30085 corrupt: false 5. Then I changed the configuration of the XML, as shown below.And re-define and start the virtual machine <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/root/snap.qcow2'/> <backingStore type='file'> <format type='qcow2'/> <source file='/root/enc.qcow2'/> <backingStore/> </backingStore> <target dev='hda' bus='ide'/> <encryption format='luks'> <secret type='passphrase' uuid='694bdf38-214e-48d3-8c4c-9dbbcf0f5fa0'/> </encryption> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> Then the startup failed and an error was thrown. As shown below. qemu-kvm: -drive file=/root/enc/vm/enc-snap.qcow2,encrypt.format=luks,encrypt.key-secret=ide0-0-0-luks-secret0,format=qcow2,if=none,id=drive-ide0-0-0: Could not open backing file: No secret with id 'sec0' The sec0 secret id could not be found in the backing file, this is my problem. Is there a problem with the way I implemented it, or does libvirt currently not support this? Any tips or help will be appreciated, Looking forward to your reply. Thank you | | 18781374080 | | 18781374080(a)163.com | 签名由网易邮箱大师定制

2 2

[libvirt-users] How can I rebase network disk?
by Boxiang Zhu 26 Oct '23

26 Oct '23

Hi. I am using openstack, ceph and libvirt now. The live volume migration will call the libvirt rebase function in openstack nova project. https://github.com/openstack/nova/blob/stable/rocky/nova/virt/libvirt/drive… https://github.com/openstack/nova/blob/stable/rocky/nova/virt/libvirt/guest… But I use the ceph as the openstack block backend. And the type of disk is network in xml. <disk type='network' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <auth username='cinder'> <secret type='ceph' uuid='86d3922a-b471-4dc1-bb89-b46ab7024e81'/> </auth> <source protocol='rbd' name='volumes002/volume-127f46fc-ef10-4462-af30-c3893cda31f9'> <host name='172.16.140.63' port='6789'/> </source> <target dev='vdb' bus='virtio'/> <serial>127f46fc-ef10-4462-af30-c3893cda31f9</serial> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> Now I found it is not supported to rebase network disk. It is only rebase block or file disk now. https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockRebase My question is that can I rebase network disk by some other ways from libvirt? Cheers, Boxiang

2 4

[libvirt-users] Does libvirt (will) support qemu's userspace vhost scsi and blk
by wuzhouhui 26 Oct '23

26 Oct '23

Does libvirt (will) support qemu's userspace vhost scsi and blk?

1 0

[libvirt-users] how xml generated
by 李卓瑶 26 Oct '23

26 Oct '23

hi : i create a domain by virt-manager tool, then there is a xxx.xml generated in /etc/libvirt/qemu/. so, my question is how the xx.xml generated? What the code involves in libvirt ? Thanks! -- Have a good day

3 6

[libvirt-users] How to convert "device_model_version = "qemu-xen-traditiona"" into libvirt xml file How to convert "device_model_version = "qemu-xen-traditiona"" into libvirt xml file
by hanyandong 26 Oct '23

26 Oct '23

I am using Xen-4.4.0, libvirt-1.2.9 My ubuntu.cfg is: ubuntu10.cfg bootloader = "/usr/local/lib/xen/boot/hvmloader" builder="hvm" memory = 512 name = "ubuntu" vif = [ "type=ioemu,bridge=ovsbr0", "type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0",,"type=ioemu,bridge=ovsbr0"] device_model_version = "qemu-xen-traditional" If I didnot add " device_model_version = "qemu-xen-traditional" " to ubuntu.cfg, I only can add four NICs to VM. If I add five or more,, I got these errors: libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 12 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited If I add " device_model_version = "qemu-xen-traditional" " to ubuntu.cfg, I can apply 8 NICs to VM. But, I want to create domU by virsh(libvirt), so How convert " device_model_version = "qemu-xen-traditional"" to xml file used by virsh? and How many NIC can a VM have? what leads to this limit？ -- Best Regards, yandong

1 0

ANNOUNCE: Forthcoming changes to libvirt mailing list hosting
by Daniel P. Berrangé 13 Oct '23

13 Oct '23

Hello Libvirt Community, For the last 18(!) years, libvirt community mailing lists have been kindly hosted by Red Hat Corporate IT on the redhat.com Mailman installation. In retrospect this wasn't the ideal home for community mailing lists but that decision is ancient history. Unfortunately as a consequence of infrastructure changes, the redhat.com Mailman service is scheduled to be decomissioned, and in the very near future ($low weeks) will cease to be able to send/receive mail for libvirt lists. As a result, all the libvirt mailing lists will need to move to a new Mailman installation, managed on our behalf by the Red Hat Open Source Community Infrastructure team[1], who provide services for a variety of OSS projects. It is intended that this new service will be dedicated for our community and thus located somewhere under the libvirt.org domain. It should go without saying that all existing mail archives will be migrated over to the new server. None of the historical record should be lost. It is not considered appropriate netiquette, however, to bulk-resubscribe all current list members under a new domain. Thus anyone who wants to remain on the community lists will soon be requested to take action to enroll on the new mailman service. The new service is not quite ready for use yet. This mail serves as a heads up that the changes will be coming in the next couple of weeks that will require action. A further announcement will be sent when the new mailman is ready to accept subscriptions, as well as warnings before the old lists stop accepting messages. With regards, Daniel [1] https://www.osci.io/ -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

1 0

Problem starting Windows 11 EE
by Rahul S 12 Oct '23

12 Oct '23

Hi, I configured a W11EE VM using virt-manager and joined it to my work domain. Everything was fine for a while. Later when I tried to reboot, I got the "Preparing Automatic Repair" message and when I selected "Startup Repair", I got the error "Startup repair couldn't repair your PC". I then went to command prompt, started 'diskpart' and ran "list disk" and got the error "there are no fixed disks to show". I have tried re-installing several times - it always ends up in this state. A few details of my system: host OS: OpenSUSE 15.5 libvirt version: 9.0.0-150500.4.3 virtio drivers: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-vi… Disk device type: virtio bitlocker is enabled in VM I am able to configure and use W11-professional without joining my work domain. The above problem isn't seen there. I booted the broken VM using my linux rescue disk image and examined the partition table. Everything seems to be proper. But windows isn't able to find the disk as I explained above. Can anybody provide any pointers for troubleshooting this ? Thanks, -Rahul

2 1

any advantage to using pool type glusterfs if no GFAPI
by W Kern 09 Oct '23

09 Oct '23

I have used fuse mounted gluster with 'dir' for years. Works great, aside from having to use the --unsafe flag on migrations. I am building up a new system and wondering if using the glusterfs type would be a better/safer choice. I'm not concerned about gfapi (host is U22LTS so I'm not even sure if it has it). I'm not concerned about the automount feature as that happens on start up anyway. I'm more interested if there is any technical or performance reasons to prefer 'glusterfs' pool type over 'dir' of course not having the --unsafe flag would be nice, but thats all scripted in anyway. -wk

2 2

Issue accidentally creating a '--type' defined pool
by Joshua Blake 04 Oct '23

04 Oct '23

Hello, I seem to have accidentally created a pool called "--type", but it doesn't appear in 'virsh pool-list'. See below. [root@vh01 /]# virsh pool-define-as --name --type dir --target /data/storage/ Pool --type defined [root@vh01 /]# virsh pool-list Name State Autostart ------------------------------ isos active yes jblake active yes [root@vh01 /]# virsh pool-destroy '--type' error: command 'pool-destroy' doesn't support option --type I can't also create a new "default" type because the directory exists for this defined '--type' [root@vh01 /]# virsh pool-define-as --name default --type dir --target /data/storage/ error: Failed to define pool default error: operation failed: Storage source conflict with pool: '--type' [root@vh01 /]# virsh pool-delete "--type" error: command 'pool-delete' doesn't support option --type Any help would be greatly appreciated.

3 3