- Users - libvirt List Archives

[libvirt-users] Block Commit: [100 %]error: failed to pivot job for disk vda
by Thomas Stein 14 Jan '15

14 Jan '15

Hello. I'm seeing this error while doing a backup of a VM. + virsh blockcommit kaltura vda --active --verbose --pivot Block Commit: [100 %]error: failed to pivot job for disk vda error: internal error: unable to execute QEMU command 'block-job-complete': The active block job for device 'drive-virtio-disk0' cannot be completed I'm on qemu 2.2.0 and libvirt-1.2.11. Does someone else see this error? Libvirt.log says: 2015-01-07 11:18:07.000+0000: 19355: warning : qemuDomainObjBeginJobInternal:1381 : Cannot start job (query, none) for domain kaltura; current job is (modify, none) owned by (19357, 0) 2015-01-07 11:18:07.000+0000: 19355: error : qemuDomainObjBeginJobInternal:1386 : Timed out during operation: cannot acquire state change lock 2015-01-07 11:18:35.556+0000: 19357: error : qemuMonitorJSONCheckError:381 : internal error: unable to execute QEMU command 'block-job-complete': The active block job for device 'drive-virtio-disk0' cannot be completed Any ideas? thanks and cheers t.

2 4

[libvirt-users] missing backend for pool type 5 (iscsi)
by Mathieu Bouillaguet 12 Jan '15

12 Jan '15

Hi, I try to define an iscsi pool with virsh but I always get the following error : error :internal error: missing backend for pool type 5 (iscsi) And yet libvirt was compiled with iscsi support : configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure: NetFS: yes configure: LVM: yes configure: iSCSI: yes configure: SCSI: yes configure: mpath: yes configure: Disk: yes configure: RBD: no configure: Sheepdog: no configure: Gluster: no configure: ZFS: no And virsh report that iscsi is supported : virsh -V Virsh command line tool of libvirt 1.2.11 See web site at http://libvirt.org/ Compiled with support for: Hyperviseurs : QEMU/KVM LXC UML OpenVZ VMWare VirtualBox ESX Test Réseau : Remote Network Bridging Interface udev Nwfilter VirtualPort Stockage : Dir Disk Filesystem SCSI Multipath iSCSI LVM Divers : Daemon Nodedev Secrets Debug Readline Modular Any idea what's going on ? thanks for your help

2 2

[libvirt-users] Libvirt to return the ip address instead of the hostname during migration
by Yagmur Akbulut 12 Jan '15

12 Jan '15

Hi all, We are working on nova live-migration using Ceph and trying to work around the problem where vm migration fails if name resolution is not enabled in a cluster. See the link, https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… We have managed to work around this by setting the flag to include “VIR_MIGRATE_TUNNELLED”. However, it is noticebaly slower than non tunnelled. We were hoping that setting the listen_addr would get libvirt to return the listen_addr rather than the hostname but virGetHostname in libvirt/src/util/virutil.c doesn’t have access to the config structure. I was wondering if libvirt can be patched in a way to return the ip address of the destination instead of the hostname during migration? Regards, Yagmur Akbulut

2 1

[libvirt-users] Using virsh blockcopy -- what's it supposed to accomplish?
by Gary R Hook 09 Jan '15

09 Jan '15

I am experimenting with the blockcopy command, and after figuring out how to integrate qemu-nbd, nbd-client and dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: What's the point? The "replication" disk file is not, from what I can ascertain, bootable. I expect this operation to create a pristine copy of my source qcow2 file (at a given point in time) which implies that I can swap that copy in and use it just like the original. Neither using --finish nor --pivot (both appear successful) give me a mirror that seems to serve any purpose. It seems especially pointless if I use --pivot because anything that happens after the pivot ends up lost if I don't actually have a usable qcow2 file. I find lots of discussion online about getting the steps to work, but as yet find nothing about using the resulting file. What am I missing here? libvirt (1.2.2) and qemu (2.2.0) as distributed with Ubuntu Trusty. -- Gary R Hook Senior Kernel Engineer NIMBOXX, Inc

