August 2016 - Users - libvirt List Archives

[libvirt-users] ceph rbd pool and libvirt manageability (virt-install)
by Jelle de Jong 29 Aug '18

29 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I created a rbd pool and activated it, but I can't seem to create volumes in it with virsh or virt-install? # virsh pool-dumpxml myrbdpool <pool type='rbd'> <name>myrbdpool</name> <uuid>2d786f7a-2df3-4d79-ae60-1535bcf1c6b5</uuid> <capacity unit='bytes'>6997998301184</capacity> <allocation unit='bytes'>10309227031</allocation> <available unit='bytes'>6977204658176</available> <source> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> <name>libvirt-pool</name> <auth type='ceph' username='libvirt'> <secret uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> </source> </pool> # virt-install --version 1.0.1 # virsh --version 1.2.9 I ended using virsh edit ceph-test.powercraft.nl and making creating the disk manually. <disk type='network' device='disk'> <auth username='libvirt'> <secret type='ceph' uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> <source protocol='rbd' name='libvirt-pool/kvm01-storage'> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> </source> <target dev='vdc' bus='virtio'/> </disk> I use virt-install a lot to define, import and undefine domains, how can I use virt-install to manage my rdb disks? Kind regards, Jelle de Jong -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlV1xlQACgkQ1WclBW9j5HkbPQP+PjNrzvlqysslOp2Yk7wH4Mxy 2sh2dn96G0KOAHEeEn3BN6IWlnD1TADZbHdpTtMwkdv48Xwn0sP1s+3QDM4pb3gP n+z+dVxS8FouDIy/eiso3IBCj3g4TWbEX8ZHqs3jKqe0lZgAXBzB9xYSUowcEBrZ ddkPbr8p8ozWyOG+9V8= =lkK7 -----END PGP SIGNATURE-----

2 3

[libvirt-users] virRandomBits - not very random
by Brian Rak 01 Jun '18

01 Jun '18

I just ran into an issue where I had about 30 guests get duplicate mac addresses assigned. These were scattered across 30 different machines. Some debugging revealed that: 1) All the host machines were restarted within a couple seconds of each other 2) All the host machines had fairly similar libvirtd pids (within ~100 PIDs of each other) 3) Libvirt seeds the RNG using 'time(NULL) ^ getpid()' This perfectly explains why I saw so many duplicate mac addresses. Why is the RNG seed such a predictable value? Surely there has to be a better source of a random seed then the timestamp and the pid? The PID seems to me to be a very bad source of any randomness. I just ran a test across 60 of our hosts. 43 of them shared their PID with at least one other machine.

7 13

[libvirt-users] stream finish throws exception via python API
by Shahar Havivi 28 Nov '16

28 Nov '16

Hi, The following snippet works fine e.g. receiving the data but when calling stream.finish() we get the following error: stream = con.newStream() vol.download(stream, 0, 0, 0) buf = stream.recv(1024) stream.finish() libvirt: I/O Stream Utils error : internal error: I/O helper exited abnormally Traceback (most recent call last): File "./helpers/kvm2ovirt", line 149, in <module> download_volume(vol, item[1], diskno, disksitems, pksize) File "./helpers/kvm2ovirt", line 102, in download_volume stream.finish() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 5501, in finish if ret == -1: raise libvirtError ('virStreamFinish() failed') libvirt.libvirtError: internal error: I/O helper exited abnormally Am I doing something wrong? Thank you, Shahar.

5 12

[libvirt-users] systemctl libvirt-guests.service fails to start during host boot
by Benoit 27 Sep '16

27 Sep '16

Hi, I have been using qemu and kvm for a while but I am newbie to libvirt. (but I really like it :) I am on Parabola (fork of Archlinux, using systemd) I only got an issue regarding libvirt-guests service, when my host boots about 7 times to 10 I got a issue on the service. ------------------------------------------------------------------------ systemctl status libvirt-guests.service ● libvirt-guests.service - Suspend Active Libvirt Guests Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2016-08-11 10:55:35 CEST; 36s ago Docs: man:libvirtd(8) http://libvirt.org Process: 347 ExecStart=/usr/lib/libvirt/libvirt-guests.sh start (code=exited, status=1/FAILURE) Main PID: 347 (code=exited, status=1/FAILURE) Aug 11 10:55:35 oms_apex_plaisir systemd[1]: Starting Suspend Active Libvirt Guests... Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: Resuming guests on default URI... Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: Resuming guest : error: failed to connect to the hypervisor Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: error: no valid connection Aug 11 10:55:35 oms_apex_plaisir libvirt-guests.sh[347]: error: Failed to connect socket to '/var/run/libvirt/libvirt-sock' no such file Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Main process exited, code=exited, status=1/FAILURE Aug 11 10:55:35 oms_apex_plaisir systemd[1]: Failed to start Suspend Active Libvirt Guests. Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Unit entered failed state. Aug 11 10:55:35 oms_apex_plaisir systemd[1]: libvirt-guests.service: Failed with result 'exit-code'. ------------------------------------------------------------------------ it is like the service starts too early. When I restart the service everything is good and if I shutdown it sends the ACPI message correctly to my guests. I already seen lot of discussion but not able to find any working solution.. any idea to help me figure out the issue ? many thanks belette

