- Users - libvirt List Archives

[libvirt-users] vnc client for libvirt from os x?
by pixelfairy 05 Feb '15

05 Feb '15

id like to access libvirt kvm consoles from my macbook. i tried realvnc, which just crashes immediately, and the built in "screen sharing" client, which insists on a password, which i havent set. does anyone here do this? which vnc client do you use?

2 3

[libvirt-users] Vepa use vf?
by Yaron Illouz 03 Feb '15

03 Feb '15

1. Does vepa mode in libvirt use sr-iov ? 2. How can I do port mirroring with sr-iov? vepa This network uses a macvtap "direct" connection in "vepa" mode to connect each guest to the network (this requires that the physical interfaces used be connected to a vepa-capable hardware switch. The physical interface to be used will be picked from among those listed in <interface>subelements of the <forward> element; multiple guest interfaces can share each physical interface (libvirt will attempt to balance usage between all available interfaces).Since 0.9.4

3 2

[libvirt-users] virsh snapshot-create persistent through destroy(undefine)
by Yitao Jiang 31 Jan '15

31 Jan '15

Hi, If i take a snapshot of a qcow2 image backed domain via virsh snapshot-create domainID and I shutdown the machine (and probably destroy the domain if virsh list still shows it running), and then undeinfed the domain will that snapshot still exist and be active when I define and start the domain back up? --- Thanks, Yitao(依涛姜) jiangyt.github.io

2 3

[libvirt-users] Disk space exhaustion
by Fabrizio Soppelsa 31 Jan '15

31 Jan '15

Hello, what happens when an instance writes data with 0% available physical disk space, on QCOW2 images for instance, apart from destruction and unpredictability? I'm aware that monitoring is mandatory in production environments, but are there other known industry tricks to deal with this? Soft/hard limit settings, autopause/stop, or does KVM react in doing force shut down the VM in question? Thank you, Fabrizio.

2 1

[libvirt-users] redistribute virtual machines from vps hosting to end users
by Vasiliy Tolstov 30 Jan '15

30 Jan '15

Hi. I need to get ability to download backups of kvm virtual machines (raw images) to end users. Virtualbox users can import ovs images, that i can create, but in case of linux and virt-manager - how users can import images and simply run it? I think about newbie linux users, that can install virt-manager under ubuntu via graphical package manager and do some easy steps... Can you share me info how can i do needed things ?=)Or may be some admins/users already solve this kind of "problems"... -- Vasiliy Tolstov, e-mail: v.tolstov(a)selfip.ru jabber: vase(a)selfip.ru

3 6

[libvirt-users] Windows Guest ignores CPU topology settings on Ubuntu Lucid host
by Karol Jędrzejczyk 29 Jan '15

29 Jan '15

I try to assign 8 host cores to Windows 2003 Server Standard guest. Because this OS version has a limit of 4 sockets, I have to change the CPU topology. My guest definition: <vcpu>8</vcpu> <cpu match='minimum'> <model>core2duo</model> <topology sockets='4' cores='1' threads='2'/> </cpu> doesn't work as expected. I should have 4 CPUs in the Device Manager and 8 CPU charts in Task Manager, but I have the opposite. And no matter what numbers I set in the topology, the guest always detects 8 sockets. What am I doing wrong? libvirt 0.7.5 qemu-kvm 0.12.3 -- Karol Jędrzejczyk

2 2

[libvirt-users] Port mirroring with sr-iov
by Yaron Illouz 29 Jan '15

29 Jan '15

Is it possible to do port mirroring while using sriov in the same host and in different host I am using libvirt What must i do? Perhaps bridge two controller virtual function If yes, should I do it with ovs-vsctl, or there is a libvirt functionnality libvirt version: 0.10.2, package: 29.el6_5.12 Open vSwitch) 1.9.0 My ethernet card is... Intel Corporation 82599ES 10-Gigabit SFI/SFP+ ethtool -i eth6 driver: ixgbe version: 3.19.1-k

1 0

Re: [libvirt-users] Sr-iov passthrough - no packet arrive to guest
by Yaron Illouz 29 Jan '15

29 Jan '15

