- Users - libvirt List Archives

[libvirt-users] Lifecycle of a connection to libvirtd
by Vincent Bernat 26 Aug '16

26 Aug '16

Hey! I am trying to figure out how to reliably maintain a connection to libvirtd. From the documentation, I would expect something like that: - virConnectOpen() - virConnectRegisterCloseCallback() - virConnectSetKeepAlive() - Application logic And in the registered callback, I would: - virConnectUnregisterCloseCallback() - virConnectClose() - virConnectOpen() - virConnectRegisterCloseCallback() - virConnectSetKeepAlive() However, looking at the source code of virsh, I see that it additional stuff, notably: - virConnectIsAlive() - checking error codes of all calls to check if they are the result of a disconnect Are those steps needed? Randomly checking virConnectIsAlive() doesn't seem reliable. Checking individual error codes either (maybe I will miss one of them or misinterpret another one). virsh code uses those error codes to check if there is a disconnection: (((last_error->code == VIR_ERR_SYSTEM_ERROR) && (last_error->domain == VIR_FROM_REMOTE)) || (last_error->code == VIR_ERR_RPC) || (last_error->code == VIR_ERR_NO_CONNECT) || (last_error->code == VIR_ERR_INVALID_CONN)))) Any hint? -- Program defensively. - The Elements of Programming Style (Kernighan & Plauger)

2 3

Re: [libvirt-users] Attaching disks with external snapshots
by Erlon Cruz 24 Aug '16

24 Aug '16