2 5

[libvirt-users] Help With Nested Virtualization
by Brandon Golway 08 Sep '16

08 Sep '16

(Copied from my post on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?pid=1650650#p1650650) I have a FreeNAS 10 KVM setup via libvirt on my Arch server and I'd like to be able to test out the virtualization features in the nightly FreeNAS 10 builds but the problem is that I can't seem to get VT-x to correctly pass through to the guest. I have followed the [u][url= https://wiki.archlinux.org/index.php/KVM#Nested_virtualization]Nested Virtualization[/url][/u] section of the KVM wiki and I'm sure it's supported and enabled. Here's proof [code] [bran@nas ~]$ sudo systool -m kvm_intel -v | grep nested nested = "Y" [bran@nas ~]$ lscpu|grep Virtualization Virtualization: VT-x[/code] So the host/hardware isn't the problem, I believe the problem lies within libvirt. RedHat says to use [b]copy host CPU configuration[/b] or [b]host-passthrough[/b], with the latter being preferred. If I use the former I get the [b]CMT not supported[/b] error, but if I type in [b]host-passthrough[/b] which according to [u][url= https://bbs.archlinux.org/viewtopic.php?id=214539]this post[/url][/u] should work. When I set [b]host-passthrough[/b] it allows the system to boot up, but when I try to start a guest FreeNAS gives me the error that VT-x instructions aren't available, I have no idea how to check them either since the [b]proc[/b] pseudo-filesystem doesn't exist in BSD. I know for a fact that this isn't a problem with the FreeNAS builds because I've been testing them out for months on my Windows 10 desktop via VMware and nested virtualization works without issue, so it must be an issue with KVM/libvirt. Can someone clue me in on what the issue is? Here's the entire XML config for the FreeNAS VM [code] <domain type='kvm'> <name>FreeNAS_10</name> <uuid>ea816b85-7685-495a-bc97-28a882f190d7</uuid> <title>FreeNAS v10</title> <description>Nightly Alpha Test Releases</description> <memory unit='KiB'>6340608</memory> <currentMemory unit='KiB'>6340608</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.6'>hvm</type> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> <vmport state='off'/> </features> <cpu mode='host-passthrough'/> <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>restart</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/sbin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk1.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk2.img'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk3.img'/> <target dev='vdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='directsync' io='native'/> <source file='/var/lib/libvirt/images/FreeNAS_10.img'/> <target dev='vde' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hda' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' 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='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:24:5c:08'/> <source bridge='vmbridge'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <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='1'/> </redirdev> <redirdev bus='usb' type='spicevmc'> <address type='usb' bus='0' port='2'/> </redirdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </memballoon> </devices> </domain>[/code] Thanks, Brandon Golway

4 6

[libvirt-users] attaching storage pool error
by Johan Kragsterman 07 Sep '16

07 Sep '16

Hi! System centos7, system default libvirt version. I've succeeded to create an npiv storage pool, which I could start without problems. Though I couldn't attach it to the vm, it throwed errors when trying. I want to boot from it, so I need it working from start. I read one of Daniel Berrange's old(2010) blogs about attaching an iScsi pool, and draw my conclusions from that. Other documentation I haven't found. Someone can point me to a more recent documentation of this? Are there other mailing list in the libvirt/KVM communities that are more focused on storage? I'd like to know about these, if so, since I'm a storage guy, and fiddle around a lot with these things... There are quite a few things I'd like to know about, that I doubt this list cares about, or have knowledge about, like multipath devices/pools, virtio-scsi in combination with npiv-storagepool, etc. So anyone that can point me further....? Rgrds Johan

3 14

[libvirt-users] installing and accessing a VM? - newbie question maybe
by vrms＠netcologne.de 06 Sep '16

06 Sep '16

3 9

[libvirt-users] active commit not supported with this QEMU binary
by Ishmael Tsoaela 01 Sep '16

01 Sep '16

Hi All, I am creating snapshot and whilest running blockcommit I am coming acrross this error: virsh blockcommit Node-A vda --verbose --pivot error: unsupported configuration: active commit not supported with this QEMU binary Does anyone know what this could be and how to fix it, i tried compiling latest libvirt and latest qemu.. libvirtd -V libvirtd (libvirt) 2.1.0 kvm -version QEMU emulator version 2.6.93, Copyright

2 1

[libvirt-users] IDE vs SATA vs VirtIO
by William Kern 01 Sep '16

01 Sep '16

ok from googling its clear that VirtIO is consistently recommend for the best performance. However, with some legacy VMs that we are bringing into the system isn't an option. Is there a peformance difference between IDE and SATA? For that matter how much BETTER is VirtIO over the other two? Note, these are QCOW2 images if that makes a difference. -bill

1 0

[libvirt-users] couple of questions about virt-v2v
by cmc 01 Sep '16

01 Sep '16

Hi, I have two questions about virt-v2v that I hope someone could help with. 1. I have a host that I use to export VMs from VMWare to oVirt, as the RHEL 7 version of virt-v2v does not support W2012. When I run the conversion/export (-o ovirt -os ovirt-srv:/mnt/export) it looks for a bridge on the host I'm running the export for. What does it need the bridge on the local host for? 2. When I run a conversion of a W2012 host, it reports: "virt-v2v: warning: Neither rhev-apt.exe nor vmdp.exe can be found. Unable to install one of them. virt-v2v: warning: there is no QXL driver for this version of Windows (6.2 x86_64). virt-v2v looks for this driver in /usr/share/virtio-win" I can't find these two exe files. I've installed the ovirt-guest-tools-iso for FC23, and symlinked the mounted ISO to /usr/share/virtio-win, and though the two files it is looking for are not on that ISO, I thought it might help (it doesn't). Can virt-v2v install such drivers, or should this just be done manually from within the guest? Thanks, C

