July 2021 - Users - libvirt List Archives

DAC & glusterFS - errors
by lejeczek 14 Jul '21

14 Jul '21

Hi guys I'm trying to spin up a VM whose image is on a GlusterFS vol, and I fail: -> $ virsh create /var/lib/pacemaker/conf.d/win10Pro.xml error: Failed to create domain from /var/lib/pacemaker/conf.d/win10Pro.xml error: failed to initialize gluster connection (src=0x7f0af807b410 priv=0x7f0af8090070): Invalid argument In logs: ... 2021-07-05 21:13:12.950+0000: 141524: warning : virSecurityDACSetOwnership:828 : Unable to restore label on 'win10Pro.qcow2'. XATTRs might have been left in inconsistent state. internal error: child reported (status=125): failed to initialize gluster connection (src=0x7f0b00097030 priv=0x7f0b000956c0): Invalid argument Any ideas & suggestions greatly appreciated. thanks, L.

5 5

virsh qemu-monitor-command block_resize not working
by arjen-libvirt＠gugu.be 14 Jul '21

14 Jul '21

Hi List, some version info: ]# /usr/libexec/qemu-kvm -version QEMU emulator version 4.2.0 (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers ]# virsh version Compiled against library: libvirt 6.0.0 Using library: libvirt 6.0.0 Using API: QEMU 6.0.0 Running hypervisor: QEMU 4.2.0 information about block devices for one specific guest: ]# virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp info block libvirt-2-format: /data/kvm/storage/diskimages01/uat-win201202_disk1_C.qcow2 (qcow2) Attached to: /machine/peripheral/virtio-disk0/virtio-backend Cache mode: writeback ide0-0-0: [not inserted] Attached to: ide0-0-0 Removable device: not locked, tray closed But then, when I want to resize the block device, I just cannot seem to find the correct device. I tried all of these: virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize libvirt-2-storage 48G Error: Cannot find device=libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-libvirt-2-storage 48G Error: Cannot find device=drive-libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize virtio-disk0 48G Error: Cannot find device=virtio-disk0 nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-virtio-disk0 48G Error: Cannot find device=drive-virtio-disk0 nor node_name= In a previous qemu version this worked (EL 7). Can someone help me out? Best regards, Arjen Van Drie, Antwerp

2 2

host identifier
by Jiatong Shen 05 Jul '21

05 Jul '21

Hello community, I am using OpenStack nova and realize that nova now uses host fqdn from libvirt as a uniq identifier for a compute node. The issue is that host might need to change its fqdn under some rare circumstances and lose some usage data due to the nova manages compute node resources. My question is: does libvirt already export host uuid identifier to other applications? I skim through the code base and find there is host uuid related code which reads /etc/machine-id to obtain a uniq uuid for migration, but seems this uuid cannot be obtained through virsh interface. Thank you for you help. -- Best Regards, Jiatong Shen

2 2