- Users - libvirt List Archives

Windows VM shutting down reason=crashed
by Jürgen Echter 27 Feb '24

27 Feb '24

Hello, i have a few Windows Server VM's running and one of them is randomly shutting itself down. In the log file i have the following line: 2024-02-26 06:53:13.286+0000: shutting down, reason=crashed What would be a good approach to figure out what the reason is? libvirt version 9.8.0 Gentoo linux with kernel 6.6.13 Thanks for some hints Juergen

2 1

add nvdimm and set it as a dax device
by Pierre Clouzet 14 Feb '24

14 Feb '24

Hello, I'm trying to add an nvdimm device on my vm and configure it to a dax mode. Directly with qemu, I was: sudo ndctl disable-namespace namespace0.0 sudo ndctl create-namespace -m devdax sudo daxctl reconfigure-device -m system-ram all --force However, when running with virt-manager, I get the following error message when I run sudo ndctl create-namespace -m devdax Error: create namespace: region0 align setting is 0x1000000 size 0x1dde0000 is misaligned. Here are the xml infos for the nvdimm device: <memory model="nvdimm" access="shared"> <source> <path>/mnt/scratch/pclouzet/libvirt/dax0.0</path> <alignsize unit="KiB">2048</alignsize> <pmem/> </source> <target> <size unit="KiB">488282</size> <node>0</node> <label> <size unit="KiB">128</size> </label> </target> <address type="dimm" slot="0"/> </memory> </devices> Is there an additional command I missed to set it as a dax device? Thanks, Pierre

1 1

qemu arguments
by Pierre Clouzet 06 Feb '24

06 Feb '24

Hello, I've recently tried libvirt api to manage virtual machine. The point of my work is to modify the topology of a virtual machine and test performances (add numa nodes, change number of cpu per numa, nvm devices, cxl, etc) As far as understand, when using virt-manager, qemu arguments stored in xml files can only be like the one that page: [ https://wiki.libvirt.org/QEMUSwitchToLibvirt.html | https://wiki.libvirt.org/QEMUSwitchToLibvirt.html ] But maybe I misundertood? For example, when I directly run qemu with arguments, I can add an arguments like this: qemu [...] -object memory-backend-ram,size=4G,id=ram0 -object memory-backend-ram,size=2G,id=ram1 -numa node,nodeid=0,memdev=ram0,cpus=0-3 -numa node,nodeid=1,memdev=ram1,cpus=4-7 To have 2 numa nodes with 4 cpus each. Is there an equivalent of -objet, -numa, -device; qemu arguments when using libvirt? Or arguments are restricted to the one described on wiki page? Thanks for you help, Have a good day, Pierre Clouzet

2 2

Migrating volumes to RBD/Ceph
by Julian Calaby 05 Feb '24

05 Feb '24

Hi, I have a fancy new Ceph cluster and have configured a storage pool using it in libvirt. I have a bunch of disk images in a "filesystem directory" storage pool. I want to migrate those disk images into the RBD pool. What is the process for doing this? I'm using libvirt from Debian Bookworm, version 9.0.0 and QEMU version 7.2. I have an XML file to define my new volume: <volume type='file'> <name>volume</name> <capacity unit='bytes'>8589934592</capacity> <allocation unit='bytes'>6747271168</allocation> <physical unit='bytes'>6747258880</physical> </volume> and I have tried: 1. virsh vol-create-from # virsh vol-create-from ceph volume.xml --inputpool default /var/lib/libvirt/images/volume.qcow2 error: Failed to create vol from volume.xml error: failed to open the RBD image 'volume.qcow2': No such file or directory No idea why it's trying to load "volume.qcow2" from within RBD when I've told it that it's in the default filesystem directory pool and provided a full path. 2. virsh blockcopy No idea how to actually achieve what I want here as it doesn't seem capable of copying to a non-file destination. 3. virsh vol-download and virsh vol-upload # mkfifo tmp # virsh vol-create --pool ceph volume.xml Vol volume created from volume.xml root@multimedia:~# virsh vol-list ceph Name Path ------------------------------------------ torrentbucket VM_images/volume root@multimedia:~# virsh vol-download --pool default volume.qcow2 tmp & [1] 2483977 root@multimedia:~# virsh vol-upload --pool ceph volume tmp error: cannot upload to volume volume error: this function is not supported by the connection driver: storage pool doesn't support volume upload I cannot believe that any sane virtual machine management solution does not have a way to achieve this, so clearly I'm missing something painfully obvious here. I've done a lot of searching for solutions and everything I've found either doesn't work for my specific case or is specifically for copying volumes within a pool or between files on a disk. Could someone please provide me with a working example of how to achieve this? Thanks, -- Julian Calaby Email: julian.calaby(a)gmail.com Profile: http://www.google.com/profiles/julian.calaby/

