- Users - libvirt List Archives

Live backups create-snapshot-as and memspec
by David Wells 01 Mar '21

01 Mar '21

Hi all! I've been using libvirt for some time and until now I have treated backups of virtual computers as if they where physical computers installing the backup client on the guest. I am now however facing the need to backup a couple a couple of guest at the host level so I've been trying to catch up by reading, googling and by trial and error too. Up to now I've been able to backup a live machine whith a command like the following > virsh snapshot-create-as --domain test --name backup --atomic > --diskspec vda,snapshot=external --disk-only This command creates a file test.backup and in the meantime I can backup the original test.qcow2 but for what I saw this disk image is in a "dirty" state, as if the machine I could restore from this file had been turned off whithout a proper shutdown. I know that I can later restore the machine to its original state by issuing a command like this > virsh blockcommit --domain test vda --active --pivot > virsh snapshot-delete test --metadata backup I have seen that it is possible to create the snapshot using a memspec parameter which would make the backup of the guest as if it where in a clean state, however I haven't found the equivalent of the blockcommit for the memory file, in a sort of speak, to be able to restore the guest to it's original state. Thank you very much! Best regards. David Wells.

3 4

Upgrading the host
by Marcin Struzak 20 Feb '21

20 Feb '21

Hello-- I'm planning on upgrading the OS on my host machine by doing manual re-installation, which will trigger an upgrade of libvirt from 1.1.3 to 6.1.0. Hardware, storage volumes & paths, etc., will be the same after upgrade. I was going to redefine & start everything from .xml files, starting with the network virsh net-define <network XML> virsh net-autostart <network> virsh net-start <network> and following with all the guests virsh define <domain XML> virsh autostart <domain> virsh start <domain> I have the following questions: 1. Do I need to generate XML dumps manually, or is it ok to use the ones from host's /etc/libvirt? 2. Do I need to define & start storage pools & volumes explicitly, or will they be picked up from domain definitions? 3. Anything else I should worry about or prepare ahead? --Marcin

5 9

Static DHCP lease never distributed
by Brooks Swinnerton 11 Feb '21

11 Feb '21

Hi there, I have a libvirt network defined as so: <network> <name>customers</name> <bridge name='customers' macTableManager='libvirt' /> <port isolated='yes' /> <dns enable='no' /> <ip address='10.0.0.1' prefix='24'> <dhcp> <host mac='02:99:92:43:eb:b8' name='dhcp-test' ip='10.0.0.10' /> </dhcp> </ip> </network> And that network is attached to a virtual machine: <interface type='network'> <mac address='02:99:92:43:eb:b8'/> <source network='customers'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> But for some reason when the domain starts, it never gets an address. If I tcpdump the bridge that was created by the network I can see it sending out discover packets, but dnsmasq never seems to respond: 01:26:25.039987 02:99:92:43:eb:b8 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 02:99:92:43:eb:b8, length 300, xid 0xc7283f76, secs 228, Flags [none] Client-Ethernet-Address 02:99:92:43:eb:b8 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Client-ID Option 61, length 7: ether 02:99:92:43:eb:b8 MSZ Option 57, length 2: 576 Parameter-Request Option 55, length 7: Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname Domain-Name, BR, NTP Vendor-Class Option 60, length 3: "d-i" Despite that appearing to be the correct mac address. Looking in /var/lib/libvirt/dnsmasq/customers.hostsfile, it's returning what I would expect to be there: 02:99:92:43:eb:b8,10.0.0.10,dhcp-test If I add a <range> stanza to the configuration, that does appear to work, so it seems this is only related to static addresses. This is libvirtd 5.8.0.

2 1

Re: [ovirt-devel] Issue: Device path changed after adding disks to guest VM
by Nir Soffer 02 Feb '21

02 Feb '21

