virt April 2017

virt@lists.centos.org

26 participants
18 discussions

lvm cache + qemu-kvm stops working after about 20GB of writes
by Richard Landsman - Rimote 26 May '17

26 May '17

Hello, I would really appreciate some help/guidance with this problem. First of all sorry for the long message. I would file a bug, but do not know if it is my fault, dm-cache, qemu or (probably) a combination of both. And i can imagine some of you have this setup up and running without problems (or maybe you think it works, just like i did, but it does not): PROBLEM LVM cache writeback stops working as expected after a while with a qemu-kvm VM. A 100% working setup would be the holy grail in my opinion... and the performance of KVM/qemu is great i must say in the beginning. DESCRIPTION When using software RAID 1 (2x HDD) + software RAID 1 (2xSSD) and create a cached LV out of them, the VM performs initially great (at least 40.000 IOPS on 4k rand read/write)! But then after a while (and a lot of random IO, ca 10 - 20 G) it effectively turns in to a writethrough cache although there's much space left on the cachedlv. When working as expected on KVM host all writes go to SSDs iostat -x -m 2 Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 324.50 0.00 22.00 0.00 14.94 1390.57 1.90 86.39 0.00 86.39 5.32 11.70 sdb 0.00 324.50 0.00 22.00 0.00 14.94 1390.57 2.03 92.45 0.00 92.45 5.48 12.05 sdc 0.00 3932.00 0.00 *2191.50* 0.00 *270.07* 252.39 37.83 17.55 0.00 17.55 0.36 *78.05* sdd 0.00 3932.00 0.00 *2197.50 * 0.00 *271.01 * 252.57 38.96 18.14 0.00 18.14 0.36 *78.95* When not working as expected on KVM host all writes go through the SSD on to the HDDs (effectively disabling writeback so it becomes a writethrough) Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 7.00 234.50 *173.50 * 0.92 *1.95* 14.38 29.27 71.27 111.89 16.37 2.45 *100.00* sdb 0.00 3.50 212.00 *177.50 * 0.83 *1.95* 14.60 35.58 91.24 143.00 29.42 2.57*100.10* sdc 2.50 0.00 566.00 *199.00 * 2.69 0.78 9.28 0.08 0.11 0.13 0.04 0.10 *7.70* sdd 1.50 0.00 76.00 *199.00* 0.65 0.78 10.66 0.02 0.07 0.16 0.04 0.07 *1.85* Stuff i've checked/tried: - The data in the cached LV has then not exceeded even half of the space, so this should not happen. It even happens when only 20% of cachedata is used. - It seems to be triggerd most of the time when %cpy/sync column of `lvs -a` is about 30%. But this is not always the case! - changing the cachepolicy from cleaner to smq, wait (check flush ready with lvs -a) and then back to smq seems to help /sometimes/! But not always... lvchange --cachepolicy cleaner /dev/mapper/XXX-cachedlv lvs -a lvchange --cachepolicy smq /dev/mapper/XXX-cachedlv - *when mounting the LV inside the host this does not seem to happen!!* So it looks like a qemu-kvm / dm-cache combination issue. Only difference is that inside host i do mkfs in stead of LVM inside VM (so could be LVM inside VM on top of LVM on KVM host problem too? small chance probably because the first 10 - 20GB it works great!) - tried disabling Selinux, upgrading to newest kernels (elrepo ml and lt), played around with dirty_cache thingeys like proc/sys/vm/dirty_writeback_centisecs /proc/sys/vm/dirty_expire_centisecs cat /proc/sys/vm/dirty_ratio , and migration threashold of dmsetup, and other probably non important stuff like vm.dirty_bytes - when in "slow state" the systems kworkers are exessively using IO (10 - 20 MB per kworker process). This seems to be the writeback process (CPY%Sync) because the cache wants to flush to HDD. But the strange thing is that after a good sync (0% left), the disk may become slow again after a few MBs of data. A reboot sometimes helps. - have tried iothreads, virtio-scsi, vcpu driver setting on virtio-scsi controller, cachesettings, disk shedulers etc. Nothing helped. - the new samsung 950 PRO SSDs have HPA enabled (30%!!), i have AMD FX(tm)-8350, 16G RAM It feels like the lvm cache has a threshold (about 20G of data that is dirty) and that is stops allowing the qemu-kvm process to use writeback caching (the root uses inside the host seems to not have this limitation). It starts flushing, but only to a certain point. After a few MBs of data it is right back in the slow spot again. Only solution is waiting for a long time (independant of CPY%SYNC) or sometimes change cachepolicy and force flush. This prevents for me the production use of this system. But it's so promising, so I hope somebody can help. desired state: Doing the FIO test (described in section reproduce) repeatedly should keep being fast till cachedlv is more or less full. If resyncing back to disc causes this degradation, it should actually flush it fully within a reasonable time and give opportunity to write fast again up to a given threshold. It now seems like a one time use cache that only uses a fraction of the SSD and is useless/very unstable afterwards. REPRODUCE 1. Install newest CentOS 7 on software RAID 1 HDDs with LVM. Keep a lot of space for the LVM cache (no /home)! So make the VG as large as possible during anaconda partitioning. 2. once installed and booted in to the system, install qemu-kvm yum install -y centos-release-qemu-ev yum install -y qemu-kvm-ev libvirt bridge-utils net-tools # disbale ksm (probably not important / needed) systemctl disable ksm systemctl disable ksmtuned 3. create LVM cache #set some variables and create a raid1 array with the two SSDs VGBASE= && ssddevice1=/dev/sdX1 && ssddevice2=/dev/sdX1 && hddraiddevice=/dev/mdXXX && ssdraiddevice=/dev/mdXXX && mdadm --create --verbose ${ssdraiddevice} --level=mirror --bitmap=none --raid-devices=2 ${ssddevice1} ${ssddevice2} # create PV and extend VG pvcreate ${ssdraiddevice} && vgextend ${VGBASE} ${ssdraiddevice} # create slow LV on HDDs (use max space left if you want) pvdisplay ${hddraiddevice} lvcreate -lXXXX -n cachedlv ${VGBASE} ${hddraiddevice} # create the meta and data: for testing purposes I keep about 20G of the SSD for a uncached lv. To rule out it is not the SSD. lvcreate -l XX -n testssd ${VGBASE} ${ssdraiddevice} #The rest can be used as cachedata/metadata. pvdisplay ${ssdraiddevice} # about 1/1000 of the space you have left on the SSD for the meta (minimum of 4) lvcreate -l X -n cachemeta ${VGBASE} ${ssdraiddevice} # the rest can be used as cachedata lvcreate -l XXX -n cachedata ${VGBASE} ${ssdraiddevice} # convert/combine pools so cachedlv is actually cached lvconvert --type cache-pool --cachemode writeback --poolmetadata ${VGBASE}/cachemeta ${VGBASE}/cachedata lvconvert --type cache --cachepool ${VGBASE}/cachedata ${VGBASE}/cachedlv # my system now looks like (VG is called cl, default of installer) [root@localhost ~]# lvs -a LV VG Attr LSize Pool Origin [cachedata] cl Cwi---C--- 97.66g * [cachedata_cdata] cl Cwi-ao---- 97.66g ** ** [cachedata_cmeta] cl ewi-ao---- 100.00m * * cachedlv cl Cwi-aoC--- 1.75t [cachedata] [cachedlv_corig] * [cachedlv_corig] cl owi-aoC--- 1.75t [lvol0_pmspare] cl ewi------- 100.00m root cl -wi-ao---- 46.56g swap cl -wi-ao---- 14.96g * testssd cl -wi-a----- 45.47g *[root@localhost ~]#lsblk* * NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdd 8:48 0 163G 0 disk └─sdd1 8:49 0 163G 0 part └─md128 9:128 0 162.9G 0 raid1 ├─cl-cachedata_cmeta 253:4 0 100M 0 lvm │ └─cl-cachedlv 253:6 0 1.8T 0 lvm ├─cl-testssd 253:2 0 45.5G 0 lvm └─cl-cachedata_cdata 253:3 0 97.7G 0 lvm └─cl-cachedlv 253:6 0 1.8T 0 lvm sdb 8:16 0 1.8T 0 disk ├─sdb2 8:18 0 1.8T 0 part │ └─md127 9:127 0 1.8T 0 raid1 │ ├─cl-swap 253:1 0 15G 0 lvm [SWAP] │ ├─cl-root 253:0 0 46.6G 0 lvm / │ └─cl-cachedlv_corig 253:5 0 1.8T 0 lvm │ └─cl-cachedlv 253:6 0 1.8T 0 lvm └─sdb1 8:17 0 954M 0 part └─md126 9:126 0 954M 0 raid1 /boot sdc 8:32 0 163G 0 disk └─sdc1 8:33 0 163G 0 part └─md128 9:128 0 162.9G 0 raid1 ├─cl-cachedata_cmeta 253:4 0 100M 0 lvm │ └─cl-cachedlv 253:6 0 1.8T 0 lvm ├─cl-testssd 253:2 0 45.5G 0 lvm └─cl-cachedata_cdata 253:3 0 97.7G 0 lvm └─cl-cachedlv 253:6 0 1.8T 0 lvm sda 8:0 0 1.8T 0 disk ├─sda2 8:2 0 1.8T 0 part │ └─md127 9:127 0 1.8T 0 raid1 │ ├─cl-swap 253:1 0 15G 0 lvm [SWAP] │ ├─cl-root 253:0 0 46.6G 0 lvm / │ └─cl-cachedlv_corig 253:5 0 1.8T 0 lvm │ └─cl-cachedlv 253:6 0 1.8T 0 lvm └─sda1 8:1 0 954M 0 part └─md126 9:126 0 954M 0 raid1 /boot # now create vm wget http://ftp.tudelft.nl/centos.org/6/isos/x86_64/CentOS-6.9-x86_64-minimal.iso -P /home/ DISK=/dev/mapper/XXXX-cachedlv # watch out, my netsetup uses a custom bridge/network in the following command. Please replace with what you normally use. virt-install -n CentOS1 -r 12000 --os-variant=centos6.7 --vcpus 7 --disk path=${DISK},cache=none,bus=virtio --network bridge=pubbr,model=virtio --cdrom /home/CentOS-6.9-x86_64-minimal.iso --graphics vnc,port=5998,listen=0.0.0.0 --cpu host # now connect with client PC to qemu virt-viewer --connect=qemu+ssh://root@192.168.0.XXX/system --name CentOS1 And install everything on the single vda disc with LVM (i use defaults in anaconda, but remove the large /home to prevent SSD beeing over used). After install and reboot log in to VM and yum install epel-release -y && yum install screen fio htop -y and then run disk test: fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test *--filename=test* --bs=4k --iodepth=64 --size=4G --readwrite=randrw --rwmixread=75 then *keep repeating *but *change the filename* attribute so it does not use the same blocks over and over again. In the beginning the performance is great!! Wow, very impressive 150MB/s 4k random r/w (close to bare metal, about 20% - 30% loss). But after a few (usually about 4 or 5) runs (always changing the filename, but not overfilling the FS, it drops to about 10 MBs/sec. normal/in the beginning read : io=3073.2MB, bw=183085KB/s, *iops=45771* , runt= 17188msec write: io=1022.1MB, bw=60940KB/s, *iops=15235* , runt= 17188msec but then read : io=3073.2MB, bw=183085KB/s, *iops=**2904* , runt= 17188msec write: io=1022.1MB, bw=60940KB/s, *iops=1751* , runt= 17188msec or even worse up to the point that it is actually the HDD that is written to (about 500 iops). P.S. when a test is/was slow, that means it is on the HDDs. So even when fixing the problem (sometimes just by waiting), that specific file will keep being slow when redoing the test till its promoted to the lvm cache (takes a lot of reads I think). And once on the SSD it sometimes keeps beeing fast, although a new testfile will be slow. So I really recommend changing the testfile all the time when trying to see if a change in speed has occurred. -- Met vriendelijke groet, Richard Landsman http://rimote.nl T: +31 (0)50 - 763 04 07 (ma-vr 9:00 tot 18:00) 24/7 bij storingen: +31 (0)6 - 4388 7949 @RimoteSaS (Twitter Serviceberichten/security updates)