I can see from different post that if working with sr-iov, i should work with vlan Is this an obligation to work with vlan if working with sr-iov? If not according to which parameter will the different vf get the traffic. Let's say i declare max_vfs=7, how will the traffic be seperated between the vm? However till i get an answer i tried to work with vlan And i still don't get traffic in vm, but i see packet arriving in the physical interface of the host I tried to do the following to define the vlan In virsh edit <interface type='hostdev' managed='yes'> <mac address='52:54:00:60:7f:57'/> <source> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x0'/> </source> <vlan> <tag id='44'/> </vlan> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> In host ip link 23: eth6: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 38:ea:a7:8f:fa:98 brd ff:ff:ff:ff:ff:ff vf 0 MAC 52:54:00:60:7f:57, vlan 44 In guest modprob 8021q eth1 Link encap:Ethernet HWaddr 52:54:00:60:7F:57 inet6 addr: fe80::5054:ff:fe60:7f57/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1156 (1.1 KiB) eth1.44 Link encap:Ethernet HWaddr 52:54:00:60:7F:57 inet6 addr: fe80::5054:ff:fe60:7f57/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ________________________________ From: Yaron Illouz Sent: Tuesday, January 27, 2015 9:56 PM To: 'libvirt-users(a)redhat.com' Subject: Sr-iov passthrough - no packet arrive to guest Hi I am trying to do passthrough to guest using sriov and libvirt I tried to use both techniques from here http://wiki.libvirt.org/page/Networking#Assignment_with_.3Chostdev.3E <http://wiki.libvirt.org/page/Networking#Assignment_with_.3Chostdev.3E> Assignment from a pool of SRIOV VFs in a libvirt <network> definition Assignment with <interface type='hostdev'> (SRIOV devices only) <network> <name>passthrough-eth6</name> <forward mode='hostdev' managed='yes'> <pf dev='eth6'/> </forward> </network> I launch the vm, there is a vm with virt-install .... --network network=passthrough-eth6 I inject traffic with a generator so I defined it in promisc mode without an ip address.(ifconfig eth6 promisc up) In my physical device eth6 i can see RX increasing. But in the guest side nothing arrive in the RX? Why? I don't know in which log to look at to understand the problem I defined the network-script/eth1 file in the guest is defined as static (not dhcp) as the interface it is connected to in host have no ip. I have a another interface on the host connected via ovs and libvirt and it is working fine - you can see it in log as vnet0(thanks to this mailing-list help). In the guest part I attached the log but I think interesting part is Jan 27 17:03:21 localhost kernel: ixgbevf 0000:00:04.0: NIC Link is Up, 10 Gbps I also attached dmesg output from guest Here is the log from the host side, I can't see an error. /var/log/message Jan 27 12:02:29 1235 avahi-daemon[2598]: Withdrawing address record for fe80::fc54:ff:fe92:7352 on vnet0. Jan 27 12:02:29 1235 kernel: device vnet0 left promiscuous mode Jan 27 12:02:30 1235 kernel: ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 Jan 27 12:02:30 1235 ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port vnet0 Jan 27 12:02:30 1235 ovs-vswitchd: 00180|bridge|ERR|bridge virbr0: mirror mirror-1-to-3 does not specify output; ignoring Jan 27 12:02:31 1235 ntpd[2905]: Deleting interface #28 vnet0, fe80::fc54:ff:fe92:7352#123, interface stats: received=0, sent=0, dropped=0, active_time=981 secs Jan 27 12:02:31 1235 ntpd[2905]: peers refreshed Jan 27 12:02:43 1235 kernel: ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. Jan 27 12:02:43 1235 kernel: kvm: 7957: cpu0 unhandled rdmsr: 0x345 Jan 27 12:02:43 1235 kernel: kvm: 7957: cpu0 unhandled wrmsr: 0x680 data 0 ... Jan 27 12:02:51 1235 ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-port br3 vnet0 -- set Interface vnet0 "external-ids:attached-mac=\"52:54:00:43:BF:8C\"" -- set Interface vnet0 "external-ids:iface-id=\"309ed431-417f-2843-89b8-179a066aa595\"" -- set Interface vnet0 "external-ids:vm-id=\"870e3b65-953b-01ee-84a3-c2d05300c2d9\"" -- set Interface vnet0 external-ids:iface-status=active Jan 27 12:02:51 1235 ovs-vswitchd: 00183|bridge|ERR|bridge virbr0: mirror mirror-1-to-3 does not specify output; ignoring Jan 27 12:02:51 1235 kernel: device vnet0 entered promiscuous mode Jan 27 12:02:51 1235 kernel: ixgbe 0000:15:00.0: setting MAC 52:54:00:d9:f1:bd on VF 0 Jan 27 12:02:51 1235 kernel: ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. Jan 27 12:02:51 1235 kernel: pci-stub 0000:15:10.0: enabling device (0000 -> 0002) Jan 27 12:02:52 1235 avahi-daemon[2598]: Registering new address record for fe80::fc54:ff:fe43:bf8c on vnet0.*. Jan 27 12:02:54 1235 ntpd[2905]: Listen normally on 29 vnet0 fe80::fc54:ff:fe43:bf8c UDP 123 Jan 27 12:02:54 1235 ntpd[2905]: peers refreshed Jan 27 12:03:17 1235 kernel: __ratelimit: 23 callbacks suppressed Jan 27 12:03:17 1235 kernel: kvm: 8006: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd Jan 27 12:03:20 1235 kernel: ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 And this is the /var/log/libvirt/qemu/probe8.log from the host 2015-01-27 17:02:51.762+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name probe8 -S -M rhel6.6.0 -enable-kvm -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 870e3b65-953b-01ee-84a3-c2d05300c2d9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/probe8.monitor,server,n owait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,ad dr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -drive file=/data/KVM/comp_VNF_MaveriQ_Probe2-cloud8.qcow2,if=none,id=drive-ide 0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/var/lib/libvirt/images/configuration8.iso,if=none,id=drive-virtio- disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=v irtio-disk0 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:43:bf:8c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:0 -vga cirrus -device pci-assign,host=15:10.0,id=hostdev0,configfd=26,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on char device redirected to /dev/pts/1 I can see that virtual function succeeded because I got the following output virsh net-dumpxml passthrough-eth6 <network connections='1'> <name>passthrough-eth6</name> <uuid>f8fd37cd-3215-e4b0-17b1-0b5515140db9</uuid> <forward mode='hostdev' managed='yes'> <pf dev='eth6'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x0'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x2'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x4'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x6'/> ... </forward> </network> lspci | grep Intel 15:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 15:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 15:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01) 15:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01) .... And Intel-IOMMU: enabled in the dmesg >From host dmesg ixgbe 0000:15:00.0: setting MAC 52:54:00:97:c6:86 on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present __ratelimit: 23 callbacks suppressed kvm: 6896: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 3 pci-stub 0000:15:10.6: claimed by stub device vnet0 left promiscuous mode pci-stub 0000:15:10.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. kvm: 7207: cpu0 unhandled rdmsr: 0x345 kvm: 7207: cpu0 unhandled wrmsr: 0x680 data 0 ... ixgbe 0000:15:00.0: setting MAC 52:54:00:16:b6:0c on VF 3 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode pci-stub 0000:15:10.6: enabling device (0000 -> 0002) assign device 0:15:10.6 vnet0: no IPv6 routers present __ratelimit: 24 callbacks suppressed kvm: 7254: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 3 pci-stub 0000:15:10.6: irq 62 for MSI/MSI-X pci-stub 0000:15:10.6: irq 63 for MSI/MSI-X pci-stub 0000:15:10.6: irq 62 for MSI/MSI-X pci-stub 0000:15:10.6: irq 63 for MSI/MSI-X device vnet0 left promiscuous mode pci-stub 0000:15:10.6: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC ba:c1:bd:19:c1:d5 on VF 3 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode ixgbe 0000:15:00.0: setting MAC 52:54:00:e2:39:62 on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present kvm: 7639: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X device vnet0 left promiscuous mode pci-stub 0000:15:10.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. kvm: 7957: cpu0 unhandled rdmsr: 0x345 kvm: 7957: cpu0 unhandled wrmsr: 0x680 data 0 ... device vnet0 entered promiscuous mode ixgbe 0000:15:00.0: setting MAC 52:54:00:d9:f1:bd on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present __ratelimit: 23 callbacks suppressed kvm: 8006: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X ...