Hi Han, Any update on this? Erlon On Wed, Aug 17, 2016 at 9:58 AM, Erlon Cruz <sombrafam(a)gmail.com> wrote: > Han, > > Did the same test again with libvirt debug enabled. This time I added the > disk[1] without snaps (OK), and then added the disk[2] with snapshots. The > libvirt log[3] (line 320) says: > > *Could not open > '/opt/stack/data/nova/mnt/a3b4c6ddd9bf82edd4f726872be58d05/volume-a75b42e8-8175-4516-b724-43ee6f3d2520': > Permission denied\r\n", "id": "libvirt-33"}]* > > But this file has 777 permissions. I can access it with any user I > tried[4]. Tough its mounted over NFS, the permissions seems to be right. > > Erlon > > [1] http://paste.openstack.org/show/556055/ > [2] http://paste.openstack.org/show/556056/ > [3] http://pastebin.com/CCFcKq5b > [4] http://paste.openstack.org/show/559018/ > > > On Tue, Aug 16, 2016 at 2:41 PM, Erlon Cruz <sombrafam(a)gmail.com> wrote: > >> Hi Han, >> >> Thanks for helping. What is the XML before the snapshot is created? Can >> you post the XML files you used too? The files are in the links pointed by >> the numbers [1], [2] etc. >> >> The versions are: >> qemu-system-x86_64 --version >> QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.4), Copyright >> (c) 2003-2008 Fabrice Bellard >> >> libvirtd --version >> libvirtd (libvirt) 1.3.1 >> >> >> >> Erlon >> >> On Mon, Aug 15, 2016 at 12:56 AM, Han Han <hhan(a)redhat.com> wrote: >> >>> Hi，Erlon >>> I was not able to reproduce your problem. It is ok to attach disk with >>> external snapshot. >>> I did it with following steps: >>> # qemu-img create /tmp/vdb 100M >>> Formatting '/tmp/vdb', fmt=raw size=104857600 >>> # virsh start snap >>> Domain snap started >>> # virsh snapshot-create-as snap s1 --disk-only --diskspec >>> vdb,file=/tmp/vdb.s1 --quiesce >>> Domain snapshot s1 created >>> # virsh dumpxml snap|awk '/<disk/,/<\/disk/' >>> <disk type='file' device='disk'> >>> <driver name='qemu' type='qcow2' cache='none'/> >>> <source file='/var/lib/libvirt/images/snap.s1'/> >>> <backingStore type='file' index='1'> >>> <format type='qcow2'/> >>> <source file='/var/lib/libvirt/images/snap.qcow2'/> >>> <backingStore/> >>> </backingStore> >>> <target dev='vda' bus='virtio'/> >>> <alias name='virtio-disk0'/> >>> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' >>> function='0x0'/> >>> </disk> >>> <disk type='file' device='disk'> >>> <driver name='qemu' type='qcow2'/> >>> <source file='/tmp/vdb.s1'/> >>> <backingStore type='file' index='1'> >>> <format type='raw'/> >>> <source file='/tmp/vdb'/> >>> <backingStore/> >>> </backingStore> >>> <target dev='vdb' bus='virtio'/> >>> <alias name='virtio-disk1'/> >>> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' >>> function='0x0'/> >>> </disk> >>> >>> Save the dumped vdb's xml to /tmp/vdb.xml >>> # virsh detach-device snap /tmp/vdb.xml >>> Device detached successfully >>> # virsh attach-device snap /tmp/vdb.xml >>> Device attached successfully >>> # virsh dumpxml snap|awk '/<disk/,/<\/disk/' >>> <disk type='file' device='disk'> >>> <driver name='qemu' type='qcow2' cache='none'/> >>> <source file='/var/lib/libvirt/images/snap.s1'/> >>> <backingStore type='file' index='1'> >>> <format type='qcow2'/> >>> <source file='/var/lib/libvirt/images/snap.qcow2'/> >>> <backingStore/> >>> </backingStore> >>> <target dev='vda' bus='virtio'/> >>> <alias name='virtio-disk0'/> >>> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' >>> function='0x0'/> >>> </disk> >>> <disk type='file' device='disk'> >>> <driver name='qemu' type='qcow2'/> >>> <source file='/tmp/vdb.s1'/> >>> <backingStore type='file' index='1'> >>> <format type='raw'/> >>> <source file='/tmp/vdb'/> >>> <backingStore/> >>> </backingStore> >>> <target dev='vdb' bus='virtio'/> >>> <alias name='virtio-disk1'/> >>> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' >>> function='0x0'/> >>> </disk> >>> >>> So I managed to attach disks with snapshot. >>> I want to know what is your libvirt and qemu-kvm version? >>> And can you provide your files: /tmp/disk.xml[1], >>> /tmp/snap-from-disk.xml[2], /tmp/disk-with-snap.xml[4], >>> /tmp/disk-with-snap.xml . I need more details. >>> >>> Han Han >>> >>> ----- Original Message ----- >>> From: "Erlon Cruz" <sombrafam(a)gmail.com> >>> To: libvirt-users(a)redhat.com >>> Sent: Friday, August 12, 2016 10:23:24 AM >>> Subject: [libvirt-users] Attaching disks with external snapshots >>> >>> Hi folks, >>> >>> I'm trying to to attach a disk to an instance using libvirt. The problem >>> is, this disk has external snapshots. The process tried was: >>> >>> 1 - Attach a disk in the domain: >>> virsh# attach-device instance-00000006 /tmp/disk.xml[1] --live >>> >>> 2 - Snapshot the disk[2]: >>> virsh# snapshot-create instance-00000006 --quiesce --xmlfile >>> /tmp/snap-from-disk.xml[2] --disk-only >>> >>> 3 - Dump the domain XML and create a new disk file from it: >>> virsh# dumpxml instance-00000006 >>> ... [3] >>> >>> 4 - Dettach the device and re-add it using the new disk file: >>> virsh# detach-device instance-00000006 /tmp/disk-with-snap.xml[4] >>> Device detached successfully >>> virsh# attach-device instance-00000006 /tmp/disk-with-snap.xml >>> error: Failed to attach device from /tmp/disk-with-snap.xml >>> error: internal error: unable to execute QEMU command 'device_add': >>> Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk1' >>> >>> Question, is this operation supported? If yes, how is the correct >>> procedure? >>> >>> Erlon >>> >>> >>> [1] http://paste.openstack.org/show/556055/ >>> [2] http://paste.openstack.org/show/556056/ >>> [3] http://paste.openstack.org/show/556063/ >>> [4] http://paste.openstack.org/show/556064/ >>> >>> _______________________________________________ >>> libvirt-users mailing list >>> libvirt-users(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/libvirt-users >>> >> >> >

2 3

[libvirt-users] qemu+ssh authentication
by Shahar Havivi 22 Aug '16

22 Aug '16

Hi, I try to login via the libvirt.openauth() API with qemu+tcp protocol and prompt for password, I am setting the username, password and the callback methdod with the following keys: auth = [[libvirt.VIR_CRED_AUTHNAME, libvirt.VIR_CRED_PASSPHRASE], request_cred, None] When I call openauth() method: conn = libvirt.openAuth('qemu+ssh://...', auth, 0) I am getting prompt for entriyng password. When using qemu+tcp it works fine. Thank you, Shahar.