3 7

Re: [libvirt-users] Using virsh blockcopy -- what's it supposed to accomplish?
by Gary R Hook 09 Jan '15

09 Jan '15

On 12/24/14 4:42 AM, Kashyap Chamarthy wrote: > On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote: > > [. . .] > > In my case, the block device is a QCOW2 disk image file. If I boot > without using the disk image file which has the operating system, the > domain will fail to boot, no? > > I see you're playing with NBD disks. I'll admit, I haven't played much > with QEMU NBD, will have to experiment post holidays. Back from the holidays, and back on this issue. I've learned a lot. I've learned how to use the blockcopy command to create a local copy in a simple disk file: virsh dumpxml my_domain > my_domain.xml virsh undefine my_domain virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait --verbose --finish virsh define my_domain.xml and the resulting copy in dsk.copy.qcow2 is, indeed, bootable. It appears to be a perfect copy, as I expect it to be. But while I see (per Kashyap's article, etc) that it can be useful in certain scenarios, it's not interesting to me. I would like to my copy to be off-system, and was hoping to use the NBD interface to accomplish that. So I tried this (a variant of the above), working on the same system because it's easier: qemu-img create -f qcow2 /tmp/dsk.test.qcow2 qemu-nbd -f qcow2 -p11112 /tmp/dsk.test.qcow2 nbd-client localhost 11112 /dev/nbd2 virsh dumpxml my_domain > my_domain.xml virsh undefine my_domain virsh blockcopy --domain my_domain --wait --verbose --finish virsh define my_domain.xml nbd-client -d /dev/nbd2 and the qemu-nbd process exits, as I wish. I presume at this point that the new file has integrity. I can take the qcow2 file that belongs to the domain and serve it up via NBD: qemu-nbd --partition=1 -p11112 /path/to/my/qcow2/file.qcow2 nbd-client localhost 11112 /dev/nbd2 mount /dev/nbd2 -oloop /mnt/foo and lo! in /mnt/foo I found my root filesytem. Seems perfectly reasonable. If, however, I try to use my generated-via-NBD file, I get this: # qemu-nbd --partition=1 -p11112 $PWD/dsk.test.qcow2 & [1] 7672 # qemu-nbd: Could not find partition 1: Invalid argument [1]+ Exit 1 qemu-nbd --partition=1 -p11112 $PWD/dsk.test.qcow2 # qemu-nbd --partition=0 -p11112 $PWD/dsk.test.qcow2 & [1] 7686 # qemu-nbd: Invalid partition 0 ^C [1]+ Exit 1 qemu-nbd --partition=0 -p11112 $PWD/dsk.test.qcow2 # qemu-nbd --partition=2 -p11112 $PWD/dsk.test.qcow2 & [1] 7699 # qemu-nbd: Could not find partition 2: Invalid argument ^C [1]+ Exit 1 qemu-nbd --partition=2 -p11112 $PWD/dsk.test.qcow2 # qemu-nbd --partition=3 -p11112 $PWD/dsk.test.qcow2 & [1] 7830 # qemu-nbd: Could not find partition 3: Invalid argument [1]+ Exit 1 qemu-nbd --partition=3 -p11112 $PWD/dsk.test.qcow2 I don't know what has been created, but it's not a copy of the original guest's disk. There's no partition there, it seems. So yes, blockcopy works fine under certain conditions. But the NBD layer seems to really muck things up. Or, more likely, I'm doing things wrong. I'm hoping someone can point out something obvious. There's a recent thread about "Block Replication for Continuous Checkpointing" that is heading towards using NBD. I fail to understand how this is ever going to work, based on my explorations. -- Gary R Hook Senior Kernel Engineer NIMBOXX, Inc

4 6

[libvirt-users] Private network for LXC
by Γιώργος Τσίρκας 08 Jan '15

08 Jan '15

Hello, i read about virtualization! It's very interesting,so i decided to find out more about it! I made my first linux container but i need some help about the creation of a private network with double nat! Thank you!

2 1

