- Users - libvirt List Archives

[libvirt-users] Question about disabling '3dnowprefetch' CPU feature in Xen Guest using libvirt
by Charles Shih 06 Jul '17

06 Jul '17

Dear All, I'm reaching this mail-list to ask a small question about disabling '3dnowprefetch' CPU feature in Xen Guest using libvirt. This is my environment: Fedora release 26 (Twenty Six) 4.11.0-0.rc3.git0.2.fc26.x86_64 xen-4.8.1-2.fc26.x86_64 libvirt-3.2.1-1.fc26.x86_64 I can disable '3dnowprefetch' CPU feature in guest via 'xl' command, with adding `cpuid='host,3dnowprefetch=0'` into the CFG file. However, follow the instruction (https://libvirt.org/ formatdomain.html#elementsCPU), I added the following block into my XML file: ``` <cpu mode='host-passthrough' check='none'> <feature policy='disable' name='3dnowprefetch'/> </cpu> ``` Created the instance, seemed this feature was not being disabled in my guest. (I was able to see '3dnowprefetch' in `lscpu` outputs) Anybody has idea on this? Does libvirt support this for Xen? Any help would be appreciated. Thank you in advance. Regards, Charles Charles Shih (史晨) Quality Engineer Red Hat, Platform QE, Virt QE, Section 1 Email: cheshi(a)redhat.com IRC: cheshi @ #eng-china, #hyperv ,#qa, #virt T: +86 10 65627484 <010%206562%207484> - IP: 8387484 M: +86 18611268098 <186%201126%208098>

2 2

[libvirt-users] node device lifecycle callback can't resive event
by netsurfed 04 Jul '17

04 Jul '17

Hi all, I registe node device lifecycle event callback function after connect qemu. In the callback function, I printf the event and detail. When I plug a USB into host, and then pull out, but there is nothing happen. The callback was not called. Could you tell me Why? And what dose node device mean? I want to auto-hotplug usb devices by using libvirt. Bellow the call of libvirt: // node device lifecycle callback function void nodeDeviceEventLifecycleCallback(virConnectPtr conn, virNodeDevicePtr dev, int event, int detail, void * opaque) { printf("event = %d, detail= %d\n", event, detail); } // registe node device lifecycle event int registeNodeDevEvent() { int ret = virEventRegisterDefaultImpl(); if (ret) { return -1;} ret = virConnectNodeDeviceEventRegisterAny(vmh_conn, NULL, VIR_NODE_DEVICE_EVENT_ID_LIFECYCLE, VIR_NODE_DEVICE_EVENT_CALLBACK(nodeDeviceEventLifecycleCallback), NULL, NULL); if (-1 == ret) { return ret;} } Below some information about my hypervisor: root@ubuntu-05:/datapool/zhuohf# virsh -v 3.4.0 root@ubuntu-05:/datapool/zhuohf# qemu-x86_64 -version qemu-x86_64 version 2.9.0 Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

1 0

Re: [libvirt-users] recovering from deleted snapshot
by Doug Hughes 30 Jun '17

30 Jun '17

On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa(a)redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: > > > > [...] > > > > > virsh blockcommit $vm $DISK --active --pivot > > > > > > Normally this works fine, though something went wrong on the 20th. > > > something happened to make the blockcommit fail, but the -snap file got > > > deleted (note to self - check return code from blockcommit command!) > > > > > > So now I'm in a state. The domain i still running. but it's running off > > > the -snapshot that is in the xml. I googled around for how to recover a > > > blockcommit from a deleted snapshot, but didn't find anything. (pointers > > > welcome) > > In fact, it's way simpler. If libvirt still knows about the overlay > image (this is necessary only so that it can say the proper things to > qemu) you can re-do the block commit: > > $ virsh list > Id Name State > ---------------------------------------------------- > 3 fedora23 running > > $ virsh snapshot-create-as --disk-only --no-metadata fedora23 > Domain snapshot 1498817916 created > $ virsh domblklist fedora23 > Target Source > ------------------------------------------------ > vda /var/lib/libvirt/images/fedora23.1498817916 > hda - > > $ rm /var/lib/libvirt/images/fedora23.1498817916 > $ ls /var/lib/libvirt/images/fedora23.1498817916 > ls: cannot access '/var/lib/libvirt/images/fedora23.1498817916': No such file or directory > $ virsh blockcommit --active --pivot fedora23 vda > > Successfully pivoted > $ virsh domblklist fedora23 > Target Source > ------------------------------------------------ > vda /var/lib/libvirt/images/fedora23.qcow2 > hda - > Thanks for the reply! The original image is still there. Only the 1st and only top-level snapshot is deleted. the blockcommit fails though: [root@vm1 ~]# virsh blockcommit serv1r2 vda --active --pivot error: block copy still active: disk 'vda' already in active block job

