- Users - libvirt List Archives

[libvirt-users] Attach / detach problem for passthrough/SR-IOV in libvirt
by Mohsen Ghaemi 27 Mar '14

27 Mar '14

Hi all I just encountered a problem in libvirt while was trying to attach and detach a sr-iov vf to my VM The version of my libvirt is 1.1.1-0ubuntu8.5 I tried to attach the device using following xml <interface type='hostdev' managed='yes'> <mac address='5c:01:fd:12:34:58'/> <source> <address type='pci' domain='0x0000' bus='0x04' slot='0x01' function='0x1'/> </source> </interface> When i attached device it worked properly and i managed to ping another host. virsh # attach-device t5 1.xml Device attached successfully But when i detached it still i had network traffic in my VM but libvirt (virsh) said that virsh # detach-device t5 1.xml Device detached successfully The next time i tried to attach it libvirt said that virsh # attach-device t5 1.xml error: Failed to attach device from 1.xml error: Requested operation is not valid: PCI device 0000:04:01.1 is in use by domain t5 I tried it with different VMs and different guest OSs that the same happend. The same action was done with another host running libvirt version Installed: 1.0.2-0ubuntu11.13.04.5~cloud1 Candidate: 1.0.2-0ubuntu11.13.04.5~cloud1 and it worked pretty OK. No problem. Do you have any idea what is wrong? More information: Kernel : 3.8.0-37-generic /etc/libvirt/qemu.conf : security_driver = "none” root@compute01:~# ethtool -i eth5 driver: bnx2x version: 1.78.58 firmware-version: bc 7.4.22 phy 1.34 bus-info: 0000:04:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes

1 0

[libvirt-users] libvirt-users@redhat.com
by Mohsen Ghaemi 27 Mar '14

27 Mar '14

Hi all I just encountered a problem in libvirt while was trying to attach and detach a sr-iov vf to my VM The version of my libvirt is 1.1.1-0ubuntu8.5 I tried to attach the device using following xml <interface type='hostdev' managed='yes'> <mac address='5c:01:fd:12:34:58'/> <source> <address type='pci' domain='0x0000' bus='0x04' slot='0x01' function='0x1'/> </source> </interface> When i attached device it worked properly and i managed to ping another host. virsh # attach-device t5 1.xml Device attached successfully But when i detached it still i had network traffic in my VM but libvirt (virsh) said that virsh # detach-device t5 1.xml Device detached successfully The next time i tried to attach it libvirt said that virsh # attach-device t5 1.xml error: Failed to attach device from 1.xml error: Requested operation is not valid: PCI device 0000:04:01.1 is in use by domain t5 I tried it with different VMs and different guest OSs that the same happend. The same action was done with another host running libvirt version Installed: 1.0.2-0ubuntu11.13.04.5~cloud1 Candidate: 1.0.2-0ubuntu11.13.04.5~cloud1 and it worked pretty OK. No problem. Do you have any idea what is wrong? More information: Kernel : 3.8.0-37-generic /etc/libvirt/qemu.conf : security_driver = "none” root@compute01:~# ethtool -i eth5 driver: bnx2x version: 1.78.58 firmware-version: bc 7.4.22 phy 1.34 bus-info: 0000:04:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes

1 0

[libvirt-users] Sending command to virtual machine
by lukass.vacek＠seznam.cz 26 Mar '14

26 Mar '14

Hello, I would like to know if there is a way how to execute a command inside of running virDomainPtr. For example call exec command but not on my computer, but on running virtual machine. If there is a way, what needs to be done for it? Thanks for answer!

2 1

[libvirt-users] Recreating nwfilter rules without a restart
by Brian Rak 26 Mar '14

26 Mar '14

Let's say I have some iptables rules defined to restrict guest traffic. If I restart the hosts firewall 'service iptables restart', all the guest-specific rules get blown away. Is there a way to reapply all the guest firewall rules, without restarting each individual guest? It looks like if I edit a nwfilter with `virsh nwfilter-edit` it goes and reapplies the rules to all the guests, so this functionality seems to be present already.

1 1

[libvirt-users] who Maintain netfilter, i want to submit a patch
by bigclouds 26 Mar '14

26 Mar '14

hi,all i have a patch for netfilter, i want to talk with you, how to submit ? thanks

3 2

[libvirt-users] Starting processes inside VMs using Libvirt?
by Taimur Al Said 25 Mar '14

25 Mar '14

Hi there, I am a beginner with Libvirt. I was practicing using Python bindings with libvirt to do some basic stuff like starting a VM, rebooting a VM, displaying the number of domain,etc. I was wondering since the hypervisor has control over the VMs, it is possible to use Libvirt to inject code into the VM? Is it possible to start processes inside a particular VM using the Libvirt API. If not, what would you recommend instead? Thanks in advance Regards, T.alsaid