Re: [libvirt-users] Error starting domain: internal error: missing IFLA_VF_INFO in netlink response
by Hong-Hua.Yin＠freescale.com 08 Jan '15

08 Jan '15

Hi Laine, Sorry to disturb you. It seemed this issue had been fixed in libvirt-1.2.2/libnl-3.2.22/linux-3.12. But we still got the error on PowerPC platform. I'll appreciate if you could give any suggestion. We are not sure if any netlink implementation in kernel space is missed. The scenario is a little complicated. We installed internal PF and VF kernel modules and want to use <interface type="hostdev" managed="yes"> syntax to start a guest domain with MAC address. # insmod fslinic.ko max_vfs=2 Freescale 10 Gigabit PCI Express Network Driver fslinic 0000:01:00.0: Multiqueue Enabled: Rx Queue count = 1, Tx Queue count = 1 fslinic 0000:01:00.0: Freescale (R) 10 Gigabit Network Connection fslinic 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 1, Tx Queue count = 1 fslinic 0000:01:00.1: Freescale (R) 10 Gigabit Network Connection # insmod fslinicvf.ko Freescale 10 Gigabit PCI Express Network Driver # lspci -mk 00:00.0 "PCI bridge" "Freescale Semiconductor Inc" "Device 0440" -r20 "" "" 01:00.0 "Power PC" "Freescale Semiconductor Inc" "Device 0440" -r20 "" "" 01:00.1 "Power PC" "Freescale Semiconductor Inc" "Device 0440" -r20 "" "" 01:00.4 "Power PC" "Freescale Semiconductor Inc" "Device 0000" -r20 "" "" 01:00.5 "Power PC" "Freescale Semiconductor Inc" "Device 1957" -r20 "" "" 01:01.0 "Power PC" "Freescale Semiconductor Inc" "Device 0000" -r20 "" "" 01:01.1 "Power PC" "Freescale Semiconductor Inc" "Device 1957" -r20 "" "" 0001:00:00.0 "PCI bridge" "Freescale Semiconductor Inc" "Device 0440" -r20 "" "" 0002:00:00.0 "PCI bridge" "Freescale Semiconductor Inc" "Device 0440" -r20 "" "" # echo 1957 0000 > /sys/bus/pci/drivers/vfio-pci/new_id # echo 1957 1957 > /sys/bus/pci/drivers/vfio-pci/new_id # cat interface.xml <domain type='kvm'> <name>interface</name> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='ppc64' machine='ppce500'>hvm</type> <kernel>/dev/shm/uImage</kernel> <initrd>/dev/shm/ramdisk</initrd> <cmdline>root=/dev/ram rw console=ttyS0,115200</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-ppc64</emulator> <controller type='usb' index='0'/> <controller type='pci' index='0' model='pci-root'/> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <interface type="hostdev" managed="yes"> <mac address="00:e0:0c:00:20:01"/> <source> <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x04"/> </source> </interface> <memballoon model='virtio'/> </devices> </domain> root@t4240rdb:/var/volatile# virsh start interface error: Failed to start domain interface error: internal error: missing IFLA_VF_INFO in netlink response The debug message is as below: error : virNetClientProgramDispatchError:175 : internal error: missing IFLA_VF_INFO in netlink response Do you have any suggestion to investigate/debug this error? Wish you could reply. Thank you in advance. Best Regards, Olivia > -----Original Message----- > From: Yin Olivia-R63875 > Sent: Monday, November 24, 2014 7:37 PM > To: 'libvirt-users(a)redhat.com'; libvir-list(a)redhat.com > Subject: Error starting domain: internal error: missing IFLA_VF_INFO in netlink > response > > Hi, > > We try PCI Passthrough of host network devices on PPC platform. > http://wiki.libvirt.org/page/Networking#Assignment_with_.3Cinterface_type.3D > .27hostdev.27.3E_.28SRIOV_devices_only.29 > > But we got a similar issue as below that reported on RedHat before: > https://bugzilla.redhat.com/show_bug.cgi?id=1040626 > > With <hostdev>, it could start VM successfully. > <hostdev mode='subsystem' type='pci' managed='yes'> > <driver name='vfio'/> > <source> > <address domain='0x0000' bus='0x01' slot='0x00' function='0x4'/> > </source> > </hostdev> > > Logged into VM and checked for VF using lspci root@model : qemu ppce500:~# > lspci > 00:00.0 PCI bridge: Freescale Semiconductor Inc MPC8533E > 00:02.0 Power PC: Freescale Semiconductor Inc Device 0000 (rev 20) > 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon > > But it will fail if using <interface type="hostdev">: > <interface type="hostdev" managed="yes"> > <mac address="00:e0:0c:00:20:01"/> > <source> > <address type="pci" domain="0x0000" bus="0x01" slot="0x00" > function="0x4"/> > </source> > </interface> > > > # virsh create vf.xml > 2014-11-24 11:08:31.390+0000: 3556: info : libvirt version: 1.2.2 > 2014-11-24 11:08:31.390+0000: 3556: debug : virLogParseOutputs:1378 : > outputs=1:file:virsh.log > error: Failed to create domain from vf.xml > error: internal error: missing IFLA_VF_INFO in netlink response > > Exactly We're using max_vfs=2 and libnl-3.2.22 # ls -l /usr/lib64/libnl-3.so.200.17.0 > -rwxr-xr-x 1 root root 154440 Sep 17 07:15 /usr/lib64/libnl-3.so.200.17.0 > > > Why this issue happened on PPC? Is there anything architecture-specific support > needed to add? > > Thanks, > Olivia