2 2

Host cpu model from "virsh capabilities" command not matching host physical model
by xtec＠trimaso.com.mx 26 Jan '24

26 Jan '24

The host cpu here is intel i5 1135g7 (this is a laptop). Using libvirt 9.0.0 Using "virsh capabilities" command, the //host/cpu/model part reads Broadwell-noTSX-IBRS But there are also the Skylake cpus available, which are newer than broadwell, and thus should better match an intel core 11th generation Why is libvirt outputting an "older processor"?

2 1

Libvirt permissions using facl instead of groups
by Stephen Lauck 26 Jan '24

26 Jan '24

Is there a way to use facl to specifically grant permission to all the files/dirs that libvirt needs instead of using groups? I am automating the install of libvirt and would like to be able to use it without sudo or having to logout/login. I have done a similar thing on a docker install using setfacl but was wondering if someone can point me to the specific kvm/libvirt places I need to grant and the privileges. Thank you for any help! -Stephen

2 1

Error when live migrating with volumes on NFS
by João Jandre 25 Jan '24

25 Jan '24

Hi, all I've been having an annoying issue with live VM + volume migration. When I try to use |virDomainMigrate2| to migrate a VM and some of its volumes (but not all) I get the following error: |unable to execute QEMU command 'block-export-add': Block node is read-only | Some additional context: * I originally found this issue using the java bindings, but I've been able to reproduce it using virsh; * I'm using Libvirt 8.0.0 and Qemu 6.2.0; * This only happens when the VM has volumes on NFS storage; * The issue does not happen when migrating all the volumes that are on NFS storage. Note that, if the VM has volumes that are on some other type of storage, such as ISCSI, those do not need to be migrated. However, migrating any volume will raise the error if the volumes on NFS are not migrated as well; * I've tried a number of valid combinations along the |VIR_MIGRATE_LIVE| flag, using the flags: |VIR_MIGRATE_PAUSED|, |VIR_MIGRATE_NON_SHARED_DISK|, |VIR_MIGRATE_NON_SHARED_INC|, |VIR_MIGRATE_UNSAFE|, |VIR_MIGRATE_COMPRESSED|. The easiest way I've found to reproduce this error was using the following steps: 1. Create a VM using virt-manager, it must have at least two volumes, at least one of them must be on NFS storage. Here's the XML of one of the VMs I've tested with: |<domain type='kvm' id='4'> <name>ubuntu22.04</name> <uuid>9965e409-c89d-408c-a9f7-488184566d56</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://ubuntu.com/ubuntu/22.04"/> </libosinfo:libosinfo> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <vmport state='off'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'/> <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='/mnt/nfs-storage/template.qcow2' index='1'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/nfs-storage/vol.qcow2' index='2'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x1b'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x1c'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x1d'/> <alias name='pci.14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c4:a7:6d'/> <source bridge='br-test'/> <target dev='vnet6'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/3'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-ubuntu22.04/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0' state='connected'/> <alias name='channel1'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='spice' port='5901' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <sound model='ich9'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </sound> <audio id='1' type='spice'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <redirdev bus='usb' type='spicevmc'> <alias name='redir0'/> <address type='usb' bus='0' port='2'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <alias name='redir1'/> <address type='usb' bus='0' port='3'/> </redirdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='rng0'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </rng> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+0</label> <imagelabel>+0:+0</imagelabel> </seclabel> </domain> | 2. Use |virsh migrate --domain <name> --copy-storage-all --live --desturi <other_host_uri> --xml ./newxml| to migrate the VM and one of its volumes, while leaving a volume that is on NFS without migration. I've tested migrating the volume to another NFS storage, as well as migrating to a ISCSI storage that is mounted on both hosts, the result is the same. Here's the content of the |newxml| for this example: |<domain type='kvm' id='4'> <name>ubuntu22.04</name> <uuid>9965e409-c89d-408c-a9f7-488184566d56</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://ubuntu.com/ubuntu/22.04"/> </libosinfo:libosinfo> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <vmport state='off'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'/> <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' cache='none'/> <source file='/mnt/nfs-storage/template1.qcow2' index='1'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/mnt/other-storage/vol.qcow2' index='2'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x1b'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x1c'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x1d'/> <alias name='pci.14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c4:a7:6d'/> <source bridge='br-test'/> <target dev='vnet6'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/3'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-ubuntu22.04/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0' state='connected'/> <alias name='channel1'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='spice' port='5901' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <sound model='ich9'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </sound> <audio id='1' type='spice'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <redirdev bus='usb' type='spicevmc'> <alias name='redir0'/> <address type='usb' bus='0' port='2'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <alias name='redir1'/> <address type='usb' bus='0' port='3'/> </redirdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='rng0'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </rng> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+0</label> <imagelabel>+0:+0</imagelabel> </seclabel> </domain> | Right after the command is sent, the |unable to execute QEMU command 'block-export-add': Block node is read-only| happens. If I do the same steps, but migrate all volumes that are on NFS (even if they stay on the same storage, only changing names), the error does not happen. Here are some other examples just to clarify when the error happens, examples with green headers do not present the error, while examples with red headers do: Volume Origin Destination ROOT iSCSI1 iSCSI2 DATA1 iSCSI1 --- DATA2 iSCSI1 --- Volume Origin Destination ROOT iSCSI1 --- DATA1 iSCSI1 iSCSI2 DATA2 iSCSI2 iSCSI1 Volume Origin Destination ROOT NFS1 NFS2 DATA1 NFS2 NFS1 DATA2 iSCSI1 --- Volume Origin Destination ROOT iSCSI1 NFS2 DATA1 NFS2 --- DATA2 NFS2 --- Volume Origin Destination ROOT iSCSI1 iSCSI1 DATA1 NFS1 --- DATA2 NFS1 --- Volume Origin Destination ROOT iSCSI1 --- DATA1 NFS2 NFS2 DATA2 NFS2 --- Has anyone experienced this before? If so, is there another workaround? As migrating all the volumes that are on NFS storage might be costly in terms of time and storage/network resources. Best regards, João Jandre.