2 1

[libvirt-users] libvirt-lxc capabilities mknod
by jsl6uy js16uy 18 Aug '16

18 Aug '16

Hello all, hope all is well Issue: Any way to give granular mknod capabilities to a container? Only allow creation of specific device? bit of background Have a laptop running arch and libvirt loading an arch lxc container created from lxc-create Overall container is up and running, I use it for vpn connections Initially it would not setup of the tun device. Previously using just the lxc tool set, I can edit the lxc.conf config file for the container and allow device creation of just the tun device. In libvirt I can add capabilities for mknod, but seems to be blanket for any device creation within the container? Is this correct? Thanks and Regards

2 2

[libvirt-users] Facing problems while connecting virsh to XenServer 6.5 to import VMs to RHEV / oVirt
by Anantha Raghava 18 Aug '16

18 Aug '16

Hi, I am trying to import couple of important Virtual Machines from XenServer 6.5 (from downloaded from xenserver.org) into RHEV / oVirt environment. When I used the RHEV / oVirt Import Wizard, I was facing the issues. In order to check further, I attempted to use virsh -c ssh://root@<xenhost> command to connect and check but received the same set of errors as in RHEV / oVirt Wizard. I am able to connect to xen server 6.5 using ssh command without password and even "sudo -u vdsm ssh root@<xenhost>" also works without any issues. To dig further I, on xen server, disabled the firewall and set SELinux to disabled and I am finding that libvirt is unable to connect to hypervisor. I have attached the libvirt client logs for your reference. Can someone help me to debug this and import the VMs from Xen Server 6.5 to RHEV / oVirt? We cannot recreate these Virtual Machines as these are critical ones and rebuilding will be a herculean task. Thanks in advance. -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees.

2 2

[libvirt-users] Python API does not return all information available
by David Ashley 15 Aug '16

15 Aug '16

All - The Python virDomain method info() does not return all the entries contained in the C struct virNodeInfo. While this is somewhat documented the entries that are returned are unlabeled and the documentation does not specify which VirNodeInfo entries they correspond to. Does anyone have more information they can pass on? Thanks, Davis Ashley

2 1

[libvirt-users] Definition /dev/shm prevent LXC container from start: "Failed to access '(null)': Bad address"
by mxs kolo 15 Aug '16

15 Aug '16

Hi all We use libvirt 1.2.x and 1.3.x with next filesystem definition in config: <filesystem type='ram' accessmode='passthrough'> <source usage='524288' units='KiB'/> <target dir='/dev/shm'/> </filesystem> But libvirt 2.1.0 with same config report error: Failed to access '(null)': Bad address Debug level 1 show: 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerMountAllFS:1618 : Mounting all non-root filesystems 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerMountAllFS:1625 : Mounting '(null)' -> '/dev/shm' 2016-08-11 10:14:56.661+0000: 1: error : lxcContainerResolveSymlinks:629 : Failed to access '(null)': Bad address 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 15 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 10 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 12 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerChild:2271 : Tearing down container Failure in libvirt_lxc startup: Failed to access '(null)': Bad address Someone use libvirt 2.x with /dev/shm device ? Probably need change config and add some definitions to /dev/shm ? b.r. Maxim Kozin

2 3

[libvirt-users] Guest Agent and API Relationship
by David Ashley 13 Aug '16

13 Aug '16

All - I have looked everywhere I can think of (except the C code) to see if I can find the relationship of an API to the guest agent. What I want to know is whether or not a given API has a dependency on the guest agent being available. I know that some of the APIs now have such a dependency but there does not seem to be an indicator in the documentation for when this is the case. Nor is there any comprehensive list of APIs that have a dependency on the guest agent. Any help would be useful. Thanks, W. David Ashley

2 1

[libvirt-users] Attaching disks with external snapshots
by Erlon Cruz 12 Aug '16

12 Aug '16