2 3

[libvirt-users] How to use virDomainOpenConsole
by Marina Danial 01 Sep '16

01 Sep '16

Hello, I have a quick question. Can anyone help with an example on how to use virDomainOpenConsole API in serial console access? Thanks Marina

2 1

[libvirt-users] Issue with virsh screenshot
by Tadas 31 Aug '16

31 Aug '16

Hello lists, I have strange issue while creating VM screenshots. virsh screenshot vmname produces ppm image. But when i try to make second screenshot, it produces the same image, even is VM screen has changed. Running screenshot on third time, it produces correct image. It looks like screenshot is producing last image every second time it is ran. OS debian stretch. virsh --version 2.0.0 qemu-system-x86_64 --version QEMU emulator version 2.6.0 (Debian 1:2.6+dfsg-3), Copyright (c) 2003- 2008 Fabrice Bellard

2 1

[libvirt-users] Use libvirt to create an NIC on the guest machine and connect to an existing TAP interface
by Marina Danial 31 Aug '16

31 Aug '16

Hello, I am facing the following issue. I have several TAP interfaces that are created by the following method on OpenVSwitch: *ovs-vsctl add-br br1* *sudo /usr/sbin/tunctl -t tap01 -p -u root* *sudo /sbin/ip link set tap01 up* *# Disable multicast* *sudo /sbin/ifconfig tap01 -multicast* *ovs-vsctl add-port br1 tap01* I need to launch a qemu VMs and have its NIC card that is created using libvirt to be connected to tap01 or other taps that are created with the above method. I need a way that libvirt only creates the new NIC on either eth0 or eht1 on the guest machine and connect it to tap01. Please help me in the best way to do so whether using the C++ APIs that libvirt provides or use the domain and/or network XMLs to achieve this. Thanks a lot Marina

2 1

[libvirt-users] virtfs / 9p - and "Permission denied" in guests
by lejeczek 31 Aug '16

31 Aug '16

hi all I wonder host is your virtfs passthrough working? I'm for the first time trying, a pretty regular setup: <filesystem type='mount' accessmode='passthrough'> <source dir='/__.aLocalStorages/2/__.home.usersSecondHome'/> <target dir='__.x.USERs.SECOND_HOME'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </filesystem> and guests mounts that mount tag, even lists the mountpoint's content, shows files & dirs but when tries to list a contets below, eg a subfolder of the mountpoint then it gets denied. would you have some suggestions how to troubleshoot it? many thanks, L

1 0

[libvirt-users] Fwd: Re: installing and accessing a VM? - newbie question maybe
by gunnar.wagner＠netcologne.de 30 Aug '16

30 Aug '16

3 3

[libvirt-users] Fwd: Re: installing and accessing a VM? - newbie question maybe
by gunnar.wagner＠netcologne.de 29 Aug '16

29 Aug '16

1 0

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

27 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 25 Aug '16

25 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 19 Aug '16

19 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 16 Aug '16

16 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 14 Aug '16

14 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 13 Aug '16

13 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