1 1

[libvirt-users] Sr-iov passthrough - no packet arrive to guest
by Yaron Illouz 28 Jan '15

28 Jan '15

Hi I am trying to do passthrough to guest using sriov and libvirt I tried to use both techniques from here http://wiki.libvirt.org/page/Networking#Assignment_with_.3Chostdev.3E <http://wiki.libvirt.org/page/Networking#Assignment_with_.3Chostdev.3E> Assignment from a pool of SRIOV VFs in a libvirt <network> definition Assignment with <interface type='hostdev'> (SRIOV devices only) <network> <name>passthrough-eth6</name> <forward mode='hostdev' managed='yes'> <pf dev='eth6'/> </forward> </network> I launch the vm, there is a vm with virt-install .... --network network=passthrough-eth6 I inject traffic with a generator so I defined it in promisc mode without an ip address.(ifconfig eth6 promisc up) In my physical device eth6 i can see RX increasing. But in the guest side nothing arrive in the RX? Why? I don't know in which log to look at to understand the problem I defined the network-script/eth1 file in the guest is defined as static (not dhcp) as the interface it is connected to in host have no ip. I have a another interface on the host connected via ovs and libvirt and it is working fine - you can see it in log as vnet0(thanks to this mailing-list help). In the guest part I attached the log but I think interesting part is Jan 27 17:03:21 localhost kernel: ixgbevf 0000:00:04.0: NIC Link is Up, 10 Gbps I also attached dmesg output from guest Here is the log from the host side, I can't see an error. /var/log/message Jan 27 12:02:29 1235 avahi-daemon[2598]: Withdrawing address record for fe80::fc54:ff:fe92:7352 on vnet0. Jan 27 12:02:29 1235 kernel: device vnet0 left promiscuous mode Jan 27 12:02:30 1235 kernel: ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 Jan 27 12:02:30 1235 ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port vnet0 Jan 27 12:02:30 1235 ovs-vswitchd: 00180|bridge|ERR|bridge virbr0: mirror mirror-1-to-3 does not specify output; ignoring Jan 27 12:02:31 1235 ntpd[2905]: Deleting interface #28 vnet0, fe80::fc54:ff:fe92:7352#123, interface stats: received=0, sent=0, dropped=0, active_time=981 secs Jan 27 12:02:31 1235 ntpd[2905]: peers refreshed Jan 27 12:02:43 1235 kernel: ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. Jan 27 12:02:43 1235 kernel: kvm: 7957: cpu0 unhandled rdmsr: 0x345 Jan 27 12:02:43 1235 kernel: kvm: 7957: cpu0 unhandled wrmsr: 0x680 data 0 ... Jan 27 12:02:51 1235 ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-port br3 vnet0 -- set Interface vnet0 "external-ids:attached-mac=\"52:54:00:43:BF:8C\"" -- set Interface vnet0 "external-ids:iface-id=\"309ed431-417f-2843-89b8-179a066aa595\"" -- set Interface vnet0 "external-ids:vm-id=\"870e3b65-953b-01ee-84a3-c2d05300c2d9\"" -- set Interface vnet0 external-ids:iface-status=active Jan 27 12:02:51 1235 ovs-vswitchd: 00183|bridge|ERR|bridge virbr0: mirror mirror-1-to-3 does not specify output; ignoring Jan 27 12:02:51 1235 kernel: device vnet0 entered promiscuous mode Jan 27 12:02:51 1235 kernel: ixgbe 0000:15:00.0: setting MAC 52:54:00:d9:f1:bd on VF 0 Jan 27 12:02:51 1235 kernel: ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. Jan 27 12:02:51 1235 kernel: pci-stub 0000:15:10.0: enabling device (0000 -> 0002) Jan 27 12:02:52 1235 avahi-daemon[2598]: Registering new address record for fe80::fc54:ff:fe43:bf8c on vnet0.*. Jan 27 12:02:54 1235 ntpd[2905]: Listen normally on 29 vnet0 fe80::fc54:ff:fe43:bf8c UDP 123 Jan 27 12:02:54 1235 ntpd[2905]: peers refreshed Jan 27 12:03:17 1235 kernel: __ratelimit: 23 callbacks suppressed Jan 27 12:03:17 1235 kernel: kvm: 8006: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd Jan 27 12:03:20 1235 kernel: ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 And this is the /var/log/libvirt/qemu/probe8.log from the host 2015-01-27 17:02:51.762+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name probe8 -S -M rhel6.6.0 -enable-kvm -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 870e3b65-953b-01ee-84a3-c2d05300c2d9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/probe8.monitor,server,n owait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,ad dr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -drive file=/data/KVM/comp_VNF_MaveriQ_Probe2-cloud8.qcow2,if=none,id=drive-ide 0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/var/lib/libvirt/images/configuration8.iso,if=none,id=drive-virtio- disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=v irtio-disk0 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:43:bf:8c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:0 -vga cirrus -device pci-assign,host=15:10.0,id=hostdev0,configfd=26,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on char device redirected to /dev/pts/1 I can see that virtual function succeeded because I got the following output virsh net-dumpxml passthrough-eth6 <network connections='1'> <name>passthrough-eth6</name> <uuid>f8fd37cd-3215-e4b0-17b1-0b5515140db9</uuid> <forward mode='hostdev' managed='yes'> <pf dev='eth6'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x0'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x2'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x4'/> <address type='pci' domain='0x0000' bus='0x15' slot='0x10' function='0x6'/> ... </forward> </network> lspci | grep Intel 15:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 15:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 15:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01) 15:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01) .... And Intel-IOMMU: enabled in the dmesg >From host dmesg ixgbe 0000:15:00.0: setting MAC 52:54:00:97:c6:86 on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present __ratelimit: 23 callbacks suppressed kvm: 6896: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 3 pci-stub 0000:15:10.6: claimed by stub device vnet0 left promiscuous mode pci-stub 0000:15:10.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. kvm: 7207: cpu0 unhandled rdmsr: 0x345 kvm: 7207: cpu0 unhandled wrmsr: 0x680 data 0 ... ixgbe 0000:15:00.0: setting MAC 52:54:00:16:b6:0c on VF 3 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode pci-stub 0000:15:10.6: enabling device (0000 -> 0002) assign device 0:15:10.6 vnet0: no IPv6 routers present __ratelimit: 24 callbacks suppressed kvm: 7254: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 3 pci-stub 0000:15:10.6: irq 62 for MSI/MSI-X pci-stub 0000:15:10.6: irq 63 for MSI/MSI-X pci-stub 0000:15:10.6: irq 62 for MSI/MSI-X pci-stub 0000:15:10.6: irq 63 for MSI/MSI-X device vnet0 left promiscuous mode pci-stub 0000:15:10.6: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC ba:c1:bd:19:c1:d5 on VF 3 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. device vnet0 entered promiscuous mode ixgbe 0000:15:00.0: setting MAC 52:54:00:e2:39:62 on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present kvm: 7639: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X pci-stub 0000:15:10.0: irq 63 for MSI/MSI-X device vnet0 left promiscuous mode pci-stub 0000:15:10.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100004) ixgbe 0000:15:00.0: setting MAC a2:fc:a8:89:2a:8f on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. kvm: 7957: cpu0 unhandled rdmsr: 0x345 kvm: 7957: cpu0 unhandled wrmsr: 0x680 data 0 ... device vnet0 entered promiscuous mode ixgbe 0000:15:00.0: setting MAC 52:54:00:d9:f1:bd on VF 0 ixgbe 0000:15:00.0: Reload the VF driver to make this change effective. pci-stub 0000:15:10.0: enabling device (0000 -> 0002) assign device 0:15:10.0 vnet0: no IPv6 routers present __ratelimit: 23 callbacks suppressed kvm: 8006: cpu0 disabled perfctr wrmsr: 0xc1 data 0xabcd ixgbe 0000:15:00.0: eth6: VF Reset msg received from vf 0 pci-stub 0000:15:10.0: irq 62 for MSI/MSI-X ...

1 0

[libvirt-users] live migration taking forever
by Xu (Simon) Chen 27 Jan '15

27 Jan '15

Hey folks, I am running libvirt 1.2.4 and qemu 2.1 on a 3.14.27 kernel. I've found that live migrating a relatively large VM (16 cores and 64G ram) is taking forever - close to 15 hours now, and still not done... With "lsof -i", I can see a connection is established from my source hypervisor to a target hypervisor, likely for the purpose of copying data. nettop shows that this connection is constantly sending 50-60MBps traffic. The VM being migrated has a disk on ceph by using librbd. I wonder if anyone has seen similar issues, and how I could troubleshoot further. (I tried but failed to get qemu monitor to work on the VM...) Thanks. -Simon

4 3