Hi folks, I'm trying to to attach a disk to an instance using libvirt. The problem is, this disk has external snapshots. The process tried was: 1 - Attach a disk in the domain: * virsh# attach-device instance-00000006 /tmp/disk.xml[1] --live* 2 - Snapshot the disk[2]: * virsh# snapshot-create instance-00000006 --quiesce --xmlfile /tmp/snap-from-disk.xml[2] --disk-only* 3 - Dump the domain XML and create a new disk file from it: *virsh# dumpxml instance-00000006* * ... [3]* 4 - Dettach the device and re-add it using the new disk file: * virsh# detach-device instance-00000006 /tmp/disk-with-snap.xml[4]* * Device detached successfully* * virsh# attach-device instance-00000006 /tmp/disk-with-snap.xml * * error: Failed to attach device from /tmp/disk-with-snap.xml* * error: internal error: unable to execute QEMU command 'device_add': Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk1'* Question, is this operation supported? If yes, how is the correct procedure? Erlon [1] http://paste.openstack.org/show/556055/ [2] http://paste.openstack.org/show/556056/ [3] http://paste.openstack.org/show/556063/ [4] http://paste.openstack.org/show/556064/

1 0

[libvirt-users] QEMU IMG vs Libvirt block commit
by Erlon Cruz 12 Aug '16

12 Aug '16

Hi folks, I'm having a issue in the standard NFS driver on OpenStack, that uses qemu-img and libvirt to create snapshots of volumes. It uses qemu-img in the Controller to manage the snapshots when the volume is not attached (offline) or calls the Compute (which calls libvirt) to manage snapshots if the volume is attached (online). When I try to create/delete snapshots from a snapshot chain. There are 3 situations: 1 - I create/delete the snapshots in Cinder (it uses qemu-img). It goes OK! I can delete and I can create snapshots. 2 - I create/delete the snapshots, in online mode (it uses libvirt). It goes Ok, as weel. 3 - I create the snapshots in Cinder (offline) and delete then in online mode (using libvirt), then it fails with this message[1]: libvirtError: invalid argument: could not find image 'volume-13cb83a2-880f-40e8-b60e-7e805eed76f9.d024731c-bdc3-4943-91c0-215a93ee2cf4' in chain for '/opt/stack/data/nova/mnt/a3b4c6ddd9bf82edd4f726872be58d05/volume-13cb83a2-880f-40e8-b60e-7e805eed76f9' But, in this folder, there the backing files are there[2] and they are chained as think it suppose to be[3]. The version for the 2 hosts in tests are: Controller/Cinder node: qemu-img version 2.0.0 && libvirt 1.2.2-0ubuntu13 Compute node: qemu-img version 2.5.0 && libvirt-1.3.1-1ubuntu10 Is there any compatibility problem between libvirt and qemu-img snapshots? Have you guys found any problem like that? Erlon ---------------------------------- [1] http://paste.openstack.org/show/543270/ [2] http://paste.openstack.org/show/543273/ [3] http://paste.openstack.org/show/543274/

1 2

[libvirt-users] Go bindings to LibVirt
by Sergey Bronnikov 11 Aug '16

11 Aug '16

Hi, everyone for a small project I need a Go bindings to LibVirt library. There is a page on the official site with a list of bindings to different languages [1], but it is lack of Go bindings. Does it mean there are no official bindings for that language? [1] https://libvirt.org/bindings.html Sergey

2 1

[libvirt-users] Sharing a host directory with a Windows guest
by Peter Steele 11 Aug '16

11 Aug '16