2 4

qemu-kvm-ev update
by Neil Wilson 26 Apr '17

26 Apr '17

How long does last week's security update remain in the test repo before it gets moved to release? Rgs Neil Wilson

2 1

Issues with exposing USB serial dongle to guest VM
by Philip Prindeville 25 Apr '17

25 Apr '17

Hi. I have Centos 7 (updated) running as my host, and I’m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn’t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though 3 are configured). So the USB CF card readers are visible, but not the USB dongle, even though it’s plugged in. Here’s what I see on the host: [philipp@kvm1 ~]$ ps -f -p13468 UID PID PPID C STIME TTY TIME CMD qemu 13468 1 2 14:51 ? 00:02:39 /usr/libexec/qemu-kvm -name guest=ubuntu16.04-2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Broadwell,+vme,+ds,+acpi,+ss,+ht,+tm,+pbe,+dtes64,+monitor,+ds_cpl,+vmx,+smx,+est,+tm2,+xtpr,+pdcm,+dca,+osxsave,+f16c,+rdrand,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm,+rtm,+hle -m 8192 -realtime mlock=off -smp 8,maxcpus=12,sockets=12,cores=1,threads=1 -uuid a9590ac8-e532-4dce-b6ef-d3b35c0db865 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x5 -device ich9-usb-ehci1,id=usb1,bus=pci.0,addr=0xa.0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/ubuntu16.04-2.img,format=raw,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device usb-host,hostbus=3,hostaddr=13,id=hostdev1,bus=usb.0,port=3 -device usb-host,hostbus=3,hostaddr=12,id=hostdev2,bus=usb.0,port=4 -device usb-host,hostbus=3,hostaddr=15,id=hostdev3,bus=usb1.0,port=1 -device vfio-pci,host=07:10.0,id=hostdev0,bus=pci.0,addr=0x3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on [philipp@kvm1 ~]$ sudo lsof -p 13468 -n -P COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME qemu-kvm 13468 qemu cwd DIR 253,0 242 64 / qemu-kvm 13468 qemu rtd DIR 253,0 242 64 / qemu-kvm 13468 qemu txt REG 253,0 8883768 100834619 /usr/libexec/qemu-kvm qemu-kvm 13468 qemu mem REG 253,0 19984 34091991 /usr/lib64/sasl2/libplain.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 19984 34091988 /usr/lib64/sasl2/liblogin.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 57888 33916680 /usr/lib64/sasl2/libdigestmd5.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 24160 33916677 /usr/lib64/sasl2/libcrammd5.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 1846280 100701718 /usr/lib64/libdb-5.3.so qemu-kvm 13468 qemu mem REG 253,0 28200 33627120 /usr/lib64/sasl2/libsasldb.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 19952 33627117 /usr/lib64/sasl2/libanonymous.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 62184 100664409 /usr/lib64/libnss_files-2.17.so qemu-kvm 13468 qemu mem REG 253,0 68192 100701681 /usr/lib64/libbz2.so.1.0.6 qemu-kvm 13468 qemu mem REG 253,0 99952 100701712 /usr/lib64/libelf-0.166.so qemu-kvm 13468 qemu mem REG 253,0 398264 100701630 /usr/lib64/libpcre.so.1.2.0 qemu-kvm 13468 qemu mem REG 253,0 28360 100702508 /usr/lib64/libogg.so.0.8.0 qemu-kvm 13468 qemu mem REG 253,0 189256 100882393 /usr/lib64/libvorbis.so.0.4.6 qemu-kvm 13468 qemu mem REG 253,0 2944120 100882395 /usr/lib64/libvorbisenc.so.2.0.9 qemu-kvm 13468 qemu mem REG 253,0 285608 100882391 /usr/lib64/libFLAC.so.8.3.0 qemu-kvm 13468 qemu mem REG 253,0 48848 100960245 /usr/lib64/libgsm.so.1.0.12 qemu-kvm 13468 qemu mem REG 253,0 113584 100664401 /usr/lib64/libnsl-2.17.so qemu-kvm 13468 qemu mem REG 253,0 157424 100701670 /usr/lib64/liblzma.so.5.2.2 qemu-kvm 13468 qemu mem REG 253,0 65648 101002376 /usr/lib64/libXi.so.6.1.0 qemu-kvm 13468 qemu mem REG 253,0 75848 101002374 /usr/lib64/libXext.so.6.4.0 qemu-kvm 13468 qemu mem REG 253,0 15512 100984172 /usr/lib64/libXau.so.6.0.0 qemu-kvm 13468 qemu mem REG 253,0 301576 100701829 /usr/lib64/libdw-0.166.so qemu-kvm 13468 qemu mem REG 253,0 155744 100701646 /usr/lib64/libselinux.so.1 qemu-kvm 13468 qemu mem REG 253,0 15624 100701842 /usr/lib64/libgmodule-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 32304 100701834 /usr/lib64/libffi.so.6.0.1 qemu-kvm 13468 qemu mem REG 253,0 11384 100667805 /usr/lib64/libfreebl3.so qemu-kvm 13468 qemu mem REG 253,0 23824 101229361 /usr/lib64/libasyncns.so.0.3.1 qemu-kvm 13468 qemu mem REG 253,0 378904 100960252 /usr/lib64/libsndfile.so.1.0.25 qemu-kvm 13468 qemu mem REG 253,0 42520 100702401 /usr/lib64/libwrap.so.0.7.6 qemu-kvm 13468 qemu mem REG 253,0 24104 101002378 /usr/lib64/libXtst.so.6.1.0 qemu-kvm 13468 qemu mem REG 253,0 32312 100826893 /usr/lib64/libSM.so.6.0.1 qemu-kvm 13468 qemu mem REG 253,0 100472 100826878 /usr/lib64/libICE.so.6.3.0 qemu-kvm 13468 qemu mem REG 253,0 141080 101002368 /usr/lib64/libxcb.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 1318920 101002372 /usr/lib64/libX11.so.6.3.0 qemu-kvm 13468 qemu mem REG 253,0 6848 101002370 /usr/lib64/libX11-xcb.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 15688 100702424 /usr/lib64/libkeyutils.so.1.5 qemu-kvm 13468 qemu mem REG 253,0 62744 100667837 /usr/lib64/libkrb5support.so.0.1 qemu-kvm 13468 qemu mem REG 253,0 19384 100701739 /usr/lib64/libgpg-error.so.0.10.0 qemu-kvm 13468 qemu mem REG 253,0 48672 100984118 /usr/lib64/libunwind.so.8.0.1 qemu-kvm 13468 qemu mem REG 253,0 285296 100702506 /usr/lib64/libjpeg.so.62.1.0 qemu-kvm 13468 qemu mem REG 253,0 334904 100701844 /usr/lib64/libgobject-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 1595056 100701838 /usr/lib64/libgio-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 62688 100882399 /usr/lib64/libcelt051.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 139008 100664438 /usr/lib64/libnl-3.so.200.23.0 qemu-kvm 13468 qemu mem REG 253,0 444832 100664446 /usr/lib64/libnl-route-3.so.200.23.0 qemu-kvm 13468 qemu mem REG 253,0 494440 100702458 /usr/lib64/libgmp.so.10.2.0 qemu-kvm 13468 qemu mem REG 253,0 160776 100702524 /usr/lib64/libhogweed.so.2.5 qemu-kvm 13468 qemu mem REG 253,0 82176 100702502 /usr/lib64/libtasn1.so.6.2.3 qemu-kvm 13468 qemu mem REG 253,0 465360 101027983 /usr/lib64/libtspi.so.1.2.0 qemu-kvm 13468 qemu mem REG 253,0 290864 100702407 /usr/lib64/libp11-kit.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 41080 100664395 /usr/lib64/libcrypt-2.17.so qemu-kvm 13468 qemu mem REG 253,0 111080 100664419 /usr/lib64/libresolv-2.17.so qemu-kvm 13468 qemu mem REG 253,0 20024 100701747 /usr/lib64/libcap.so.2.22 qemu-kvm 13468 qemu mem REG 253,0 304576 100701679 /usr/lib64/libdbus-1.so.3.7.4 qemu-kvm 13468 qemu mem REG 253,0 502608 375140 /usr/lib64/pulseaudio/libpulsecommon-6.0.so qemu-kvm 13468 qemu mem REG 253,0 45456 100701728 /usr/lib64/libjson-c.so.2.0.1 qemu-kvm 13468 qemu mem REG 253,0 454008 100702586 /usr/lib64/libssl.so.1.0.1e qemu-kvm 13468 qemu mem REG 253,0 2025760 100702584 /usr/lib64/libcrypto.so.1.0.1e qemu-kvm 13468 qemu mem REG 253,0 19888 100701744 /usr/lib64/libattr.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 15608 100702497 /usr/lib64/libboost_system-mt.so.1.53.0 qemu-kvm 13468 qemu mem REG 253,0 94320 100702518 /usr/lib64/libboost_thread-mt.so.1.53.0 qemu-kvm 13468 qemu mem REG 253,0 344280 100868642 /usr/lib64/libldap-2.4.so.2.10.3 qemu-kvm 13468 qemu mem REG 253,0 61872 100868640 /usr/lib64/liblber-2.4.so.2.10.3 qemu-kvm 13468 qemu mem REG 253,0 15848 100701657 /usr/lib64/libcom_err.so.2.1 qemu-kvm 13468 qemu mem REG 253,0 202568 100667824 /usr/lib64/libk5crypto.so.3.1 qemu-kvm 13468 qemu mem REG 253,0 959008 100667833 /usr/lib64/libkrb5.so.3.3 qemu-kvm 13468 qemu mem REG 253,0 324888 100667817 /usr/lib64/libgssapi_krb5.so.2.2 qemu-kvm 13468 qemu mem REG 253,0 19776 100664397 /usr/lib64/libdl-2.17.so qemu-kvm 13468 qemu mem REG 253,0 251784 101017300 /usr/lib64/libnspr4.so qemu-kvm 13468 qemu mem REG 253,0 20048 101017301 /usr/lib64/libplc4.so qemu-kvm 13468 qemu mem REG 253,0 15744 101017302 /usr/lib64/libplds4.so qemu-kvm 13468 qemu mem REG 253,0 186216 100706671 /usr/lib64/libnssutil3.so qemu-kvm 13468 qemu mem REG 253,0 1236840 100702603 /usr/lib64/libnss3.so qemu-kvm 13468 qemu mem REG 253,0 164040 100702605 /usr/lib64/libsmime3.so qemu-kvm 13468 qemu mem REG 253,0 315080 101072314 /usr/lib64/libssl3.so qemu-kvm 13468 qemu mem REG 253,0 208920 100701832 /usr/lib64/libidn.so.11.6.11 qemu-kvm 13468 qemu mem REG 253,0 534768 100667864 /usr/lib64/libgcrypt.so.11.8.2 qemu-kvm 13468 qemu mem REG 253,0 2118128 100664059 /usr/lib64/libc-2.17.so qemu-kvm 13468 qemu mem REG 253,0 143944 100664417 /usr/lib64/libpthread-2.17.so qemu-kvm 13468 qemu mem REG 253,0 88720 100663365 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 qemu-kvm 13468 qemu mem REG 253,0 1141928 100664399 /usr/lib64/libm-2.17.so qemu-kvm 13468 qemu mem REG 253,0 999944 100667871 /usr/lib64/libstdc++.so.6.0.19 qemu-kvm 13468 qemu mem REG 253,0 44448 100664421 /usr/lib64/librt-2.17.so qemu-kvm 13468 qemu mem REG 253,0 6944 100701846 /usr/lib64/libgthread-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 305168 100984122 /usr/lib64/libtcmalloc.so.4.2.6 qemu-kvm 13468 qemu mem REG 253,0 31904 100827014 /usr/lib64/libusbredirparser.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 99528 100826629 /usr/lib64/libusb-1.0.so.0.1.0 qemu-kvm 13468 qemu mem REG 253,0 1287896 100701840 /usr/lib64/libglib-2.0.so.0.4600.2 qemu-kvm 13468 qemu mem REG 253,0 49800 100702607 /usr/lib64/libcacard.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 1230208 100749039 /usr/lib64/libspice-server.so.1.10.1 qemu-kvm 13468 qemu mem REG 253,0 80096 101153158 /usr/lib64/libibverbs.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 92032 101153164 /usr/lib64/librdmacm.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 266680 100984135 /usr/lib64/libseccomp.so.2.3.1 qemu-kvm 13468 qemu mem REG 253,0 23800 100826840 /usr/lib64/libsnappy.so.1.1.4 qemu-kvm 13468 qemu mem REG 253,0 135112 100702462 /usr/lib64/liblzo2.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 1292416 101027989 /usr/lib64/libgnutls.so.28.41.16 qemu-kvm 13468 qemu mem REG 253,0 201296 100702526 /usr/lib64/libnettle.so.4.7 qemu-kvm 13468 qemu mem REG 253,0 121296 100701724 /usr/lib64/libsasl2.so.3.0.0 qemu-kvm 13468 qemu mem REG 253,0 179296 100768842 /usr/lib64/libpng15.so.15.13.0 qemu-kvm 13468 qemu mem REG 253,0 320984 101017286 /usr/lib64/libpulse.so.0.18.0 qemu-kvm 13468 qemu mem REG 253,0 1033536 100826787 /usr/lib64/libasound.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 50712 100702422 /usr/lib64/libnuma.so.1 qemu-kvm 13468 qemu mem REG 253,0 14872 100664425 /usr/lib64/libutil-2.17.so qemu-kvm 13468 qemu mem REG 253,0 698744 100826854 /usr/lib64/libpixman-1.so.0.34.0 qemu-kvm 13468 qemu mem REG 253,0 174088 100826406 /usr/lib64/libssh2.so.1.0.1 qemu-kvm 13468 qemu mem REG 253,0 20040 100706670 /usr/lib64/libuuid.so.1.3.0 qemu-kvm 13468 qemu mem REG 253,0 99304 100794835 /usr/lib64/libgfxdr.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 115088 100794833 /usr/lib64/libgfrpc.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 896344 100794837 /usr/lib64/libglusterfs.so.0.0.1 qemu-kvm 13468 qemu mem REG 253,0 150056 100826654 /usr/lib64/libgfapi.so.0.0.0 qemu-kvm 13468 qemu mem REG 253,0 37056 100701754 /usr/lib64/libacl.so.1.1.0 qemu-kvm 13468 qemu mem REG 253,0 5342808 100841989 /usr/lib64/librados.so.2.0.0 qemu-kvm 13468 qemu mem REG 253,0 5789632 100768762 /usr/lib64/librbd.so.1.0.0 qemu-kvm 13468 qemu mem REG 253,0 435120 100842007 /usr/lib64/libcurl.so.4.3.0 qemu-kvm 13468 qemu mem REG 253,0 125336 33843740 /usr/lib64/iscsi/libiscsi.so.2.0.10900 qemu-kvm 13468 qemu mem REG 253,0 6264 100702465 /usr/lib64/libaio.so.1.0.1 qemu-kvm 13468 qemu mem REG 253,0 90664 100701649 /usr/lib64/libz.so.1.2.7 qemu-kvm 13468 qemu mem REG 253,0 155464 100664052 /usr/lib64/ld-2.17.so qemu-kvm 13468 qemu mem REG 0,9 6936 anon_inode:[vfio-device] (stat: No such file or directory) qemu-kvm 13468 qemu mem REG 253,0 162552 100706665 /usr/lib64/libsystemd.so.0.6.0 qemu-kvm 13468 qemu mem REG 253,0 83208 100706667 /usr/lib64/libudev.so.1.6.2 qemu-kvm 13468 qemu DEL REG 0,4 37202 /dev/zero qemu-kvm 13468 qemu DEL REG 0,4 37201 /dev/zero qemu-kvm 13468 qemu mem REG 0,18 4024 38290 /dev/shm/spice.13468 qemu-kvm 13468 qemu DEL REG 0,4 38287 /dev/zero qemu-kvm 13468 qemu 0u CHR 1,3 0t0 1028 /dev/null qemu-kvm 13468 qemu 1w FIFO 0,8 0t0 45255 pipe qemu-kvm 13468 qemu 2w FIFO 0,8 0t0 45255 pipe qemu-kvm 13468 qemu 3r CHR 1,9 0t0 1033 /dev/urandom qemu-kvm 13468 qemu 4u a_inode 0,9 0 6936 [signalfd] qemu-kvm 13468 qemu 5u a_inode 0,9 0 6936 [eventpoll] qemu-kvm 13468 qemu 6u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 7u a_inode 0,9 0 6936 [eventpoll] qemu-kvm 13468 qemu 8u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 9u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 10u unix 0xffff88102b7c1000 0t0 38284 /var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock qemu-kvm 13468 qemu 11u CHR 5,2 0t0 1158 /dev/ptmx qemu-kvm 13468 qemu 12u CHR 10,232 0t0 12724 /dev/kvm qemu-kvm 13468 qemu 13u a_inode 0,9 0 6936 kvm-vm qemu-kvm 13468 qemu 14u unix 0xffff88102b7c3c00 0t0 38288 socket qemu-kvm 13468 qemu 15u unix 0xffff88102b7c2800 0t0 38289 socket qemu-kvm 13468 qemu 16u REG 0,18 4024 38290 /dev/shm/spice.13468 qemu-kvm 13468 qemu 17u IPv4 38293 0t0 TCP 127.0.0.1:5900 (LISTEN) qemu-kvm 13468 qemu 18u REG 253,1 171825168384 1074520646 /var/lib/libvirt/images/ubuntu16.04-2.img qemu-kvm 13468 qemu 19u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 20u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 21u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 22u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 23u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 24u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 25u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 26u a_inode 0,9 0 6936 kvm-vcpu qemu-kvm 13468 qemu 27u unix 0xffff881026898000 0t0 40135 socket qemu-kvm 13468 qemu 28u unix 0xffff88102689f400 0t0 40136 socket qemu-kvm 13468 qemu 29u netlink 0t0 40137 KOBJECT_UEVENT qemu-kvm 13468 qemu 30r FIFO 0,8 0t0 40138 pipe qemu-kvm 13468 qemu 31w FIFO 0,8 0t0 40138 pipe qemu-kvm 13468 qemu 32r FIFO 0,8 0t0 40139 pipe qemu-kvm 13468 qemu 33w FIFO 0,8 0t0 40139 pipe qemu-kvm 13468 qemu 34u a_inode 0,9 0 6936 [timerfd] qemu-kvm 13468 qemu 35u CHR 245,0 0t0 22111 /dev/vfio/30 qemu-kvm 13468 qemu 36u CHR 10,196 0t0 11903 /dev/vfio/vfio qemu-kvm 13468 qemu 37u a_inode 0,9 0 6936 kvm-vfio qemu-kvm 13468 qemu 38u a_inode 0,9 0 6936 [vfio-device] qemu-kvm 13468 qemu 39u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 40u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 41u unix 0xffff88102de37000 0t0 40140 /var/lib/libvirt/qemu/domain-2-ubuntu16.04-2/monitor.sock qemu-kvm 13468 qemu 42u CHR 189,268 0t0 11444 /dev/bus/usb/003/013 qemu-kvm 13468 qemu 43u CHR 189,267 0t0 11441 /dev/bus/usb/003/012 qemu-kvm 13468 qemu 44u unix 0xffff88102d675c00 0t0 47483 socket qemu-kvm 13468 qemu 45u unix 0xffff88102689a400 0t0 40142 socket qemu-kvm 13468 qemu 46u unix 0xffff88102d674400 0t0 47488 socket qemu-kvm 13468 qemu 47u unix 0xffff880e32a7a400 0t0 44457 socket qemu-kvm 13468 qemu 48u unix 0xffff88102b200c00 0t0 45264 socket qemu-kvm 13468 qemu 49u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 50u unix 0xffff8810392a1000 0t0 22123 socket qemu-kvm 13468 qemu 51u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 52u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 53u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 54u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 55u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 56u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 57u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 58u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 59u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 60u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 61u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 62u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 63u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 64u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 65u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 66u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 67u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 68u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 69u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 70u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 71u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 72u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 73u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 74u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 75u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 76u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 77u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 78u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 79u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 80u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 81u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 82u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 83u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 84u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 85u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 86u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 87u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 88u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 89u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 90u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 91u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 92u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 93u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 94u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 95u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 96u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 97u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 98u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 99u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 100u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 101u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 102u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 103u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 104u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 105u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 106u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 107u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 108u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 109u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 110u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 111u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 112u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 113u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 114u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 115u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 116u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 117u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 118u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 119u a_inode 0,9 0 6936 [eventfd] qemu-kvm 13468 qemu 120u a_inode 0,9 0 6936 [eventfd] [philipp@kvm1 ~]$ lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 1058:25da Western Digital Technologies, Inc. Bus 004 Device 002: ID 2109:8110 VIA Labs, Inc. Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 0557:2419 ATEN International Co., Ltd Bus 003 Device 004: ID 0557:7000 ATEN International Co., Ltd Hub Bus 003 Device 015: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 013: ID 05dc:ba04 Lexar Media, Inc. Bus 003 Device 012: ID 0bda:0309 Realtek Semiconductor Corp. Bus 003 Device 009: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 003 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 011: ID 045e:000b Microsoft Corp. Natural Keyboard Elite Bus 003 Device 010: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 003 Device 008: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 003 Device 005: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 002: ID 2109:2811 VIA Labs, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [philipp@kvm1 ~]$ sudo cat /etc/libvirt/qemu/ubuntu16.04-2.xml  <domain type='kvm'> <name>ubuntu16.04-2</name> <uuid>a9590ac8-e532-4dce-b6ef-d3b35c0db865</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static' current='8'>12</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.3.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-model'> <model fallback='allow'/> </cpu> <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/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/ubuntu16.04-2.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' 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='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='0x06' function='0x0'/> </controller> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='1' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x7'/> </controller> <interface type='network'> <mac address='52:54:00:fc:0f:5e'/> <source network='hostdev-net0'/> <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='spice' autoport='yes'> <listen type='address'/> <image compression='off'/> </graphics> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <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> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x05dc'/> <product id='0xba04'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0bda'/> <product id='0x0309'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x067b'/> <product id='0x2303'/> </source> <address type='usb' bus='1' port='1'/> </hostdev> <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='0x08' function='0x0'/> </memballoon> </devices> </domain> [philipp@kvm1 ~]$ and here’s what I see on the guest: philipp@ubuntu16:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0309 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05dc:ba04 Lexar Media, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub philipp@ubuntu16:~$ I’m not sure what I’m missing. How do I verify that the parameters in the .xml domain definition are correct, and that they’re resulting in the correct args being passed to qemu-kvm when it gets exec’d? And why do the args: -device usb-host,hostbus=3,hostaddr=15,id=hostdev3,bus=usb1.0,port=1 seem to be silently ignored? I understand that USB is inherently pluggable and hence the device may or may not be present at the time that Qemu gets kicked off… Looking at https://github.com/esminc/qemu/blob/master/Source/device-qemu/android/andro… it claims that the PL2303 driver is supported. What am I missing? I need to access serial ports from several of my guest VMs, and my host doesn’t have built-in serial ports to USB dongles are my only option. Thanks, -Philip