3 4

[libvirt-users] recovering from deleted snapshot
by Doug Hughes 30 Jun '17

30 Jun '17

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic --no-metadata --quiesce ... virsh blockcommit $vm $DISK --active --pivot Normally this works fine, though something went wrong on the 20th. something happened to make the blockcommit fail, but the -snap file got deleted (note to self - check return code from blockcommit command!) So now I'm in a state. The domain i still running. but it's running off the -snapshot that is in the xml. I googled around for how to recover a blockcommit from a deleted snapshot, but didn't find anything. (pointers welcome) [root@vm1 images]# virsh domblklist serv1r2 Target Source ------------------------------------------------ vda /var/lib/libvirt/images/serv1r2-snap.qcow2 fda - hdb /var/lib/libvirt/images/virtio-win-0.1.126.iso I can see the size increasing on the deleted file in lsof: qemu-kvm 48994 49033 qemu 97u REG 0,44 1855913984 1078 /var/lib/libvirt/images/serv1r2-snap.qcow2 (deleted) ... qemu-kvm 48994 49033 qemu 97u REG 0,44 1856110592 1078 /var/lib/libvirt/images/serv1r2-snap.qcow2 (deleted) -- so, do I need to rollback the zfs snapshot image or is there some other way to recover from this snafu? Thanks.

2 2

[libvirt-users] Problems creating a new volume
by Pablo Vieytes 27 Jun '17

27 Jun '17

Hi, I'm having troubles creating a new storage volume in c++. This is my code: storageVolXml = "<volume>\ <name>" + name +".img</name>\ <allocation>0</allocation>\ <capacity unit=\"G\">" + hd + "</capacity>\ <target>\ <path>" + filePath + "</path>\ <format type='"+ diskFormatType + "'/>\ </target>\ </volume>"; storageVolPtr = virStorageVolCreateXML(pool, storageVolXml.toLatin1().data(), VIR_STORAGE_VOL_CREATE_PREALLOC_METADATA); I don't have any error but no file is created in the specified path (filePath). Any suggestion? Thanks in advance.

1 0

[libvirt-users] Accepting RELATED, ESTABLISHED (TCP) connections into VM using Network Filters
by Wido den Hollander 27 Jun '17

27 Jun '17

Hi, Over the past few days I've been trying to get a prototype working of a stateful firewall for a Virtual Machine using Libvirt's network filters. My goal is to replace the current custom Python/Java code in the Apache CloudStack [0] project by Network Filters of Libvirt. Both IPv4 and IPv6 should work, but I started off with IPv4 and I have issues with accepting back RELATED,ESTABLISHED connections into the VM. In the guest's XML I have this defined: <filterref filter='nwfilter-test'> <parameter name='IP' value='192.168.200.250'/> <parameter name='IPV6' value='2001:db8:100:0:5054:ff:fe9c:6ce6'/> <parameter name='IPV6' value='fe80::5054:ff:fe9c:6ce6'/> </filterref> And the filter currently looks like this: <filter name='nwfilter-test' chain='root'> <uuid>a2493284-9dd5-4c20-98b5-7e70745b53de</uuid>  <filterref filter='no-mac-spoofing'/> <filterref filter='no-ip-spoofing'/> <filterref filter='no-arp-spoofing'/> <filterref filter='allow-dhcp'/>  <rule action='accept' direction='in' priority='100'> <all state='RELATED,ESTABLISHED'/> </rule> <rule action='return' direction='in' priority='500'> <icmp/> </rule> <rule action='accept' direction='in' priority='500'> <tcp dstportstart='22'/> </rule> <rule action='accept' direction='in' priority='500'> <tcp dstportstart='80'/> </rule> <rule action='reject' direction='in' priority='1000'> <all/> </rule> </filter> I can SSH into the VM and also visit the Webserver running on it. But going out the VM results in issues: root@nwfilter-test:~# telnet 109.72.92.155 80 Trying 109.72.92.155... telnet: Unable to connect to remote host: Connection refused root@nwfilter-test:~# I can however ping the same target: root@nwfilter-test:~# ping -c 2 109.72.92.155 PING 109.72.92.155 (109.72.92.155) 56(84) bytes of data. 64 bytes from 109.72.92.155: icmp_seq=1 ttl=56 time=13.2 ms 64 bytes from 109.72.92.155: icmp_seq=2 ttl=56 time=14.1 ms --- 109.72.92.155 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 13.225/13.703/14.182/0.492 ms root@nwfilter-test:~# Looking at iptables-save it seems like the right rules are programmed: -A FI-vnet1 -p icmp -j RETURN -A FI-vnet1 -p tcp -m tcp --sport 22 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN -A FI-vnet1 -p tcp -m tcp --sport 80 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN -A FI-vnet1 -j REJECT --reject-with icmp-port-unreachable -A FO-vnet1 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FO-vnet1 -p icmp -j RETURN -A FO-vnet1 -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -m conntrack --ctdir ORIGINAL -j ACCEPT -A FO-vnet1 -p tcp -m tcp --dport 80 -m conntrack --ctstate NEW,ESTABLISHED -m conntrack --ctdir ORIGINAL -j ACCEPT -A FO-vnet1 -j REJECT --reject-with icmp-port-unreachable -A HI-vnet1 -p icmp -j RETURN -A HI-vnet1 -p tcp -m tcp --sport 22 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN -A HI-vnet1 -p tcp -m tcp --sport 80 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN -A HI-vnet1 -j REJECT --reject-with icmp-port-unreachable -A libvirt-host-in -m physdev --physdev-in vnet1 -g HI-vnet1 -A libvirt-in -m physdev --physdev-in vnet1 -g FI-vnet1 -A libvirt-in-post -m physdev --physdev-in vnet1 -j ACCEPT -A libvirt-out -m physdev --physdev-out vnet1 --physdev-is-bridged -g FO-vnet1 I tried changing 'accept' into 'return' for the incoming RELATED,ESTABLISHED rules, but that didn't help. I also tried searching for example of more complex network filters, but all I keep finding are the default filters of Libvirt. Does anybody know what I'm doing wrong here? Or are there any examples of working filters out there? Thank you! Wido [0]: http://cloudstack.apache.org/