1 0

[libvirt-users] Libvirt guest can't boot up when use ceph as storage backend with Selinux enabled
by Shanzhi Yu 08 Jan '15

08 Jan '15

Hi there, I met one problem that guest fail to boot up when Selinux is enabled with guest storage based on ceph. However, I can boot the guest with qemu directly. I also can boot it up with Selinux disabled. Not sure it is a libvirt bug or wrong use case. 1. Enable Selinux # getenforce && iptables -L Enforcing Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination 2. Define a guest with source file based on ceph # virsh define /dev/stdin <<EOF <domain type='kvm' id='13'> <name>ceph</name> <memory unit='KiB'>4048896</memory> <currentMemory unit='KiB'>4048576</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.1.0'>hvm</type> <boot dev='hd'/> </os> <features> </features> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='network' device='disk'> <driver name='qemu' type='raw' cache='none'/> <auth username='libvirt'> <secret type='ceph' usage='client.libvirt secret'/> </auth> <source protocol='rbd' name='libvirt-pool/rhel7-rbd.img'> <host name='10.66.xxx.xx' port='6789'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> </devices> </domain> EOF Domain ceph defined from /dev/stdin 3. Try to start the guest by virsh # virsh start ceph error: Failed to start domain ceph error: internal error: process exited while connecting to monitor: What I can see from libvirtd log is below: 2015-01-08 08:07:32.376+0000: 22552: warning : qemuDomainObjTaint:1890 : Domain id=19 name='ceph' uuid=e4412366-1f16-4c54-b121-dfb565672427 is tainted: high-privileges Detaching after fork from child process 23015. 2015-01-08 08:07:32.684+0000: 22552: error : qemuMonitorOpenUnix:309 : failed to connect to monitor socket: No such process 2015-01-08 08:07:32.684+0000: 22552: error : qemuProcessWaitForMonitor:2207 : internal error: process exited while connecting to monitor: 2015-01-08 08:07:32.684+0000: 22552: error : virDBusCall:1542 : error from service: TerminateMachine: No such file or directory 4. Start it by qemu cmd # cat /usr/local/var/log/libvirt/qemu/ceph.log 2015-01-08 08:08:12.179+0000: starting up LC_ALL=C PATH=/root/perl5/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name ceph -S -machine pc-i440fx-rhel7.1.0,accel=kvm,usb=off -m 3954 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e4412366-1f16-4c54-b121-dfb565672427 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/usr/local/var/lib/libvirt/qemu/ceph.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=rbd:libvirt-pool/rhel7-rbd.img:id=libvirt:key=AQAQLq5UwO8PMRAA5qftTrdfzXnFZdnunN1WeQ==:auth_supported=cephx\;none:mon_host=10.66.106.92\:6789,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2 -msg timestamp=on Domain id=20 is tainted: high-privileges 2015-01-08 08:08:12.473+0000: shutting down # /usr/libexec/qemu-kvm -name ceph -S -machine pc-i440fx-rhel7.1.0,accel=kvm,usb=off -m 3954 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 319cf458-8740-4d83-9317-e2d52025aa9e -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/usr/local/var/lib/libvirt/qemu/ceph.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=rbd:libvirt-pool/rhel7-rbd.img:id=libvirt:key=AQAQLq5UwO8PMRAA5qftTrdfzXnFZdnunN1WeQ==:auth_supported=cephx\;none:mon_host=10.66.106.92,if=none,id=drive-virtio-disk0,format=raw,cache=none # ps aux|grep qemu root 23075 2.5 0.2 5114492 16352 pts/5 Sl+ 16:09 0:00 /usr/libexec/qemu-kvm -name ceph -S -machine pc-i440fx-rhel7.1.0,accel=kvm,usb=off -m 3954 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 319cf458-8740-4d83-9317-e2d52025aa9e -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/usr/local/var/lib/libvirt/qemu/ceph.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=rbd:libvirt-pool/rhel7-rbd.img:id=libvirt:key=AQAQLq5UwO8PMRAA5qftTrdfzXnFZdnunN1WeQ==:auth_supported=cephx;none:mon_host=10.66.106.92,if=none,id=drive-virtio-disk0,format=raw,cache=none 5. Disable Selinux, start guest by virsh will succeed # setenforce 0 && virsh start ceph Domain ceph started # virsh list Id Name State ---------------------------------------------------- 21 ceph running # virsh dumpxml ceph|grep disk -A 10 .. <disk type='network' device='disk'> <driver name='qemu' type='raw' cache='none'/> <auth username='libvirt'> <secret type='ceph' usage='client.libvirt secret'/> </auth> <source protocol='rbd' name='libvirt-pool/rhel7-rbd.img'> <host name='10.66.xxx.xx' port='6789'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> .. I use latest libvirt build from git and # rpm -q librbd1 librados2 qemu-kvm-rhev librbd1-0.87-0.el7.x86_64 librados2-0.87-0.el7.x86_64 qemu-kvm-rhev-2.1.2-17.el7.x86_64 -- Regards shyu