On Wed, Dec 2, 2020 at 4:57 PM Joy Li <joooy.li(a)gmail.com> wrote: > > Thanks a lot Nir! Good to know that oVirt cannot guarantee the disk names so that I don't need to spend more time trying to enable such a feature. > > I can always reproduce the problem via my application, basically, the procedure is as following: > > 1. create a VM Which guest OS? Can you share the guest disk image or ISO image used to instal it? > 2. add disks to the VM (e.g.: disk names: disk1, disk3) > 3. check the disk mappings via `virsh domblklist ` Please shared the libvirt domain xml (virsh dumpxml vm-name) > 4. add another disk (let's say, disk2, give a name alphabetically before some existing disks) Add disk while the vm is running (hotplug)? > 5. shutdown the VM via hypervisor and start it again (reboot won't work) What do you mean by "reboot does not work?" > 6. `virsh domblklist` again, then you might see the problem I mentioned before Mapping is different compared with state before the reboot? > There are no virtio devices inside /dev/disk/by-id/xxx of my guest VM. Maybe you don't have systemd-udev installed? The links in /dev/disk/... are created by udev during startup, and when detecting a new disk. > And I just noticed that the disks mapping information given by hypervisor (from VM configuration or virsh command) is different from the reality inside the VM. The disk name inside the VM was actually not changed. > > So now my issue is that given a disk name (/dev/vdb) of a VM, how can I get its wwid? Before I got it from the hypervisor, but now the hypervisor's information is not reliable, and since the disk is unformatted, I cannot use UUID. You can use: # udevadm info /dev/vda P: /devices/pci0000:00/0000:00:02.5/0000:06:00.0/virtio4/block/vda N: vda L: 0 S: disk/by-path/pci-0000:06:00.0 S: disk/by-id/virtio-b97e68b2-87ea-45ca-9 S: disk/by-path/virtio-pci-0000:06:00.0 E: DEVPATH=/devices/pci0000:00/0000:00:02.5/0000:06:00.0/virtio4/block/vda E: DEVNAME=/dev/vda E: DEVTYPE=disk E: MAJOR=252 E: MINOR=0 E: SUBSYSTEM=block E: USEC_INITIALIZED=10518442 E: ID_SERIAL=b97e68b2-87ea-45ca-9 E: ID_PATH=pci-0000:06:00.0 E: ID_PATH_TAG=pci-0000_06_00_0 E: DEVLINKS=/dev/disk/by-path/pci-0000:06:00.0 /dev/disk/by-id/virtio-b97e68b2-87ea-45ca-9 /dev/disk/by-path/virtio-pci-0000:06:00.0 E: TAGS=:systemd: I tried to reproduce you issue 4.4.5 development build: Starting vm with 2 direct LUN disks: # virsh -r dumpxml disk-mapping ... <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='native' discard='unmap'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5' index='3'> <seclabel model='dac' relabel='no'/> </source> <backingStore type='block' index='5'> <format type='qcow2'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/ad891316-b80a-4ab5-895b-400108bd0ca1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> </backingStore> <target dev='sda' bus='scsi'/> <serial>40018b33-2b11-4d10-82e4-604a5b135fb2</serial> <boot order='1'/> <alias name='ua-40018b33-2b11-4d10-82e4-604a5b135fb2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/3600140594af345ed76d42058f2b1a454' index='2'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <serial>b97e68b2-87ea-45ca-94fb-277d5b30baa2</serial> <alias name='ua-b97e68b2-87ea-45ca-94fb-277d5b30baa2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5' index='1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vdb' bus='virtio'/> <serial>d9a29187-f492-4a0d-aea2-7d5216c957d7</serial> <alias name='ua-d9a29187-f492-4a0d-aea2-7d5216c957d7'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </disk> ... # virsh -r domblklist disk-mapping Target Source --------------------------------------------------------------------------------------------------------------------------------------------------------------- sdc - sda /rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5 vda /dev/mapper/3600140594af345ed76d42058f2b1a454 vdb /dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5 In guest: # ls -lh /dev/disk/by-id/virtio-* lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-b97e68b2-87ea-45ca-9 -> ../../vda lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-d9a29187-f492-4a0d-a -> ../../vdb NOTE: "d9a29187-f492-4a0d-a" are the first characters of the disk id: "d9a29187-f492-4a0d-aea2-7d5216c957d7" seen in oVirt: https://my-engine/ovirt-engine/webadmin/?locale=en_US#disks-general;id=d9a2… Adding another disk in sorted in the middle (while the vm is running): # virsh -r dumpxml disk-mapping ... <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='native' discard='unmap'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5' index='3'> <seclabel model='dac' relabel='no'/> </source> <backingStore type='block' index='5'> <format type='qcow2'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/ad891316-b80a-4ab5-895b-400108bd0ca1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> </backingStore> <target dev='sda' bus='scsi'/> <serial>40018b33-2b11-4d10-82e4-604a5b135fb2</serial> <boot order='1'/> <alias name='ua-40018b33-2b11-4d10-82e4-604a5b135fb2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/3600140594af345ed76d42058f2b1a454' index='2'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <serial>b97e68b2-87ea-45ca-94fb-277d5b30baa2</serial> <alias name='ua-b97e68b2-87ea-45ca-94fb-277d5b30baa2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5' index='1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vdb' bus='virtio'/> <serial>d9a29187-f492-4a0d-aea2-7d5216c957d7</serial> <alias name='ua-d9a29187-f492-4a0d-aea2-7d5216c957d7'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/36001405b4d0c0b7544d47438b21296ef' index='7'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vdc' bus='virtio'/> <serial>e801c2e4-dc2e-4c53-b17b-bf6de99f16ed</serial> <alias name='ua-e801c2e4-dc2e-4c53-b17b-bf6de99f16ed'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </disk> ... # virsh -r domblklist disk-mapping Target Source --------------------------------------------------------------------------------------------------------------------------------------------------------------- sdc - sda /rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5 vda /dev/mapper/3600140594af345ed76d42058f2b1a454 vdb /dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5 vdc /dev/mapper/36001405b4d0c0b7544d47438b21296ef In the guest: # ls -lh /dev/disk/by-id/virtio-* lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-b97e68b2-87ea-45ca-9 -> ../../vda lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-d9a29187-f492-4a0d-a -> ../../vdb lrwxrwxrwx. 1 root root 9 Jan 6 09:51 /dev/disk/by-id/virtio-e801c2e4-dc2e-4c53-b -> ../../vdc Shutdown VM and start it again # virsh -r dumpxml disk-mapping ... <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='native' discard='unmap'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5' index='4'> <seclabel model='dac' relabel='no'/> </source> <backingStore type='block' index='6'> <format type='qcow2'/> <source dev='/rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/ad891316-b80a-4ab5-895b-400108bd0ca1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> </backingStore> <target dev='sda' bus='scsi'/> <serial>40018b33-2b11-4d10-82e4-604a5b135fb2</serial> <boot order='1'/> <alias name='ua-40018b33-2b11-4d10-82e4-604a5b135fb2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/3600140594af345ed76d42058f2b1a454' index='3'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <serial>b97e68b2-87ea-45ca-94fb-277d5b30baa2</serial> <alias name='ua-b97e68b2-87ea-45ca-94fb-277d5b30baa2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/36001405b4d0c0b7544d47438b21296ef' index='2'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vdb' bus='virtio'/> <serial>e801c2e4-dc2e-4c53-b17b-bf6de99f16ed</serial> <alias name='ua-e801c2e4-dc2e-4c53-b17b-bf6de99f16ed'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </disk> <disk type='block' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='native' iothread='1'/> <source dev='/dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5' index='1'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> <target dev='vdc' bus='virtio'/> <serial>d9a29187-f492-4a0d-aea2-7d5216c957d7</serial> <alias name='ua-d9a29187-f492-4a0d-aea2-7d5216c957d7'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </disk> ... # virsh -r domblklist disk-mapping Target Source --------------------------------------------------------------------------------------------------------------------------------------------------------------- sdc - sda /rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5 vda /dev/mapper/3600140594af345ed76d42058f2b1a454 vdb /dev/mapper/36001405b4d0c0b7544d47438b21296ef vdc /dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5 In the guest: # ls -lh /dev/disk/by-id/virtio-* lrwxrwxrwx. 1 root root 9 Jan 6 09:55 /dev/disk/by-id/virtio-b97e68b2-87ea-45ca-9 -> ../../vda lrwxrwxrwx. 1 root root 9 Jan 6 09:55 /dev/disk/by-id/virtio-d9a29187-f492-4a0d-a -> ../../vdb lrwxrwxrwx. 1 root root 9 Jan 6 09:55 /dev/disk/by-id/virtio-e801c2e4-dc2e-4c53-b -> ../../vdc Comparing to state before reboot: # virsh -r domblklist disk-mapping Target Source --------------------------------------------------------------------------------------------------------------------------------------------------------------- sdc - sda /rhev/data-center/mnt/blockSD/84dc4e3c-00fd-4263-84e8-fc246eeee6e9/images/40018b33-2b11-4d10-82e4-604a5b135fb2/40f455c4-8c92-4f8f-91c2-991b0ddfc2f5 vda /dev/mapper/3600140594af345ed76d42058f2b1a454 vdb /dev/mapper/360014050058f2f8a0474dc7a8a7cc6a5 vdc /dev/mapper/36001405b4d0c0b7544d47438b21296ef # ls -lh /dev/disk/by-id/virtio-* lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-b97e68b2-87ea-45ca-9 -> ../../vda lrwxrwxrwx. 1 root root 9 Jan 6 09:42 /dev/disk/by-id/virtio-d9a29187-f492-4a0d-a -> ../../vdb lrwxrwxrwx. 1 root root 9 Jan 6 09:51 /dev/disk/by-id/virtio-e801c2e4-dc2e-4c53-b -> ../../vdc In the guest disks are mapped to the same device name. It looks like libivrt domblklist is not correct - vdb and vdc are switched. Peter, this expected? Nir > > Joy > > On Wed, Dec 2, 2020 at 1:28 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> On Wed, Dec 2, 2020 at 10:27 AM Joy Li <joooy.li(a)gmail.com> wrote: >> > >> > Hi All, >> > >> > I'm facing the problem that after adding disks to guest VM, the device target path changed (My ovirt version is 4.3). For example: >> > >> > Before adding a disk: >> > >> > virsh # domblklist <vmname> >> > Target Source >> > --------------------------------------------------------- >> > hdc - >> > vda /dev/mapper/3600a09803830386546244a546d494f53 >> > vdb /dev/mapper/3600a09803830386546244a546d494f54 >> > vdc /dev/mapper/3600a09803830386546244a546d494f55 >> > vdd /dev/mapper/3600a09803830386546244a546d494f56 >> > vde /dev/mapper/3600a09803830386546244a546d494f57 >> > vdf /dev/mapper/3600a09803830386546244a546d494f58 >> > >> > After adding a disk, and then shutdown and start the VM: >> > >> > virsh # domblklist <vmname> >> > Target Source >> > --------------------------------------------------------- >> > hdc - >> > vda /dev/mapper/3600a09803830386546244a546d494f53 >> > vdb /dev/mapper/3600a09803830386546244a546d494f54 >> > vdc /dev/mapper/3600a09803830386546244a546d494f6c >> > vdd /dev/mapper/3600a09803830386546244a546d494f55 >> > vde /dev/mapper/3600a09803830386546244a546d494f56 >> > vdf /dev/mapper/3600a09803830386546244a546d494f57 >> > vdg /dev/mapper/3600a09803830386546244a546d494f58 >> > >> > The devices' multipath doesn't map to the same target path as before, so in my VM the /dev/vdc doesn't point to the old /dev/mapper/3600a09803830386546244a546d494f55 anymore. >> > >> > Anybody knows how can I make the device path mapping fixed without being changed after adding or removing disks. >> >> Device nodes are not stable, and oVirt cannot guarantee that you will >> get the same >> node in the guest in all runs. >> >> You should use /dev/disk/by-id/xxx links to located devices, and blkid to create >> fstab mounts that do not depend on node names. >> >> Regardless, oVirt try to keep devices stable as possible. Do you know >> how to reproduce >> this issue reliably? >> >> Nir >>

6 6

Fwd: virsh backup-begin problem
by Andrey Fokin 22 Jan '21

22 Jan '21

Ok. Sorry. On Thu, Jan 21, 2021 at 3:38 PM Peter Krempa <pkrempa(a)redhat.com> wrote: > On Thu, Jan 21, 2021 at 15:16:44 +0300, Andrey Fokin wrote: > > Yes, there is an error message. > > sudo virsh backup-begin lubuntu2 ./backup.xml > > error: XML document failed to validate against schema: Unable to validate > > doc against /usr/share/libvirt/schemas/domainbackup.rng > > Element domainbackup has extra content: disk > > As I've noted in the exact mail you are replying to, I will not offer > any further assistance unless you post the question also on > libvirt-users(a)redhat.com list as you did with your original question. > This is to archive any discussions for future reference. > > > On Thu, Jan 21, 2021 at 2:40 PM Peter Krempa <pkrempa(a)redhat.com> wrote: > > > > > On Thu, Jan 21, 2021 at 12:34:43 +0100, Peter Krempa wrote: > > > > On Thu, Jan 21, 2021 at 14:31:18 +0300, Andrey Fokin wrote: > > > > > Peter, thanks. I understood you message about additional > configuration > > > in > > > > > domen settings. It's really interesting, and I'll going to test it > as > > > well. > > > > > But could you please advise how change backup-begin command XML > > > parameters > > > > > file to start full backup process? What is wrong in my case and > how to > > > fix > > > > > it? My config below. > > > > > Thanks a lot! > > > > > <domainbackup> > > > > > <disk name='/var/lib/libvirt/images/lubuntu2.qcow2' > type='file'> > > > > > <target file='$PWD/scratch1.img'/> > > > > > <driver type='raw'/> > > > > > </disk> > > > > > <disk name='/var/lib/libvirt/images/lubuntu2-1.qcow2' > type='file'> > > > > > <target file='$PWD/scratch2.img'/> > > > > > <driver type='raw'/> > > > > > </disk> > > > > > </domainbackup> > > > > > > > > Could you please describe what the problem is? You are getting an > error? > > > > If so why didn't you paste it? > > > > > > > > I'm not going to setup a backup just to try your configuration. > Please > > > > provide all information you have and describe the problem as best as > > > > possible. > > Here: > > > > > > > Oh, and don't drop libvirt-users from the CC-list! That way my advice > > > would not be recorded in the mailing list archives and browsable by > > > others with a possibly same problem. > > > > > > Please Re-post your query to the list AND include any information you > > > have to get a reply from me. > > > > > > > > > > -- > > BRG, > > Andrey > > -- BRG, Andrey

2 5

virsh backup-begin problem
by Andrey Fokin 21 Jan '21

21 Jan '21

Colleagues, could you please advise what a problem could be in XML file in case of: virsh backup-begin lubuntu2 ./backup.xml where backup.xml - <domainbackup> <disk name='/var/lib/libvirt/images/lubuntu2.qcow2' type='file'> <target file='$PWD/scratch1.img'/> <driver type='raw'/> </disk> <disk name='/var/lib/libvirt/images/lubuntu2-1.qcow2' type='file'> <target file='$PWD/scratch2.img'/> <driver type='raw'/> </disk> </domainbackup> and domain config is- <domain type="kvm"> <name>lubuntu2</name> <uuid>c466086e-4570-4fb5-8cb6-bfe104791381</uuid> <memory unit="KiB">1048576</memory> <currentMemory unit="KiB">1048576</currentMemory> <vcpu placement="static">1</vcpu> <os> <type arch="x86_64" machine="pc-i440fx-focal">hvm</type> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <vmport state="off"/> </features> <cpu mode="host-model" check="partial"/> <clock offset="utc"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled="no"/> <suspend-to-disk enabled="no"/> </pm> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/lubuntu2.qcow2"/> <target dev="hda" bus="ide"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> <disk type="file" device="cdrom"> <driver name="qemu" type="raw"/> <target dev="hdb" bus="ide"/> <readonly/> <address type="drive" controller="0" bus="0" target="0" unit="1"/> </disk> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/lubuntu2-1.qcow2"/> <target dev="hdc" bus="ide"/> <address type="drive" controller="0" bus="1" target="0" unit="0"/> </disk> <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller> <controller type="usb" index="0" model="ich9-uhci1"> <master startport="0"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x0" multifunction="on"/> </controller> <controller type="usb" index="0" model="ich9-uhci2"> <master startport="2"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x1"/> </controller> <controller type="usb" index="0" model="ich9-uhci3"> <master startport="4"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x2"/> </controller> <controller type="pci" index="0" model="pci-root"/> <controller type="ide" index="0"> <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x1"/> </controller> <controller type="virtio-serial" index="0"> <address type="pci" domain="0x0000" bus="0x00" slot="0x06" function="0x0"/> </controller> <interface type="network"> <mac address="52:54:00:90:d7:29"/> <source network="default"/> <model type="e1000"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0"/> </interface> <serial type="pty"> <target type="isa-serial" port="0"> <model name="isa-serial"/> </target> </serial> <console type="pty"> <target type="serial" port="0"/> </console> <channel type="spicevmc"> <target type="virtio" name="com.redhat.spice.0"/> <address type="virtio-serial" controller="0" bus="0" port="1"/> </channel> <input type="tablet" bus="usb"> <address type="usb" bus="0" port="1"/> </input> <input type="mouse" bus="ps2"/> <input type="keyboard" bus="ps2"/> <graphics type="spice" autoport="yes"> <listen type="address"/> <image compression="off"/> </graphics> <sound model="ich6"> <address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0"/> </sound> <video> <model type="qxl" ram="65536" vram="65536" vgamem="16384" heads="1" primary="yes"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0"/> </video> <redirdev bus="usb" type="spicevmc"> <address type="usb" bus="0" port="2"/> </redirdev> <redirdev bus="usb" type="spicevmc"> <address type="usb" bus="0" port="3"/> </redirdev> <memballoon model="virtio"> <address type="pci" domain="0x0000" bus="0x00" slot="0x07" function="0x0"/> </memballoon> </devices> </domain> -- BRG, Andrey

2 3

How to enable libvirtd auth just like oVirt ?
by tommy 18 Jan '21

18 Jan '21

Hi everyone: In my libvirtd test env, there's no auth when using virsh: root@ubts2:~# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # virsh # virsh # list Id Name State -------------------------- 26 3.ohost1 running 27 3.ohost2 running 28 3.ohost3 running virsh # virsh # virsh # virsh # But, in oVirt env, there's auth when using virsh: [root@ohost1 ~]# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # virsh # virsh # virsh # virsh # list Please enter your authentication name: How can I enable auth in my libvirtd env just like oVirt ? Thanks.

2 1

I would like to contribute to libvirt
by PRAJWAL BENEDICT A 14 Jan '21

14 Jan '21

2 1

Get Host Capabilities failed: Internal JSON-RPC error: {'reason': 'internal error: Duplicate key'}
by tommy 13 Jan '21

13 Jan '21

Hi,everyone: I got this error in my ovirt env: VDSM ooengh1.tltd.com command Get Host Capabilities failed: Internal JSON-RPC error: {'reason': 'internal error: Duplicate key'} Systemctl message is: Dec 23 20:48:48 ooengh1.tltd.com vdsm[2431]: ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File "<string>", line 2, in getCapabilities File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in getCapabilities c = caps.get() File "/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 93, in get machinetype.compatible_cpu_models()) File "/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in __call__ value = self.func(*args) File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 142, in compatible_cpu_models all_models = domain_cpu_models(c, arch, cpu_mode) File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 97, in domain_cpu_models domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3844, in getDomainCapabilities if ret is None: raise libvirtError ('virConnectGetDomainCapabilities() failed', conn=self) libvirtError: internal error: Duplicate key AnyOne can help me ? Thanks!

2 4

[resent] virt-manager connection fails with 'qemu unexpectedly closed the monitor'
by John Paul Adrian Glaubitz 12 Jan '21

12 Jan '21

Hi! I recently ran into a problem when connecting to libvirtd 6.9.0 on Debian unstable and trying to import an existing image with Windows 7. Upon finishing the wizard and starting the instance, the import process fails with the following error message: Unable to complete install: 'internal error: qemu unexpectedly closed the monitor' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2081, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 731, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 679, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python3.8/site-packages/libvirt.py", line 4366, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor Since this error message is rather generic, I don't know where to start debugging. Does anyone know how to increase verbosity here to get an error message that might be more helpful? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz(a)debian.org `. `' Freie Universitaet Berlin - glaubitz(a)physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

2 4