- Users - libvirt List Archives

[libvirt-users] Data format
by Anastasiya Ruzhanskaya 28 Apr '17

28 Apr '17

What is exactly the format of data being sent across remote connection ( from client to server with RPC protocol)? I see, there is XML but converted to string.

2 1

[libvirt-users] Tunnelled migrate Windows7 VMs halted
by Eric Blake 27 Apr '17

27 Apr '17

[moderator note: I'm forwarding a stripped down version of the original mail which was rejected in the moderator queue. I stripped the 3.3 megabyte .tar.bz2 of the log file attachment, which is inappropriate for a technical list. Either trim the log to the relevant portion, or host the log externally and have your list email merely give a URL of the externally-hosted file] > ForwardedMessage.eml > > Subject: > Tunnelled migrate Windows7 VMs halted > From: > 邓林文 <dlworld0(a)163.com> > Date: > 04/25/2017 11:12 PM > > To: > libvirt-users(a)redhat.com > > > > I migrated a Windows 7 VM with libvirtd tunnelled, the VM halted on the target although the status is running. > > > [root@test15 ~]# virsh migrate --live --p2p --tunnelled i-000000ac qemu+tcp://192.168.65.13/system > > > But when migrated with qemu native mode, the VM runs well. > > > [root@test15 ~]# virsh migrate --live --p2p i-000000ac qemu+tcp://192.168.65.13/system > > > System Info: > Release: Centos 7.2 > Kernel: 3.10.0-327.28.3.el7.x86_64 > Qemu: qemu-kvm-rhev-2.3.0 > Libvirt: libvirt-1.2.17/libvirt-2.0.0 > CPU: AMD Opteron(TM) Processor 6212 > > > As CPUFrequency may lead windows migrate halt, I have disabled Power Management. > > > Does anyone have some sugestions? > > > Thanks, > Linwen Deng > > > vm.xml > > > <domain type='kvm' id='8'> > <name>i-000000ac</name> > <uuid>53f0710f-b25e-4f47-a7cf-c15a9409fdc3</uuid> > <metadata> > <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0"> > <nova:package version="12.0.0-4"/> > <nova:name>c7-vm15-test15-7</nova:name> > <nova:creationTime>2017-04-14 06:48:54</nova:creationTime> > <nova:flavor name="oeflavor-4-2048-20"> > <nova:memory>2048</nova:memory> > <nova:disk>20</nova:disk> > <nova:swap>0</nova:swap> > <nova:ephemeral>0</nova:ephemeral> > <nova:vcpus>4</nova:vcpus> > </nova:flavor> > <nova:owner> > <nova:user uuid="b0f21b1d16b147ffb3f7713716cc894a">admin</nova:user> > <nova:project uuid="ae883f160c3c41db850d5cde8de8208b">service</nova:project> > </nova:owner> > </nova:instance> > </metadata> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <memoryBacking> > <hugepages> > <page size='2048' unit='KiB' nodeset='0'/> > </hugepages> > </memoryBacking> > <vcpu placement='static'>2</vcpu> > <cputune> > <shares>4096</shares> > <vcpupin vcpu='0' cpuset='4-7'/> > <vcpupin vcpu='1' cpuset='4-7'/> > <emulatorpin cpuset='4-7'/> > </cputune> > <resource> > <partition>/machine</partition> > </resource> > <sysinfo type='smbios'> > <system> > <entry name='manufacturer'>Fedora Project</entry> > <entry name='product'>OpenStack Nova</entry> > <entry name='version'>12.0.0-4</entry> > <entry name='serial'>95637afe-453f-42a8-b198-df673ab59c91</entry> > <entry name='uuid'>53f0710f-b25e-4f47-a7cf-c15a9409fdc3</entry> > <entry name='family'>Virtual Machine</entry> > </system> > </sysinfo> > <os> > <type arch='x86_64' machine='pc-i440fx-rhel7.2.0'>hvm</type> > <boot dev='cdrom'/> > <boot dev='hd'/> > <boot dev='fd'/> > <smbios mode='sysinfo'/> > </os> > <features> > <acpi/> > <apic/> > </features> > <cpu mode='host-model'> > <model fallback='allow'/> > <topology sockets='2' cores='1' threads='1'/> > </cpu> > <clock offset='utc'> > <timer name='pit' tickpolicy='delay'/> > <timer name='rtc' tickpolicy='catchup'/> > <timer name='hpet' present='no'/> > </clock> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>destroy</on_crash> > <devices> > <emulator>/usr/libexec/qemu-kvm</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='qcow2' cache='none'/> > <source file='/opt/ssd/win7.qcow2'/> > <backingStore type='file' index='1'> > <format type='raw'/> > <source file='/opt/ssd/_base/win7.qcow2'/> > <backingStore/> > </backingStore> > <target dev='vda' bus='virtio'/> > <serial>8164a82d-6066-46d7-8a92-8391620fc58c</serial> > <alias name='virtio-disk0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> > </disk> > <controller type='usb' index='0' model='ich9-ehci1'> > <alias name='usb'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x7'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci1'> > <alias name='usb'/> > <master startport='0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci2'> > <alias name='usb'/> > <master startport='2'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci3'> > <alias name='usb'/> > <master startport='4'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x2'/> > </controller> > <controller type='pci' index='0' model='pci-root'> > <alias name='pci.0'/> > </controller> > <controller type='virtio-serial' index='0'> > <alias name='virtio-serial0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> > </controller> > <serial type='file'> > <source path='/var/lib/nova/instances/53f0710f-b25e-4f47-a7cf-c15a9409fdc3/console.log'/> > <target port='0'/> > <alias name='serial0'/> > </serial> > <serial type='pty'> > <source path='/dev/pts/2'/> > <target port='1'/> > <alias name='serial1'/> > </serial> > <console type='file'> > <source path='/var/lib/nova/instances/53f0710f-b25e-4f47-a7cf-c15a9409fdc3/console.log'/> > <target type='serial' port='0'/> > <alias name='serial0'/> > </console> > <channel type='spicevmc'> > <target type='virtio' name='com.redhat.spice.0' state='connected'/> > <alias name='channel0'/> > <address type='virtio-serial' controller='0' bus='0' port='1'/> > </channel> > <input type='tablet' bus='usb'> > <alias name='input0'/> > </input> > <input type='mouse' bus='ps2'> > <alias name='input1'/> > </input> > <input type='keyboard' bus='ps2'> > <alias name='input2'/> > </input> > <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0' keymap='en-us'> > <listen type='address' address='0.0.0.0'/> > </graphics> > <graphics type='spice' port='5901' autoport='yes' listen='0.0.0.0' keymap='en-us'> > <listen type='address' address='0.0.0.0'/> > <image compression='auto_glz'/> > <streaming mode='filter'/> > <mouse mode='client'/> > </graphics> > <sound model='ich6'> > <alias name='sound0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> > </sound> > <video> > <model type='qxl' ram='65536' vram='65536' vgamem='16384' primary='yes'/> > <alias name='video0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> > </video> > <memballoon model='virtio'> > <stats period='10'/> > <alias name='balloon0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> > </memballoon> > </devices> > <seclabel type='none' model='none'/> > <seclabel type='dynamic' model='dac' relabel='yes'> > <label>+0:+107</label> > <imagelabel>+0:+107</imagelabel> > </seclabel> > </domain> > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org

3 3

[libvirt-users] Performance monotoring: Perf Event support
by Hui Jing 26 Apr '17

26 Apr '17

Hi everyone, I am using libvirt 2.5.0. I'd like to enable the "perf events" to monitoring my vm performance such as l3 cache. But it failed with "error: argument unsupported: unable to enable host cpu perf event for cmt". 1. Could you please give some hints on how to check if my host CPU supports cmt,mbm, is it displayed in /proc/cpuinfo? 2. Does the kernel version matters as well to support it? Thanks, Hui

2 1

[libvirt-users] External snapshot issue
by Leroy Tennison 24 Apr '17

24 Apr '17

I have used virsh snapshot-create-as <VM name> <snapshot name> "<snapshot description>" --diskspec "vda,snapshot=external,file=/path/to/external-snapshot" --disk-only --atomic to create an external snapshot of a running VM. I followed it with virsh blockpull <VM name> --path /path/to/external-snapshot and monitored it until done. I confirmed it with qemu-img info /path/to/external-snapshot which shows no backing store. However, when I do grep {/etc,/run}/libvirt/qemu/<VM name>.xml the xml for the VM still shows a backing store in the /run/... definition (but not in the /etc/... definition, my understanding is that the /etc/... definition won't be updated until the VM is shut down): <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/external-snapshot.qcow2'/> <backingStore type='file' index='1'> <format type='qcow2'/> <source file='/var/lib/libvirt/images/original-image-file.qcow'/> <backingStore/> </backingStore> <target dev='hda' bus='ide'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> This is using libvirtd version 1.3.1 and qemu-img version 2.5.0. How do I resolve this situation? I don't want to have to rely on a backing store permanently. Thanks for any help or pointers.

2 1

[libvirt-users] ZFS: creating a pool in a created zfs does not work, only when using the whole zfs-pool.
by Thies C. Arntzen 24 Apr '17

24 Apr '17

Hi, I’m new here so apologies if this has been answered before. I have a box that uses ZFS for everything (ubuntu 17.04) and I want to create a libvirt pool on that. My ZFS pool is named „big" So i do: > zfs create big/zpool > virsh pool-define-as --name zpool --source-name big/zpool --type zfs > virsh pool-start zpool > virsh pool-autostart zpool > virsh pool-list > virsh vol-create-as --pool zpool --name test1 --capacity 1G > virsh vol-list zpool Everything seems to work (no error message, vol-list shows the created volume, I can see the volume via zfs list -t all). -BUT- I cannot use that volume via virt-manager and after a short while it’s no longer listed via virsh vol-list zpool. The very same thing works as expected if I create a new zfs pool which I hand into libvirt. So instead of creating a pool from "big/zpool“ I create a pool names „somepool“ on a free device and -voila- everything works. Hope I did make myself clear? Best regards, thies

2 3

[libvirt-users] virt-manager, Network Manager and bridged networking
by Daniel Pocock 24 Apr '17

24 Apr '17

The wiki suggests that Network Manager doesn't support bridges[1] but I think that is out-of-date. Other documents like this[2] show how to set up bridges in Network Manager. For users wanting to run libvirt/KVM on their desktop system, can they now configure a bridge through Network Manager and then use it in virt-manager to create a guest without editing any of their configuration files by hand? Would it be possible for virsh or virt-manager to be enhanced to go one step further and automatically create bridges in Network Manager (using some API) on demand so the user doesn't have to do anything outside of virt-manager? Regards, Daniel 1. https://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging 2. http://ask.xmodulo.com/configure-linux-bridge-network-manager-ubuntu.html

2 1

[libvirt-users] External snapshot issue addendum
by Leroy Tennison 23 Apr '17

23 Apr '17

I made a mistake in my original post, --diskspec in snapshot-create-as should have shown "hda ...". I also just noticed that 'virsh edit <VM name>' has the correct information (no backing store, only the external snapshot file shown), I was under the impression that /run/... showed the current state, incorrect?

1 0

[libvirt-users] Proper way to remove a qemu-nbd-mounted volume usnig lvm
by Leroy Tennison 23 Apr '17

23 Apr '17

I either haven't searched for the right thing or the web doesn't contain the answer. I have used the following to mount an image and now I need to know the proper way to reverse the process. qemu-nbd -c /dev/nbd0 <qcow2 image using lvm> vgscan --cache (had to use --cache to get the qemu-nbd volume to be recognized, lvmetad is running) vgchange -ay lvdisplay mount <selected qemu-nbd related 'LV Path' found from lvdisplay above> <mount point> I have done the following: umount <mount point> lvchange -an <all qemu-nbd related 'LV Path's found from lvdisplay above> vgchange -an <qemu-nbd related volume> Now what? How do I get the volume out of the list so I can use 'qemu-nbd -d /dev/nbd0' to dis-associate the image with /dev/nbd0? vgreduce seems to be for volumes which have multiple underlying devices. I started to use vgremove but, when it started prompting for confirmation about removing logical volumes, I wasn't sure exactly what it was going to do and responded 'no'. If there is a web reference explaining this specific situation just point me to it - I'm not opposed to reading. Thanks for the help.

1 0

[libvirt-users] subscribe to domain start/stop/panic events
by Vasiliy Tolstov 22 Apr '17

22 Apr '17

Hi! How can i'm subscribe in my app to domain lifecycle messages? Does it possible to subscribe for all domains and not just one? -- Vasiliy Tolstov, e-mail: v.tolstov(a)selfip.ru

1 1

[libvirt-users] libvirtd segfault when using oVirt 4.1 with graphic console - CentOS7.3
by Rafał Wojciechowski 21 Apr '17

21 Apr '17

hello, I am getting such error: libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp 00007f4930711740 error 4 in libvirt.so.0.2000.0[7f4940678000+353000] when I am trying to start VM with graphic spice/vnc console - in headless mode(without graphic console) it is running I noticed this after update oVirt 4.0 to oVirt 4.1 however I noticed that also libvirtd and related packages were upgraded from 1.2.7 to 2.0.0: libvirt-daemon-kvm-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64 I am running up to date CentOS7.3 with 3.10.0-514.16.1.el7.x86_64 I have same issue with SELinux and without SELinux(checked after reboot with permissive mode) I tried to get information about this issue from oVirt team, but after mail conversation both me and oVirt team thinks that it might be issue in libvirtd in below link I am putting xmls generated by vdsm which are passing to the libvirtd to run the VMs first one is from vdsm log and second one is extracted from dump after segfault of libvirtd https://paste.fedoraproject.org/paste/eqpe8Byu2l-3SRdXc6LTLl5M1UNdIGYhyRLiv… Regards, Rafal Wojciechowski

2 4