1 0

[libvirt-users] trying to get "pages" output in virsh capabilities
by Chris Friesen 07 Jan '15

07 Jan '15

When running "virsh capabilities" one of my systems shows a couple entries for "pages" under host/cpu. (One for 4KB, one for 2MB.) On my other system I'm missing the "pages" entries. Is there something that I need to configure, or is this a libvirt version issue, or what? The system with the "pages" entries is running 1.2.9, while the system without them is running 1.2.2. Thanks, Chris

2 1

[libvirt-users] libvirt bridges rhel7
by Derek Yarnell 07 Jan '15

07 Jan '15

Hi, In RHEL5/6 we have been able to create bridges on our hyper-visor of a number of vlans (eg. em1 -> em1.483 -> br483) We would be able to see this br483 in the virt-manager drop down network choice at the end of creating a new host. On RHEL7 we are not using NetworkManager per the documentation[0] for bridges (and because it is not worth it). So a RHEL7 virt-manager (0.10.0) when connected to a libvirtd for RHEL6 (0.10.2) shows the bridge but when connected to a libvirtd for RHEL7 (1.1.1) it does not. So it isn't a virt-manager problem as it seems to be a difference in the backend libvirtd. You are able to manually specify the bridge device and it does work though. The `iface-dumpxml br483` command in virsh on RHEL6 and RHEL7 both are identical. I guess the question how does a libvirt client like virt-manager determine a iface is a usable bridge? [0] - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht… Thanks, derek -- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies

1 0