2 1

Libvirt php api 0.5.8
by Simon Fairweather 22 Jan '24

22 Jan '24

I am looking to use libvirt_connect_get_domain_capabilities but 0.5.8 has not be released yet, any timeframe for this to be released? Regards Simon.

2 2

Install on Windows for use of Hyper-V driver
by Mateusz Loskot 06 Jan '24

06 Jan '24

Hi, TL;TR: Can I call libvirt API from Go or Python on Windows host using any pre-built binaries of required components? I'm trying to understand what I need to install on Windows host in order to use the Hyper-V driver [1] and call the API from Go or Python. The Windows page [2] says "The development headers are not currently provided in this installer, so this cannot be used for compiling new applications against libvirt." but it does not address development with Go or Python. The Go module [3] documentation says "Make sure to have libvirt-dev package (or the development files otherwise somewhere in your include path)" I'm not a stranger to C/C++ development, but this information is not quite helpful for Windows host environment. The Python bindings [4] documentation makes it clearer "requires the GCC and pkg-config tools, and development headers" and also clears remains of my hope which seems to be killed by this comment [5] on GitLab : "you likely won't be able to use libvirt with Python on Windows" which, I sense, can be extrapolated to Go bindings too. Is my understanding correct that Windows binaries [2] are for VM manager GUI only and any scripting or development using libvirt API is not supported on Windows? Hmm, how on earth the virt-manager itself paves its way to Windows then :-) [1] https://lists.libvirt.org/archives/list/users@lists.libvirt.org/thread/IHVI… [2] https://libvirt.org/windows.html [3] https://gitlab.com/libvirt/libvirt-go-module [4] https://pypi.org/project/libvirt-python/ [5] https://gitlab.com/libvirt/libvirt-python/-/issues/7#note_623686805 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

VM won't start from virt-manager -- Unable to open system.token
by John W. Himpel 03 Jan '24

03 Jan '24

I just updated libvirt to 9.10.0-3 and virt-manager to 4.1.0-4. Before the update, I could start my defined VMs from virt-manager without issue. Now I get the following: Error starting domain: can't connect to virtlogd. Unable to open system.token /run/libvirt/common/system.token: Permission denied I am running virt-manager from my unpriviledged userid. My userid is already a member of the libvirt group. I see no error messages in the journal or in any of the logs under /var/log Any suggestions would be greatly appreciated.

3 6