I'm running libvirt un a CentOS 7.2 host and have created a Windows 10 VM under that. I've been researching how to share a folder on my host with the Windows guest VM but can't figure out if it's possible. I've added the code <filesystem type='mount' accessmode='passthrough'> <driver type='path' wrpolicy='immediate'/> <source dir='var/lib/mydata`'/> <target dir='/mydata'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </filesystem> to the xml definition of my Windows VM but I assume something needs to be configured on the VM side as well. Is there a way to accomplish this? Peter

2 1

[libvirt-users] Proper XML for compareCPU method
by David Ashley 10 Aug '16

10 Aug '16

All - What is the proper XML to supply to the Python Connections compareCPU method? I have looked at the cpu_map.xml file and I believe I have the proper XML configured but the method always throws an exception with a missing CPU architecture error. Here is the code. from __future__ import print_function import sys import libvirt conn = libvirt.open('qemu:///system') if conn == None: print('Failed to open connection to qemu:///system', file=sys.stderr) exit(1) retc = conn.compareCPU('<cpu><arch name="x86"><model name="kvm64"/></arch></cpu>') if retc == -1: print("CPUs are not the same.") else: print("CPUs are the same.") conn.close() exit(0) This probably just a simple error on my part but I have tried more that a few permutations of the XML with no success. So I guess I need some help with this. Thanks, David Ashley

2 1

[libvirt-users] Cannot guestmount a Fedora 24 XFS disk.
by Andre Goree 09 Aug '16

09 Aug '16

I seem to be having trouble using guestmount to mount a Fedora 24 disk that is using XFS. This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these? /dev/sda1 (xfs) Verbose output shows: libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [03647ms] appliance is up libguestfs: send_to_daemon: 72 bytes: 00 00 00 44 | 20 00 f5 f5 | 00 00 00 04 | 00 00 00 4a | 00 00 00 00 | ... guestfsd: main_loop: new request, len 0x44 /dev/sda1: No such file or directory mount -o /dev/vda1 /sysroot/ [ 1.759120] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 1.762869] XFS (vda1): Version 5 superblock detected. This kernel has EXPERIMENTAL support enabled! [ 1.762869] Use of these features in this kernel is at your own risk! [ 1.764819] XFS (vda1): Superblock has unknown read-only compatible features (0x1) enabled. [ 1.765834] XFS (vda1): Attempted to mount read-only compatible filesystem read-write. [ 1.765834] Filesystem can only be safely mounted read only. [ 1.767472] XFS (vda1): SB validate failed with error 22. mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestfsd: error: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestfsd: main_loop: proc 74 (mount_options) took 0.09 seconds libguestfs: recv_from_daemon: 272 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 00 00 4a | 00 00 00 01 | 00 12 34 00 | ... libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so I've tried with both /dev/sda1 and /dev/vda1 but no luck. Interestingly enough, a CentOS 7.2 image with XFS and the same setup (i.e., a single partition formatted with XFS) mounts without issue. Any ideas? Andre Goree Senior Engineer, Atlantic.Net CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information. Any unauthorized disclosure or use without Atlantic.Net's express written consent is strictly prohibited. If you received this email in error, please notify the sender and delete this email from your system.

2 3

[libvirt-users] Mounting VM filesystem on host while VM running
by Patrick PICHON 08 Aug '16

08 Aug '16

Hello, All my VMs are using LVs created on the host side. I'm using collectd to monitor some of the ressources of my host as well as the libvirt pluging to monitor my VMs. Collectd has an interesting plugin ( df ) which can monitor the filesystem usage. I would like to use it to monitor the VMs filesytsem usage. As it is obvious that if I mount the VM filesystem on the host while the VM is running, I'm wondering if I could mount it in READONLY without expecting any panic/corruption problem. Any advices ? Patrick

4 8

[libvirt-users] Libvirt: dynamic ownership did not work
by Jonatan Schlag 05 Aug '16

05 Aug '16

Hi, I have a very strange problem with libvirt. I work on some machines with libvirt (Debian/ Arch Linux) and libvirt set the ownership of images file automatically to the qemu user / group for example on Arch Linux to nobody:kvm. So when I copy an image file with root and use I then with qemu, libvirt change the owner/ group to nobody:kvm. But I also compiled libvirt for a machine (gcc 4.9.4 glibc 2.12) and on this machine libvirt did not change the ownership of the image files which results in this error: libvirtError: internal error: process exited while connecting to monitor: able-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on 2016-08-03T18:19:47.494512Z qemu-system-x86_64: -drive file=/data/hdd1/libvirt/images/test.img,format=raw,if=none,id=drive-virtio-disk0: Could not open '/data/hdd1/libvirt/images/test.img': Permission denied When I set the ownership manually to nobody:kvm everything is fine, but I could not work out why libvirt is unable to set the ownership automatically. Can anybody give me a hint where I could search further to work out the problem? My libvirt version is 1.3.3.2 and the settings dynamic_ownership = 1 in /etc/libvirt/qemu.conf is set. I also created a bug report where I described the problem a little bit more detailed. https://bugzilla.redhat.com/show_bug.cgi?id=1363864 Thanks for every help. Regards Jonatan

3 9

[libvirt-users] NPIV storage pools do not map to same LUN units across hosts.
by Nitesh Konkar 04 Aug '16

04 Aug '16

Link: http://wiki.libvirt.org/page/NPIV_in_libvirt Topic: Virtual machine configuration change to use vHBA LUN There is a NPIV storage pool defined on two hosts and pool contains a total of 8 volumes, allocated from a storage device. Source: # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000366 unit:0:0:1 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000367 unit:0:0:2 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000368 unit:0:0:3 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000369 unit:0:0:4 /dev/disk/by-id/wwn-0x6005076802818bda300000000000036a unit:0:0:5 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000380 unit:0:0:6 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000381 unit:0:0:7 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000382 -------------------------------------------------------------------- Destination: -------------------------------------------------------------------- # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000380 unit:0:0:1 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000381 unit:0:0:2 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000382 unit:0:0:3 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000367 unit:0:0:4 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000368 unit:0:0:5 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000366 unit:0:0:6 /dev/disk/by-id/wwn-0x6005076802818bda300000000000036a unit:0:0:7 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000369 -------------------------------------------------------------------- As you can see in the above output,the same set of eight LUNs from the storage server have been mapped, but the order that the LUNs are probed on each host is different, resulting in different unit names on the two different hosts . If the the guest XMLs is referencing its storage by "unit" number then is it safe to migrate such guests because the "unit number" is assigned by the driver according to the specific way it probes the storage and hence when you migrate these guests , it results in different unit names on the destination hosts. Thus the migrated guest gets mapped to the wrong LUNs and is given the wrong disks. The problem is that the LUN numbers on the destination host and source host do not agree. Example, LUN 0 on source_host, for example, may be LUN 5 on destination_host. When the guest is given the wrong disk, it suffers a fatal I/O error. (This is manifested as fatal I/O errors since the guest has no idea that its disks just changed out under it.)The migration does not take into account that the unit numbers do match on on the source and destination sides. So, should libvirt make sure that the guest domains reference NPIV pool volumes by their globally-unique wwn instead of by "unit" numbers? The guest XML references its storage by "unit" number. Eg:- <disk type='volume' device='lun'> <driver name='qemu' type='raw' cache='none'/> <source pool='poolvhba0' volume='unit:0:0:0'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> I am planning to write a patch for it. Any comments on the above observation/approach would be appreciated. Thanks, Nitesh.

1 1

[libvirt-users] Error with OpenStack starting an instance
by Silvia Fichera 03 Aug '16

03 Aug '16

Hi all, I have installed OpenStack using devstack, when I try to launch an instance I have an error related to libvirt: libvirtError: Cannot get interface MTU on 'br-int' and this don't allow to create a VM. Any hint to solve it? Thanks -- Silvia Fichera

2 1

[libvirt-users] Assigning static ip address in libvirt
by harish.shastry＠gmail.com 03 Aug '16

03 Aug '16

Hello Is there way to assign static ip address to lxc and KVM guests with libvirt? I saw some snippets here https://libvirt.org/formatdomain.html#ipconfig but unable to get it to work. Regards Harish Regards Harish

2 1

[libvirt-users] Crash after connection close when callback is in progress
by Vincent Bernat 03 Aug '16

03 Aug '16

Hey! It seems that if I close a connection while a domain event callback is in progress, I can easily have a crash. Here is a backtrace: #v+ #0 virFree (ptrptr=0x0) at ../../../src/util/viralloc.c:582 save_errno = <optimized out> #1 0x00007fc8328a4ad2 in virObjectEventCallbackListPurgeMarked (cbList=0xadfc30) at ../../../src/conf/object_event.c:282 freecb = <optimized out> n = 0 #2 virObjectEventStateFlush (state=0xaf5380) at ../../../src/conf/object_event.c:819 tempQueue = { count = 0, events = 0x0 } #3 virObjectEventTimer (timer=<optimized out>, opaque=0xaf5380) at ../../../src/conf/object_event.c:560 state = 0xaf5380 #4 0x00007fc83280b7aa in virEventPollDispatchTimeouts () at ../../../src/util/vireventpoll.c:457 cb = 0x7fc8328a48d0 <virObjectEventTimer> timer = 1 opaque = 0xaf5380 now = 1470212691501 i = 0 ntimeouts = 1 #5 virEventPollRunOnce () at ../../../src/util/vireventpoll.c:653 fds = 0x7fc824000920 ret = <optimized out> timeout = <optimized out> nfds = 1 __func__ = "virEventPollRunOnce" __FUNCTION__ = "virEventPollRunOnce" #6 0x00007fc83280a141 in virEventRunDefaultImpl () at ../../../src/util/virevent.c:314 __func__ = "virEventRunDefaultImpl" #7 0x0000000000400b37 in loop (arg=0x0) at crash.c:8 __PRETTY_FUNCTION__ = "loop" #v- And the state of cbList: #v+ >>> print *cbList $2 = { nextID = 11419456, count = 1, callbacks = 0x0 } #v- I have another thread, but it is just sleeping when the crash happens. Here is the source code: #+begin_src c #include <stdio.h> #include <unistd.h> #include <assert.h> #include <pthread.h> #include <libvirt/libvirt.h> void* loop(void *arg) { while (1) { assert (virEventRunDefaultImpl() >= 0); } return NULL; } void callback(virConnectPtr conn, virDomainPtr dom, void *opaque) { // Do nothing. } void freecb(void *opaque) { // Do nothing. } int main() { assert(virInitialize() >= 0); assert(virEventRegisterDefaultImpl() >= 0); pthread_t event_loop; assert(pthread_create(&event_loop, NULL, loop, NULL) == 0); virConnectPtr conn = virConnectOpen("test:///default"); assert(conn != NULL); int cbid = virConnectDomainEventRegisterAny(conn, NULL, VIR_DOMAIN_EVENT_ID_LIFECYCLE, callback, NULL, freecb); assert(cbid != -1); virDomainPtr dom = virDomainDefineXML(conn, "<domain type=\"test\">" "<name>new VM</name>" "<memory unit=\"KiB\">8192</memory>" "<os><type>hvm</type> </os>" "</domain>"); assert(dom != NULL); assert(virDomainCreate(dom) != -1); virDomainFree(dom); assert(virConnectDomainEventDeregisterAny(conn, cbid) != -1); if (virConnectClose(conn) > 0 ) { printf("leak...\n"); } usleep(100000); return 0; } #+end_src Running this program in an infinite loop triggers the bug in less than 1 second (most of the time, just after displaying "leak..."). I am using libvirt 2.0.0 (in Debian). I have also file the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1363628 -- Write clearly - don't sacrifice clarity for "efficiency". - The Elements of Programming Style (Kernighan & Plauger)

1 0

[libvirt-users] systemd restarts libvirt
by Ishmael Tsoaela 02 Aug '16

02 Aug '16

Hi All, Can anyone please assist with this issue I am facing. There is continuous restart of libvirt, this causes virt-manager to disconnect. syslogs: systemd[1]: libvirt-bin.service: Start operation timed out. Terminating. systemd[1]: Failed to start Virtualization daemon. systemd[1]: libvirt-bin.service: Unit entered failed state. systemd[1]: libvirt-bin.service: Failed with result 'timeout'. systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. systemd[1]: Stopped Virtualization daemon. systemd[1]: Starting Virtualization daemon... dnsmasq[1296]: read /etc/hosts - 7 addresses libvirtd (libvirt) 1.3.4 QEMU emulator version 2.3.0 vir-manager 1.4.0

2 2

[libvirt-users] Some question about code of xenapi
by netcas 01 Aug '16

01 Aug '16

Hello, guys! I am doing some experiment to control XenServer with libvirt, when I define a domain, it always fails and gives the following message: error: Failed to define domain from /root/new.xml error: internal error: Couldn't get VM information from XML so I diving into the souce and found it always fails at network creating, and the code in libvirt-1.3.5\src\xenapi\xenapi_utils.c, line 437 is following: xen_vif_create(session, &vif, vif_record); if (!vif) { xen_vif_free(vif); xen_vif_record_free(vif_record); xen_network_record_free(net_rec); xen_network_set_free(net_set); return 0; } xen_vif_record_free(vif_record); xen_network_record_free(net_rec); ... ... return -1; should this if be if (vif) {...}, if the vif is null, why need to free it?

2 1

[libvirt-users] Live Disk Backup
by Prof. Dr. Michael Schefczyk 01 Aug '16

01 Aug '16

Dear All, using CentOS 7.2.1511, and libvirt from ovirt repositories (currently 1.2.17-13.el7_2.5, but without otherwise using ovirt) I am regularly backing up my VMs which are on qcow2 files. In general, I am trying to follow http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit A typical backup script would be #!/bin/bash dt=`date +%y%m%d` if virsh dominfo dockers10a | grep -q -E '^Status: *laufend|^State: *running' then virsh snapshot-create-as --domain dockers10a dockers10a --diskspec vda,file=/home/dockers10asnap.qcow2 --disk-only --no-metadata --atomic cp /kvm01/dockers10a.qcow2 /backup/dockers10a$dt.qcow2 virsh blockcommit dockers10a vda --active --verbose --pivot virsh snapshot-delete dockers10a dockers10a rm /home/dockers10asnap.qcow2 fi I am fully aware that the third line from the end "virsh snapshot-delete ..." will fail under regular circumstances. It is just there as a precaution to delete unnecessary snapshots should a previous backup have failed. For some time, I am noticing that from time to time backup fails in the way that the xml definition file of the VM backed up keeps the temporary file (in the example above /home/dockers10asnap.qcow2) as the source file. Then, at least upon rebooting the host, it will be unable to restart the VM. In addition, lots of other troubles can arise (following backups failing, storage issues). I am using a similar setup on four hosts. It seems that the better the resources of the host are, the lower the likelihood of the problem occurring - but that cannot be an acceptable state. Can someone please point me to how to avoid this? Regards, Michael Schefczyk

2 2

[libvirt-users] Network without forward mode
by Vincent Bernat 28 Jul '16

28 Jul '16

Hey! Another question. The documentation about networks say: ╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├───── │Inclusion of the forward element indicates that the virtual network is │to be connected to the physical LAN.Since 0.3.0. The mode attribute │determines the method of forwarding. If there is no forward element, the │network will be isolated from any other network (unless a guest │connected to that network is acting as a router, of course). ╰───── That's exactly what I want: just a vnet interface, no bridge, no routing, no forwarding. However, if I create a network with just that: #v+ <network> <name>public</name> <uuid>4629ba54-9e33-4a1f-9e45-78a1c8faaddc</uuid> </network> #v- libvirt (2.0.0) adds a bridge stanza: #v+ <network> <name>public</name> <uuid>4629ba54-9e33-4a1f-9e45-78a1c8faaddc</uuid> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:15:45:da'/> </network> #v- The bridge is created. If I spawn a VM attached to this network, it gets added to the bridge. Any way to have a network where absolutely no setup is done? Thanks! -- Use the "telephone test" for readability. - The Elements of Programming Style (Kernighan & Plauger)

3 6

[libvirt-users] Routing isolated network
by Erwin Straver 28 Jul '16

28 Jul '16

I want to create a network like this: Internet -- physical router -- host (network 192.168.178.x) -- virtual machine dmz -- eth0 (connected to pyshical router) -- eth1 (connect to isolated network 10.0.0.x) -- virtual machine www - eth0 (connect to isolated network 10.0.0.x) [image: network design] <http://i.stack.imgur.com/QoCz9.png> I have a virtual host which is conntected to my physical router with eth0 and ip4 address 192.168.178.100. I create a virtual machine dmz which connects 'direct' to my router via my physical device eth0 on the virtual host: <network connections='1'> <name>direct</name> <uuid>379d4687-445e-4bc6-8354-b555c7f18b15</uuid> <forward dev='eth0' mode='bridge'> <interface dev='eth0' connections='1'/> </forward> </network> On my virtual machine i create a second nic eth1 which is connected on a virtual network virbr-local: <network> <name>local</name> <uuid>d31b2e0d-810b-4ba0-8ac4-02bc53746142</uuid> <bridge name='virbr-local' stp='on' delay='0'/> <mac address='52:54:00:92:06:5c'/> <domain name='local.box'/> <dns> <forwarder addr='192.168.178.1'/> </dns> <ip address='10.0.0.1' netmask='255.0.0.0'> <dhcp> <range start='10.0.0.100' end='10.0.0.255'/> <host mac='52:54:00:51:31:86' ip='10.0.0.30'/> </dhcp> </ip> <route address='10.0.0.0' prefix='8' gateway='10.0.0.30'/> </network> Now I want to create a second virtual machine which connects to the internet through the virtual machine dmz on the virbr-local subnet. Is there a way to accomplish this kind of setup? My routing table on the virtual host looks likes this: Destination Gateway Genmask Flags Metric Ref Use Iface default fritz.box 0.0.0.0 UG 0 0 0 eth0 10.0.0.0 * 255.0.0.0 U 0 0 0 virbr-local 10.0.0.0 10.0.0.30 255.0.0.0 UG 1 0 0 virbr-local 192.168.178.0 * 255.255.255.0 U 0 0 0 eth0 But when I want to ping an address from the www virtual machine I get a unreachable network message. I setup a DNAT om the virtual machine dmz. But looking witch tcpdump on eht1 there's no traffic.I appreciate some help to setup the network. I clearly missing something. Get a signature like this: Click here! <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW…>

2 1