1 0

[libvirt-users] Authenticating virsh with username and password
by Petr Kotas 26 Jun '17

26 Jun '17

Hi, I am new to libvirt and still learning, so thanks for any help. I am using libvirt configured with username and password. I need to utilize libvirt service "libvirt-guests.service" to shutdown all my VMs on system shutdown. Unfortunately it fails due to failed authentication. Jun 26 15:56:55 localhost virsh[13326]: All-whitespace username. Jun 26 15:56:55 localhost libvirt-guests.sh[13114]: Unable to connect to libvirt currently. Retrying .. 2Please enter your authenti Jun 26 15:56:55 localhost libvirtd[1155]: End of file while reading data: Input/output error Is it possible to specify user and password somehow? I cannot run kerberos or some other token based authentication. Thanks for any help. Kind regards, Petr Kotas

1 0

[libvirt-users] Configuring VMM for USB/Serial
by Brianna Moczynski 26 Jun '17

26 Jun '17

Hello, I keep receiving errors such as the following: Error rebooting domain: Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 126, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1378, in reboot self._backend.reboot(0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2024, in reboot if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self) libvirtError: Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) Whereby VMM loads, showing my VM in the "Paused" state and will not start, restart, shout down, etc. Restarting libvirt did not seem to have an effect on the issue. I ultimately solved it by removing and reinstalling the VM itself. Additionally, and I believe the issues may be somewhat related, I am having the following issues: libvirt not supporting forwarding ttys as usb serial devices (for pci serial cards (multiple serial ports)) virt-manager not supporting redirecting usb devices by vendor:device id I was wondering if you might have any suggestions on how to configure libvirt so that I do not have these issues. Thanks, BJM

1 0

[libvirt-users] About libvirt concurrency
by 马金舟 26 Jun '17

26 Jun '17

hi all: hello. I would like to ask a question about concurrency. Whether libvirt can achieve at the same time open 200 virtual machines. I try to open 200 virtual machines at the same time. oh on. when i am connected one of the virtual machines, i waited for a long time. I guess libvirt can't achieve concurrent operaction. I wish I could get a real result as soon as possible. thank you.

2 1

[libvirt-users] GPIO support in libvirt
by 陶缘 24 Jun '17

24 Jun '17

Hi, Dear libvirt experts: I am deploying a Virtual Machine to my hardware running linux. The thing is about the LED, the LED is controlled by GPIO operation. I do not know if my current qemu or libvirt can virtualize GPIO operation. And if yes, where can I find the options of qemu or libvirt(preferred) I am using qemu 2.4.0 and libvirt 1.3.2 Appreciate if hear from you Thanks eddy

1 0