3 4

[libvirt-users] Clock problems on live migration
by Paul Boven 24 Mar '14

24 Mar '14

Hi everyone, While doing a live migration, Linux guests will frequently get stuck and become unresponsive, while the CPU utilization on the host for that guest goes to 100%. Sometimes they recover, and dmesg then shows that there's been a clock problem during the live migration: Clocksource tsc unstable (delta = 35882846234 ns) So the TSC did a jump of nearly 36 seconds. Migrations often fail when going from server A to B, but will then work fine in the other direction. Both servers are locked to the same NTP source, and are well within 1ms from one another. Both hosts are running Ubuntu 13.04 with these versions (from Ubuntu packages): Kernel: 3.8.0-35-generic x86_64 Libvirt: 1.0.2 Qemu: 1.4.0 Gluster-fs: 3.4.2 (libvirt access the images via the filesystem, not using libgfapi yet). The interconnect between both machines (both for migration and gluster) is 10GbE. We have different guests (all Ubuntu releases, 13.04 and 13.10), and they all seem to be affected. Clocksource: kvm-clock on all guests. Clock entry from the guest XML: <clock offset='utc'/> Now as far as I've read in the documentation of kvm-clock, it specifically supports live migrations, so I'm a bit surprised at these problems. There isn't all that much information to find on these issue, although I have found postings by others that seem to have run into the same issues, but without a solution. Any help would be much appreciated. Regards, Paul Boven. -- Paul Boven <boven(a)jive.nl> +31 (0)521-596547 Unix/Linux/Networking specialist Joint Institute for VLBI in Europe - www.jive.nl VLBI - It's a fringe science

1 0

[libvirt-users] io mode=native precisions
by Raphael Bauduin 24 Mar '14

24 Mar '14

Hi, Before switching to io mode=native, I wanted to check if there are any disadvantages or potential problem with this setting. I virtio-blk data plane required to use this setting effectively? (as illustrated here: http://blog.vmsplice.net/2013/03/new-in-qemu-14-high-performance-virtio.html) Is there a requirement on the host kernel (eg minimum version)? Thanks in advance Raph

2 3

[libvirt-users] can I undo the snapshot apply of a qcow2 image
by lyz_pro 24 Mar '14

24 Mar '14

Hi all I have a problem. Two days ago , I used kvm-img create a snapshot of an qcow2 format image. And today I apply the snapshot of this image. The question is can I recovery the image to the last point . I mean Undo this snapshot apply -------------- lyz_pro 2014-03-24

2 1

[libvirt-users] Issues to manage RAM on openvz guests
by Aurelien Martin 22 Mar '14

22 Mar '14

Hi all, I'm playing with virsh, and I succeed to mange easily some KVM nodes. But I have issues to size RAM of openvz guests. virsh set by default the the memory to 256M on each guest instead of that I specify in the XML I have to modify by end the variable PHYSPAGES on each /etc/vz/conf/id_of_my_vz.conf Please follow the XML dump and the steps that I did. Cheers,Aurelien Log ---- 1) Define openvz guest domain 103 #virsh -c openvz:///system define vztest.xml Domain 103 defined from vztest.xml 2) Start the guest #virsh -c openvz:///system start 103 Domain 103 started #vzlist CTID NPROC STATUS IP_ADDR HOSTNAME 103 20 running - - 3) Check memory size vz guest 103 #vzctl enter 103 entered into CT 103 #root@test:/# free -m total used free shared buffers cached Mem: 256 27 228 0 0 14 -/+ buffers/cache: 13 242 Swap: 512 0 512 vztest.xml ----------- <domain type='openvz'> <name>100</name> <uuid>86c12009-e591-a159-6e9f-91d18b85ef78</uuid> <memory unit='GiB'>1</memory> <currentMemory unit='GiB'>1</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type>exe</type> <init>/sbin/init</init> </os> <devices> <filesystem type='template' accessmode='passthrough'> <source name='debian-7.0-x86_64'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='00:16:3e:1a:66:67'/> <source bridge='br0'/> <target dev='veth3'/> </interface> </devices> </domain> xmldump -------- <domain type='openvz' id='103'> <name>103</name> <uuid>86c52009-e541-a159-6e9f-91d18b85ef79</uuid> <memory unit='KiB'>0</memory> <currentMemory unit='KiB'>0</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <filesystem type='template' accessmode='passthrough'> <source name='debian-7.0-x86_64'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='00:16:3e:1a:66:67'/> <source bridge='br0'/> <target dev='veth3'/> </interface> </devices> </domain>

1 1