1 0

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
by Anderson, Dave 21 Apr '17

21 Apr '17

List moderator: feel free to delete my previous large message with attachments that's in the moderation queue...it's now obsolete anyway. I have found a fix/workaround for my reboot issues with Xen 4.6.3-12 + Kernel 4.9.13: Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace: [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0 APIC: 7 installing Xen timer for CPU 8 [Firmware Bug]: CPU8: APIC id mismatch. Firmware: 0 APIC: 20 smpboot: Package 1 of CPU 8 exceeds BIOS package data 1. ------------[ cut here ]------------ kernel BUG at arch/x86/kernel/cpu/common.c:997! invalid opcode: 0000 [#1] SMP Modules linked in: CPU: 8 PID: 0 Comm: swapper/8 Not tainted 4.9.13-22.el7.x86_64 #1 Hardware name: Supermicro X9DRT/X9DRT, BIOS 3.2a 08/04/2015 random: fast init done task: ffff880058a8c4c0 task.stack: ffffc900400b4000 RIP: e030:[<ffffffff8103e527>] [<ffffffff8103e527>] identify_secondary_cpu+0x57/0x80 RSP: e02b:ffffc900400b7f08 EFLAGS: 00010086 RAX: 00000000ffffffe4 RBX: ffff88005d80a020 RCX: ffffffff81c5be68 RDX: 0000000000000001 RSI: 0000000000000005 RDI: 0000000000000005 RBP: ffffc900400b7f18 R08: 00000000000000cb R09: 0000000000000004 R10: 0000000000000000 R11: 0000000000000006 R12: 0000000000000008 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88005d800000(0000) knlGS:0000000000000000 CS: e033 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000001c07000 CR4: 0000000000042660 Stack: 0000000000000008 0000000000000000 ffffc900400b7f28 ffffffff8104e94e ffffc900400b7f40 ffffffff81029925 0000000000000000 ffffc900400b7f50 ffffffff810299a0 0000000000000000 0000000000000000 0000000000000000 Call Trace: [<ffffffff8104e94e>] smp_store_cpu_info+0x3e/0x40 [<ffffffff81029925>] cpu_bringup+0x35/0x90 [<ffffffff810299a0>] cpu_bringup_and_idle+0x20/0x40 Code: 44 89 e7 ff 50 68 0f b7 93 d2 00 00 00 39 d0 75 1c 0f b7 bb da 00 00 00 44 89 e6 e8 24 03 01 00 85 c0 75 07 5b 41 5c 5d c3 0f 0b <0f> 0b 0f b7 8b d4 00 00 00 89 c2 44 89 e6 48 c7 c7 98 87 a6 81 RIP [<ffffffff8103e527>] identify_secondary_cpu+0x57/0x80 RSP <ffffc900400b7f08> ---[ end trace dc5563100443876e ]--- I surmised that reducing the number of dom0 vcpu might solve this issue (they were unbounded) In testing adding "dom0_max_vcpus=4 dom0_vcpus_pin" to the GRUB_CMDLINE_XEN_DEFAULT line in /etc/defaults/grub and re-running grub2-mkconfig has resulted in the system I have that never booted Xen 4.6.3-12 + Kernel 4.9.13, booting every single time out of 5-10 tests. So...I don't know if there's a race condition somewhere, or what...but...so far this workaround has not failed me. Thanks, -Dave > On Fri, Apr 7, 2017 at 6:58 AM, PJ Welsh <pjwelsh at gmail.com >> wrote: >> I've not gotten any bites from my posting on the xen-devel mailing list. >> Here is the only one to-date: >> https://lists.xen.org/archives/html/xen-devel/2017-04/msg01069.html >> >> From that email, there needs to be some hypervisor messages. >> >> Does anyone know how to produce the hypervisor messages? I've already > >> removed the rhgb and quiet options from the boot. > >> >> Thanks >> PJ > > > I spoke too soon. To get more information: Please see > > https://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen_Project > > and > > https://wiki.xenproject.org/wiki/Xen_Serial_Console > > or alternatively at least add "vga=keep". > > pjwelsh

5 17

qemu-kvm-ev-2.6.0-28.el7_3.9.1 now available for testing
by Sandro Bonazzola 20 Apr '17

20 Apr '17

Hi, just pushed to testing a new build of qemu-kvm-ev, here's the ChangeLog: * Thu Apr 20 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.6.0-28.el7_3.9.1 - Removing RH branding from package name * Fri Mar 24 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.9 - kvm-block-gluster-memory-usage-use-one-glfs-instance-per.patch [bz#1413044] - kvm-gluster-Fix-use-after-free-in-glfs_clear_preopened.patch [bz#1413044] - kvm-fix-cirrus_vga-fix-OOB-read-case-qemu-Segmentation-f.patch [bz#1430061] - kvm-cirrus-vnc-zap-bitblit-support-from-console-code.patch [bz#1430061] - kvm-cirrus-add-option-to-disable-blitter.patch [bz#1430061] - kvm-cirrus-fix-cirrus_invalidate_region.patch [bz#1430061] - kvm-cirrus-stop-passing-around-dst-pointers-in-the-blitt.patch [bz#1430061] - kvm-cirrus-stop-passing-around-src-pointers-in-the-blitt.patch [bz#1430061] - kvm-cirrus-fix-off-by-one-in-cirrus_bitblt_rop_bkwd_tran.patch [bz#1430061] - kvm-file-posix-Consider-max_segments-for-BlockLimits.max.patch [bz#1431149] - kvm-file-posix-clean-up-max_segments-buffer-termination.patch [bz#1431149] - kvm-file-posix-Don-t-leak-fd-in-hdev_get_max_segments.patch [bz#1431149] - Resolves: bz#1413044 (block-gluster: use one glfs instance per volume) - Resolves: bz#1430061 (CVE-2016-9603 qemu-kvm-rhev: Qemu: cirrus: heap buffer overflow via vnc connection [rhel-7.3.z]) - Resolves: bz#1431149 (VMs pause when writing to Virtio-SCSI direct lun with scsi passthrough enabled via an Emulex HBA) * Tue Mar 21 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.8 - kvm-target-i386-present-virtual-L3-cache-info-for-vcpus.patch [bz#1430802] - Resolves: bz#1430802 (Enhance qemu to present virtual L3 cache info for vcpus) * Wed Mar 15 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.7 - kvm-block-check-full-backing-filename-when-searching-pro.patch [bz#1425125] - kvm-qemu-iotests-Don-t-create-fifos-pidfiles-with-protoc.patch [bz#1425125] - kvm-qemu-iotest-test-to-lookup-protocol-based-image-with.patch [bz#1425125] - kvm-target-i386-Don-t-use-cpu-migratable-when-filtering-.patch [bz#1413897] - Resolves: bz#1413897 (cpu flag nonstop_tsc is not present in guest with host-passthrough and feature policy require invtsc) - Resolves: bz#1425125 (qemu fails to recognize gluster URIs in backing chain for block-commit operation) In order to test it: # yum install centos-release-qemu-ev # yum-config-manager --enable centos-qemu-ev-test # yum install qemu-kvm-ev Or just yum update if you already have qemu-kvm-ev installed and test repository enabled. If you test it, please provide feedback. I'm going to release it on April 26th if no negative feedback is provided. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

qemu-kvm-ev ppc64le release builds
by Lance Albertson 20 Apr '17

20 Apr '17

Hi, We're using qemu-kvm-ev on ppc64le and I've noticed that it's included in the extras repo for ppc64le but in the qemu-kvm-ev repo for x86_64. I also noticed the version in ppc64le is lagging behind x86. I see that ppc64le is being built for this, however isn't tagged for virt7-kvm-common-release and thus showing up under /virt/kvm-common on the mirrors. Is there any particular reason why this is happening? If possible, I can certainly provide some testing to get this moving along. Thank you! [1] http://cbs.centos.org/koji/packageinfo?packageID=539 -- Lance Albertson Director Oregon State University | Open Source Lab

2 1

Testing kernel crash: 4.9.23-26.el6.x86_64
by Piotr Gackiewicz 20 Apr '17

20 Apr '17

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules linked in: xt_physdev br_netfilter xt_mac ebt_arp xen_pciback xen_gntalloc ebtable_filter ebtables bridge 8021q mrp garp stp llc xt_CT xt_addrtype iptable_raw nf_log_ ipv4 nf_log_common xt_LOG xt_limit xt_owner iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_sta te nf_conntrack ip6table_filter ip6_tables blktap xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd ppdev parport_pc parport fjes 3c59x asus_atk0110 pcspkr serio_raw k8temp vi a_rhine mii i2c_viapro shpchp raid1 pata_via pata_acpi ata_generic sata_via [59826.069842] CPU: 0 PID: 32443 Comm: sshd Not tainted 4.9.23-26.el6.x86_64 #1 [59826.069860] Hardware name: System manufacturer System Product Name/K8V-VM, BIOS 0201 06/13/2006 [59826.069882] task: ffff880014c8c900 task.stack: ffffc90043820000 [59826.069896] RIP: e030:[<ffffffff812405d6>] [<ffffffff812405d6>] kmem_cache_alloc_node+0xa6/0x1c0 [59826.070019] RSP: e02b:ffffc90043823b08 EFLAGS: 00010246 [59826.070019] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000ec741e [59826.070019] RDX: 0000000000ec741d RSI: 00000000024000c0 RDI: ffff0000ffff0000 [59826.070019] RBP: ffffc90043823b68 R08: 000000000001cd00 R09: 0000000000000000 [59826.070019] R10: 0000000000007ff0 R11: ffffc900407ebe88 R12: ffff88001a8013c0 [59826.070019] R13: ffff88001a8013c0 R14: 00000000ffffffff R15: 00000000024000c0 [59826.070019] FS: 00007f652071e7c0(0000) GS:ffff88001f800000(0000) knlGS:0000000000000000 [59826.070019] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [59826.070019] CR2: 00007fff0870ad60 CR3: 000000000f940000 CR4: 0000000000000660 [59826.070019] Stack: [59826.070019] ffffc90043823b38 ffffffff818d5e36 ffff880016711758 ffffffff81792687 [59826.070019] ffff880015d1ec10 ffff880015d1ec00 ffffc90043823c38 ffff880015d1ec00 [59826.070019] 00000000024000c0 00000000ffffffff ffff88001a8013c0 0000000000000024 [59826.070019] Call Trace: [59826.070019] [<ffffffff818d5e36>] ? mutex_lock+0x16/0x40 [59826.070019] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.070019] [<ffffffff81792687>] __alloc_skb+0x57/0x200 [59826.070019] [<ffffffff817e2af0>] ? netlink_attachskb+0x1b0/0x1b0 [59826.070019] [<ffffffff817df900>] ? netlink_overrun+0x50/0x50 [59826.070019] [<ffffffff817e319c>] netlink_ack+0x6c/0x170 [59826.070019] [<ffffffff8115526b>] audit_receive+0x8b/0xa0 [59826.070019] [<ffffffff817e30aa>] netlink_unicast+0x19a/0x220 [59826.070019] [<ffffffff817e3ed2>] netlink_sendmsg+0x302/0x380 [59826.070019] [<ffffffff81787ba9>] sock_sendmsg+0x49/0x60 [59826.070019] [<ffffffff8178a006>] SYSC_sendto+0x116/0x170 [59826.070019] [<ffffffff81287efc>] ? __alloc_fd+0x4c/0x1b0 [59826.070019] [<ffffffff810033c1>] ? syscall_trace_enter+0x201/0x2c0 [59826.070019] [<ffffffff8115b199>] ? __audit_syscall_exit+0x229/0x2b0 [59826.070019] [<ffffffff8178a06e>] SyS_sendto+0xe/0x10 [59826.070019] [<ffffffff81003e7a>] do_syscall_64+0x7a/0x240 [59826.070019] [<ffffffff8106f1a7>] ? do_page_fault+0x37/0x90 [59826.070019] [<ffffffff818d83eb>] entry_SYSCALL64_slow_path+0x25/0x25 [59826.070019] Code: e8 36 41 39 c6 74 17 48 8b 4d b8 44 89 f2 44 89 fe 4c 89 e7 e8 2c f7 ff ff 48 89 c3 eb 2c 49 63 44 24 20 4d 8b 04 24 48 8d 4a 01 <48> 8b 1c 07 48 89 f8 49 8d 30 e8 eb b 4 1e 00 3c 01 75 95 49 63 [59826.070019] RIP [<ffffffff812405d6>] kmem_cache_alloc_node+0xa6/0x1c0 [59826.070019] RSP <ffffc90043823b08> [59826.076823] general protection fault: 0000 [#2] SMP [59826.077009] Modules linked in: xt_physdev br_netfilter xt_mac ebt_arp xen_pciback xen_gntalloc ebtable_filter ebtables bridge 8021q mrp garp stp llc xt_CT xt_addrtype iptable_raw nf_log_ ipv4 nf_log_common xt_LOG xt_limit xt_owner iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_sta te nf_conntrack ip6table_filter ip6_tables blktap xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd ppdev parport_pc parport fjes 3c59x asus_atk0110 pcspkr serio_raw k8temp vi a_rhine mii i2c_viapro shpchp raid1 pata_via pata_acpi ata_generic sata_via [59826.077733] CPU: 0 PID: 32443 Comm: sshd Tainted: G D 4.9.23-26.el6.x86_64 #1 [59826.077733] Hardware name: System manufacturer System Product Name/K8V-VM, BIOS 0201 06/13/2006 [59826.077733] task: ffff880014c8c900 task.stack: ffffc90043820000 [59826.077733] RIP: e030:[<ffffffff81241ad5>] [<ffffffff81241ad5>] kmem_cache_alloc+0x85/0x1b0 [59826.077733] RSP: e02b:ffff88001f803ba8 EFLAGS: 00010286 [59826.077733] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000ec741e [59826.077733] RDX: 0000000000ec741d RSI: 0000000002080020 RDI: 000000000001cd00 [59826.077733] RBP: ffff88001f803bf8 R08: ffff88001f81cd00 R09: ffff0000ffff0000 [59826.077733] R10: 0000000000000003 R11: 0000000000000000 R12: ffff88001a8013c0 [59826.077733] R13: ffff88001a8013c0 R14: ffffffff8179240e R15: 0000000002080020 [59826.077733] FS: 00007f652071e7c0(0000) GS:ffff88001f800000(0000) knlGS:0000000000000000 [59826.077733] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [59826.077733] CR2: 00007fff0870ad60 CR3: 000000000f940000 CR4: 0000000000000660 [59826.077733] Stack: [59826.077733] ffff88001f803bb8 ffffffff81025105 ffff88001f803bc8 ffff88001f816760 [59826.077733] 0000000000000780 0000000000000780 ffff8800144af880 0000000000000000 [59826.077733] 0000000000000200 ffff8800144af880 ffff88001f803c38 ffffffff8179240e [59826.077733] Call Trace: [59826.077733] <IRQ> [59826.077733] [<ffffffff81025105>] ? xen_clocksource_read+0x15/0x20 [59826.077733] [<ffffffff8179240e>] __build_skb+0x2e/0xe0 [59826.077733] [<ffffffff817929fa>] __netdev_alloc_skb+0xda/0x120 [59826.077733] [<ffffffff810d0a5a>] ? activate_task+0x7a/0x90 [59826.077733] [<ffffffffc0027368>] rhine_rx+0x2b8/0x530 [via_rhine] [59826.077733] [<ffffffffc00276be>] rhine_napipoll+0xde/0x190 [via_rhine] [59826.077733] [<ffffffff817abfdb>] napi_poll+0xdb/0x1f0 [59826.077733] [<ffffffff81119aae>] ? process_timeout+0xe/0x10 [59826.077733] [<ffffffff81119732>] ? call_timer_fn+0x42/0x140 [59826.077733] [<ffffffff817ac1b5>] net_rx_action+0xc5/0x240 [59826.077733] [<ffffffff8111b1d6>] ? run_timer_softirq+0x276/0x2c0 [59826.077733] [<ffffffff810d833c>] ? sched_clock_local+0x1c/0x90 [59826.077733] [<ffffffff810d844a>] ? sched_clock_cpu+0x9a/0xb0 [59826.077733] [<ffffffff818db0ce>] __do_softirq+0xce/0x2bf [59826.077733] [<ffffffff810d844a>] ? sched_clock_cpu+0x9a/0xb0 [59826.077733] [<ffffffff810ab1d5>] irq_exit+0x105/0x110 [59826.077733] [<ffffffff8150e3f9>] xen_evtchn_do_upcall+0x39/0x50 [59826.077733] [<ffffffff818d93de>] xen_do_hypervisor_callback+0x1e/0x40 [59826.077733] <EOI> [59826.077733] [<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20 [59826.077733] [<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20 [59826.077733] [<ffffffff81103fff>] ? console_unlock+0x2ff/0x3e0 [59826.077733] [<ffffffff81024c5d>] ? xen_force_evtchn_callback+0xd/0x10 [59826.077733] [<ffffffff810253b6>] ? check_events+0x16/0x30 [59826.077733] [<ffffffff81025393>] ? xen_restore_fl_direct_reloc+0x4/0x4 [59826.077733] [<ffffffff81032b3d>] ? oops_end+0x7d/0xe0 [59826.077733] [<ffffffff81032cab>] ? die+0x5b/0x90 [59826.077733] [<ffffffff81030084>] ? do_general_protection+0xe4/0x170 [59826.077733] [<ffffffff818d97a8>] ? general_protection+0x28/0x30 [59826.077733] [<ffffffff812405d6>] ? kmem_cache_alloc_node+0xa6/0x1c0 [59826.077733] [<ffffffff812406c5>] ? kmem_cache_alloc_node+0x195/0x1c0 [59826.077733] [<ffffffff818d5e36>] ? mutex_lock+0x16/0x40 [59826.077733] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.077733] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.077733] [<ffffffff817e2af0>] ? netlink_attachskb+0x1b0/0x1b0 [59826.077733] [<ffffffff817df900>] ? netlink_overrun+0x50/0x50 [59826.077733] [<ffffffff817e319c>] ? netlink_ack+0x6c/0x170 [59826.077733] [<ffffffff8115526b>] ? audit_receive+0x8b/0xa0 [59826.077733] [<ffffffff817e30aa>] ? netlink_unicast+0x19a/0x220 [59826.077733] [<ffffffff817e3ed2>] ? netlink_sendmsg+0x302/0x380 [59826.077733] [<ffffffff81787ba9>] ? sock_sendmsg+0x49/0x60 [59826.077733] [<ffffffff8178a006>] ? SYSC_sendto+0x116/0x170 [59826.077733] [<ffffffff81287efc>] ? __alloc_fd+0x4c/0x1b0 [59826.077733] [<ffffffff810033c1>] ? syscall_trace_enter+0x201/0x2c0 [59826.077733] [<ffffffff8115b199>] ? __audit_syscall_exit+0x229/0x2b0 [59826.077733] [<ffffffff8178a06e>] ? SyS_sendto+0xe/0x10 [59826.077733] [<ffffffff81003e7a>] ? do_syscall_64+0x7a/0x240 [59826.077733] [<ffffffff8106f1a7>] ? do_page_fault+0x37/0x90 [59826.077733] [<ffffffff818d83eb>] ? entry_SYSCALL64_slow_path+0x25/0x25 [59826.077733] Code: 05 91 86 dc 7e 4d 8b 08 49 8b 40 10 4d 85 c9 0f 84 24 01 00 00 48 85 c0 0f 84 1b 01 00 00 49 63 44 24 20 49 8b 3c 24 48 8d 4a 01 <49> 8b 1c 01 4c 89 c8 48 8d 37 e8 ec 9 f 1e 00 3c 01 75 b6 49 63 [59826.077733] RIP [<ffffffff81241ad5>] kmem_cache_alloc+0x85/0x1b0 [59826.077733] RSP <ffff88001f803ba8> [59826.100347] ---[ end trace 58d7c3379dbe9d6a ]--- [59826.100533] Kernel panic - not syncing: Fatal exception in interrupt [59826.100721] Kernel Offset: disabled (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. Regards, -- Piotr Gackiewicz Intertele S.A. - operator systemów ITL.PL i DOMENY.ITL.PL al. T. Rejtana 10, 35-310 Rzeszów TEL: +48 17 8507580, FAX: +48 17 8520275 http://www.itl.pl - niezawodne usługi hostingowe http://domeny.itl.pl - tanie domeny internetowe http://www.intertele.pl

1 0

virsh error: driver is not whitelisted
by Marco Aurelio L. Gomes 19 Apr '17

19 Apr '17

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <hugepages> <page size='2' unit='M' nodeset='0'/> </hugepages> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <shares>4096</shares> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <emulatorpin cpuset='4,5'/> </cputune> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-model'> <model fallback='allow'/> <topology sockets='2' cores='1' threads='1'/> <numa> <cell id='0' cpus='0-1' memory='4194304' unit='KiB' memAccess='shared'/> </numa> </cpu> <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='/root/cirros-0.3.5-x86_64-disk.img'/> <target dev='vda' bus='virtio'/> </disk> <disk type='dir' device='disk'> <driver name='qemu' type='fat'/> <source dir='/usr/src/dpdk-stable-16.11.1'/> <target dev='vdb' bus='virtio'/> <readonly/> </disk> <interface type='vhostuser'> <mac address='00:00:00:00:00:01'/> <source type='unix' path='/var/run/openvswitch/dpdkvhostuser0' mode='client'/> <model type='virtio'/> <driver queues='2'> <host mrg_rxbuf='off'/> </driver> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> </devices> </domain> When I run: virsh create domain.xml I got the following error: error: Failed to create domain from domain.xml error: internal error: qemu unexpectedly closed the monitor: 2017-04-17T17:00:37.012369Z qemu-kvm: -drive file=fat:/usr/src/dpdk-stable-16.11.1,if=none,id=drive-virtio-disk1,readonly=on: Driver 'vvfat' is not whitelisted If I comment the disk that cause this error, the instance starts without error. Is there a way to whitelist this vvfat driver to instance this VM? And the strange thing about this error is that when I check the available drives, there is vvfat in the list: /usr/libexec/qemu-kvm -drive format=? Supported formats: ftps http null-aio null-co file quorum blkverify vvfat blkreplay qed raw qcow2 bochs dmg vmdk parallels vhdx vpc https sheepdog host_cdrom ssh host_device nbd gluster qcow iscsi rbd tftp ftp vdi blkdebug luks cloop Here some information about the environment: cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) virsh --version 2.0.0 /usr/libexec/qemu-kvm --version QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-28.el7_3.6.1), Copyright (c) 2003-2008 Fabrice Bellard Thanks in advance for the help Marco Aurelio Gomes NCC - UNESP

2 2

Is Xen on CentOS 7 production ready?
by redundantl y 17 Apr '17

17 Apr '17

I see the announcement from February that it's available, but is it considered to be safe for Production use? The documentation in the SIG still only references CentOS 6. https://wiki.centos.org/Manuals/ReleaseNotes/Xen4-01 https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Thanks.

2 2

qemu-kvm-ev 2.6 + libvirtd 3.0
by FeldHost Admin 17 Apr '17

17 Apr '17

Hello, it is safe to use centos 7 qemu-kvm-ev repo with new one for libvirt 3.0 https://cbs.centos.org/repos/virt7-libvirt-latest-release/x86_64/os/Package… Anybody using it? Thanks. -- S pozdravem Kristián Feldsam

1 0

optimal windows xml config for xen
by Christoph 14 Apr '17

14 Apr '17

Hi I use this config to start win7 64bit via virsh: <domain type='xen' id='21'> <name>marax</name> <uuid>6df7f16c-50e1-4541-b5b1-a91ff675a7c2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>8</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib64/xen/boot/hvmloader</loader> <boot dev='cdrom'/> </os> <features> <acpi/> <apic/> <pae/> <viridian/> </features> <clock offset='variable' adjustment='0' basis='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type='block' device='disk'> <driver name='phy'/> <source dev='/dev/vg_lilith/lv_marax_c'/> <backingStore/> <target dev='hda'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='disk'> <driver name='phy'/> <source dev='/dev/vg_lilith/lv_marax_d'/> <backingStore/> <target dev='hdb'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='ide' index='0'/> <interface type='bridge'> <mac address='00:16:3e:05:01:10'/> <source bridge='xenbr5'/> <script path='vif-bridge'/> <model type='e1000'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' port='6000' autoport='no' keymap='de'/> <video> <model type='xen' vram='16384' heads='1'/> </video> </devices> </domain> it is optimal for win7? does someone see any options what I could make better? -- ---------- Greetz Christoph

1 0

Pair-bonding on virtualized servers, particularly on CentOS 7
by Nico Kadel-Garcia 14 Apr '17

14 Apr '17

Is anyone out there using pair-bonding on CentOS 7? I'm particularly looking at systems where one VM network port is tied to one bridge, tied to one port on the hypervisor, and one network port on the VM tied to t he other bridge tied to th e other port on the hypervisor, for failover in a VM that can be exposed directly to the local network. I'm also dealing with pair bonding of they hypervisor, even if the VM's are NAT'ed, and wonder if anyone wants to share testing confgs and notes for CentOS 7. I published notes on KVM bridging, pair bonding, and even tagged VLAN's for CentOS 5 and 6 years ago, but CentOS 7 has proven to be trickier, and I'm wondering if anyone else doing virtualization has spent cycles on this. I think I've gotten the setup on the hypervisor automated, but don't have much space or time to run tests. I'm happy to share tools and access to tools under an open source license.

1 0

Centos 6.9 AWS Images and c4-8xlarge
by John Peacock 14 Apr '17

14 Apr '17

I asked back in September: https://lists.centos.org/pipermail/centos-virt/2016-September/005219.html and again in November: https://lists.centos.org/pipermail/centos-virt/2016-November/005257.html about getting c4.8xlarge enabled for the official image in AWS Marketplace: https://aws.amazon.com/marketplace/pp/B00NQAYLWO?ref=cns_srchrow Now that the 6.9 release is coming, it would be nice to have that last checkbox enabled. We want to be able to usethe 10G networking that c4.8xlarge instances provide and we want to base all of our images directly on the official Centos6 release AMI. Please advise if there is anything I can do to assist in this effort. Thanks John Peacock

4 4

unable to execute QEMU command 'migrate': this feature or command is not currently supported
by Valentin Guggiana 11 Apr '17

11 Apr '17

Hi all I'm trying to do a live migration with non-shared storage on CentOS 7. It was working well doing it from CentOS 6 to CentOS 7 but not between to CentOS 7 machines. I read that this feature was removed in RHEL/CentOS 7 but should be available in the CentOS-QEMU-EV repository. But I still get the error using qemu-kvm-ev: error: internal error: unable to execute QEMU command 'migrate': this feature or command is not currently supported My installed libvirt and qemu packets are: libvirt-2.0.0-10.el7_3.5.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64 libvirt-glib-0.2.3-1.el7.x86_64 libvirt-python-2.0.0-2.el7.x86_64 qemu-img-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-common-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-tools-ev-2.6.0-28.el7_3.6.1.x86_64 My command is: virsh migrate --live --copy-storage-all --persistent --undefinesource --tunnelled --p2p --verbose --xml server.xml server qemu+ssh://xxx@a.b.c.d/system Any help would be greatly appreciated. Thanks, Valentin

3 5

Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
by PJ Welsh 07 Apr '17

07 Apr '17

Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results. Anyone have an idea? The 3.18.x series runs without issue of course. Thanks PJ

8 23

Clocksource boot issues 4.9.13
by Chris Elliott 07 Apr '17

07 Apr '17

Hi all I’ve got a few Intel Z87 chipset machines with Adaptec 5405 raid cards (latest firmware), they work fine on 3.18 but during Dom0 boot using kernel 4.9.13 it hangs at “Using clocksource tsc” and the aacraid driver keeps trying to reset Has anyone seen anything like this? I’ve tried specifying clocksource=xen in grub instead of the default of tsc, and that has the same issue. HPET is enabled and Xen is seeing it: (XEN) ACPI: HPET D9649CB0, 0038 (r1 ALASKA A M I 1072009 AMI. 5) (XEN) Platform timer is 14.318MHz HPET Thanks Chris

4 4

Network isolation for KVM guests
by C. L. Martinez 04 Apr '17

04 Apr '17

Hi all, What options exists under CentOS hosts to work with isolated networks?. For example, on BSD systems it is really trivial. In FreeBSD you can use setfib tools and on OpenBSD it is possible to use rdomain options. In 30 secs it is possible to work with isolated networks and assign process, ip address and routes (hidden from the main route table and ip addresses), etc. But I can't find a similar solution for CentOS environments. I have found two similar options: a/ Network namespaces (but doesn't provides a real network isolation) b/ VRF (but it is supported only for kernels 4.8 and up) Any ideas? Thanks. -- Greetings, C. L. Martinez

6 12

Xen 4.6.3-9 release
by Brandon Shoemaker 03 Apr '17

03 Apr '17

Hi list, Xen 4.6.3-9 will be general release soon?

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt April 2017