- Users - libvirt List Archives

[libvirt-users] How to set QEMU qcow2 l2-cache-size using libvirt xml?
by Frank Myhr 20 Sep '16

20 Sep '16

QEMU's default qcow2 L2 cache size is too small for large images (and small cluster sizes), resulting in very bad performance. https://blogs.igalia.com/berto/2015/12/17/improving-disk-io-performance-in-… shows huge performance hit for a 20GB qcow2 with default 64kB cluster size: L2 Cache, MiB Average IOPS 1 (default) 5100 1.5 7300 2 12700 2.5 63600 The above link also gives the formula: optimal L2 cache size = L2 table size = (8 Byte) * (disk size) / (cluster size) and the QEMU command line for setting L2 cache size, which is not persistent, but must be specified at each invocation: qemu-system-x86_64 -drive file=hd.qcow2,l2-cache-size=2621440 I'd like to set the l2-cache-size in libvirt xml, but cannot make out how to do it. There are only hints in the comments at the above link and at http://wiki.libvirt.org/page/QEMUSwitchToLibvirt and an earlier unanswered question on this list https://www.redhat.com/archives/libvirt-users/2016-February/msg00036.html Has anyone successfully done this, and could you please give an example of the actual libvirt xml used? Thanks! Frank

2 2

[libvirt-users] qemu 2.7 / libvirt 2.2 / iPXE
by Gregory Gincley 17 Sep '16

17 Sep '16

Hi, I've been having some trouble lately with iPXE booting. I'm on Arch Linux vanilla 4.7.4 kernel qemu 2.7 libvirt 2.2.0 virt-manager 1.4.0 Since the upgrade from qemu 2.6.1 to 2.7 a few days ago. I'm no longer able to PXE boot using a bridged network connection. The PXE boot fails using NAT (host only) networking as well, when on a domain thats started by virt-manager, or through virsh. My networking setup is a bridge (br1) (shared device) established by systemd. Another machine on my LAN acts as a tFTP server and my router (tomato) directs all machines to it via this dnsmasq directive: 'dhcp-boot=pxelinux.0,nas,192.168.9.103' I have used this setup for years without issue. All other networking functionality appears to be fine if I boot into existing domains, skipping PXE rom. This occurs on domains created with 2.6.1 or with 2.7 Reverting to qemu 2.6.1 package corrects the issue. When I choose PXE boot, the machine immediately moves to a paused state (crashed). I only see this: Booting from ROM... iPXE (PCI 00:03.0) starting execution Followed by an immediate crash of qemu. The log simply states emulation error with some other information I don't understand memory contents perhaps. I can use qemu virtual networking and boot via local files served over tfp: eg: qemu-system-x86_64 -boot n -net nic,model=virtio,vlan=0 -net user,vlan=0,tftp=/tmp/tftp,bootfile=/pxelinux.0 I have also tried reverting to the 2.6.1 pxe-virtio.rom file while using qemu 2.7. Still I get the crash. So this appears to be some issue with how either libvirt/qemu is interacting with my network? I'm not sure what to look at next? Anyone else have similar issues? Thanks, Greg

1 0

[libvirt-users] New error: Failed to create chardev
by Iain Hallam 15 Sep '16

15 Sep '16

Hi. I'm running libvirt across a fleet of CentOS 7 desktops to provide VMs for other operating systems, and they've been running fine for the last year, through rebuilds, etc. In the last week, PCs that have been rebuilt no longer start our VMs, failing with the error: error: internal error: process exited while connecting to monitor: 2016-09-15T10:15:12.839724Z qemu-kvm: -chardev pty,id=charserial0: Failed to create chardev Various sites list remounting /dev/pts to solve this, with the command: mount -n -t devpts -o remount,mode=0620,gid=5 devpts /dev/pts After this command, the mount entry for devpts changed: devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) devpts on /dev/pts type devpts (rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000) However, the chardev error is still present. The VM log in /var/log/libvirt/qemu shows: 2016-09-15 10:15:59.422+0000: starting up libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) qemu version: 1.5.3 (qemu-kvm-1.5.3-105.el7_2.7) LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name centos6 -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 901c9deb-1935-4cfe-b9b4-ea2221d10487 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-centos6/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/vm/centos6-vda.qcow2,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -netdev tap,fd=23,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:02:59:93,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on 2016-09-15T10:15:59.508359Z qemu-kvm: -chardev pty,id=charserial0: Failed to create chardev 2016-09-15 10:15:59.682+0000: shutting down Anyone got any ideas? The only configuration change we have introduced in the last few weeks is creating local user accounts and turning off NIS on those boxes. SELinux is set to Permissive. Thanks, Iain Hallam. -- iain(a)nineworlds.net http://www.iainhallam.com/

1 0

[libvirt-users] Help With Nested Virtualization
by Brandon Golway 08 Sep '16

08 Sep '16

(Copied from my post on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?pid=1650650#p1650650) I have a FreeNAS 10 KVM setup via libvirt on my Arch server and I'd like to be able to test out the virtualization features in the nightly FreeNAS 10 builds but the problem is that I can't seem to get VT-x to correctly pass through to the guest. I have followed the [u][url= https://wiki.archlinux.org/index.php/KVM#Nested_virtualization]Nested Virtualization[/url][/u] section of the KVM wiki and I'm sure it's supported and enabled. Here's proof [code] [bran@nas ~]$ sudo systool -m kvm_intel -v | grep nested nested = "Y" [bran@nas ~]$ lscpu|grep Virtualization Virtualization: VT-x[/code] So the host/hardware isn't the problem, I believe the problem lies within libvirt. RedHat says to use [b]copy host CPU configuration[/b] or [b]host-passthrough[/b], with the latter being preferred. If I use the former I get the [b]CMT not supported[/b] error, but if I type in [b]host-passthrough[/b] which according to [u][url= https://bbs.archlinux.org/viewtopic.php?id=214539]this post[/url][/u] should work. When I set [b]host-passthrough[/b] it allows the system to boot up, but when I try to start a guest FreeNAS gives me the error that VT-x instructions aren't available, I have no idea how to check them either since the [b]proc[/b] pseudo-filesystem doesn't exist in BSD. I know for a fact that this isn't a problem with the FreeNAS builds because I've been testing them out for months on my Windows 10 desktop via VMware and nested virtualization works without issue, so it must be an issue with KVM/libvirt. Can someone clue me in on what the issue is? Here's the entire XML config for the FreeNAS VM [code] <domain type='kvm'> <name>FreeNAS_10</name> <uuid>ea816b85-7685-495a-bc97-28a882f190d7</uuid> <title>FreeNAS v10</title> <description>Nightly Alpha Test Releases</description> <memory unit='KiB'>6340608</memory> <currentMemory unit='KiB'>6340608</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.6'>hvm</type> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> <vmport state='off'/> </features> <cpu mode='host-passthrough'/> <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/sbin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk1.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk2.img'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/storage/vm-storage/FreeNAS_Disk3.img'/> <target dev='vdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='directsync' io='native'/> <source file='/var/lib/libvirt/images/FreeNAS_10.img'/> <target dev='vde' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x2'/> </controller> <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='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:24:5c:08'/> <source bridge='vmbridge'/> <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='vnc' port='-1' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <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> <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='0x0a' function='0x0'/> </memballoon> </devices> </domain>[/code] Thanks, Brandon Golway

4 6

[libvirt-users] Hiding hypervisor cpuid bit in Qemu
by Miller, Cody 08 Sep '16

08 Sep '16

Hello, I was hoping someone could help me with an issue I'm having with libvirt 1.3.3 and qemu 2.5.1. I'm trying to prevent qemu from exposing the 'hypervisor' cupid feature to my VMs. When running qemu directly I can use "-cpu ...,-hypervisor"; which works as expected. Using libvirt, I add "<feature policy='disable' name='hypervisor'/>" to the cpu section of the VMs xml. This however, does not prevent exposing the bit. Any help would be appreciated.

1 0

[libvirt-users] attaching storage pool error
by Johan Kragsterman 07 Sep '16

07 Sep '16

Hi! System centos7, system default libvirt version. I've succeeded to create an npiv storage pool, which I could start without problems. Though I couldn't attach it to the vm, it throwed errors when trying. I want to boot from it, so I need it working from start. I read one of Daniel Berrange's old(2010) blogs about attaching an iScsi pool, and draw my conclusions from that. Other documentation I haven't found. Someone can point me to a more recent documentation of this? Are there other mailing list in the libvirt/KVM communities that are more focused on storage? I'd like to know about these, if so, since I'm a storage guy, and fiddle around a lot with these things... There are quite a few things I'd like to know about, that I doubt this list cares about, or have knowledge about, like multipath devices/pools, virtio-scsi in combination with npiv-storagepool, etc. So anyone that can point me further....? Rgrds Johan

3 14

[libvirt-users] My Windows7 VM stopped at loading screen.
by Hyungwan Seo 06 Sep '16

06 Sep '16

Hello. I've been tesing VGA passthrough using libvirt. However, My *Windows7*(64bit) Virtual Machine stopped at loading screen as soon as I installed graphic driver(*AMD Radeon HD 7750*) and then restarted the VM. How Can I use VGA passthrough technology in my *Windows7* VM? I attached my testing information(HW, system environment and settings, qemu log and so on..) Best Regards. *------------------------------------- INFORMATION ------------------------------------------------------* *<1. HW specificatioin>* 1-(1). *Motherboard*: Gigabyte Z87X-OC-CF 1-(2). *CPU*: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz 1-(3). *Video*: AMD Radeon HD 7750 1-(4). *Audio*: AMD Radeon HD 7700/7800 Series *<2. System specification>* 2-(1). *OS*: Debian 8.5 (Jessie) 2-(2). *Kernel*: 3.16.0-4-amd64 2-(3). *qemu*: v2.1.2 2-(4). *libvirt*: v1.2.9 2-(5). *virt-manager*: v1.0.1 *<3. Testing process>* 3-(1). Execute a vfio.sh script. -> # ./vfio.sh 3-(2). Execute the following command -> # virsh create windows7_test999_Radeon.xml 3-(3). Connect to windows7 VM via vnc viewer. 3-(4). Install AMD Radeon HD 7750 graphic driver. 3-(5). Rebooting. 3-(6). Infinite windows7 loading screen. ---> PROBLEM!! *<4. Detailed system settings and script information>* *4-(1). vfio.sh script* # ./vfio.sh ========================= #!/bin/bash # vfio.sh configfile=/etc/vfio-pci1.cfg vfiobind() { dev="$1" vendor=$(cat /sys/bus/pci/devices/$dev/vendor) device=$(cat /sys/bus/pci/devices/$dev/device) if [ -e /sys/bus/pci/devices/$dev/driver ]; then echo $dev > /sys/bus/pci/devices/$dev/driver/unbind fi echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id } modprobe vfio-pci cat $configfile | while read line;do echo $line | grep ^# >/dev/null 2>&1 && continue vfiobind $line done exit 0 ======================== *4-(2). /etc/vfio-pci1.cfg* # cat /etc/vfio-pci1.cfg 0000:01:00.0 0000:01:00.1 # lspci -nn ---SNIP--- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E] [1002:683f] 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] [1002:aab0] ---SNIP--- *4-(3). /etc/initramfs-tools/modules* # cat /etc/initramfs-tools/modules pci_stub ids=1002:683f,1002:aab0 *4-(4). dmesg | grep pci-stub* # dmesg | grep pci-stub [ 2.863634] pci-stub: add 1002:683F sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000 [ 2.863642] pci-stub 0000:01:00.0: claimed by stub [ 2.863647] pci-stub 0000:02:00.0: claimed by stub [ 2.863662] pci-stub 0000:03:00.0: claimed by stub [ 2.863666] pci-stub 0000:04:00.0: claimed by stub [ 2.863669] pci-stub: add 1002:AAB0 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000 [ 2.863673] pci-stub 0000:01:00.1: claimed by stub [ 2.863678] pci-stub 0000:02:00.1: claimed by stub [ 2.863684] pci-stub 0000:03:00.1: claimed by stub [ 2.863690] pci-stub 0000:04:00.1: claimed by stub *4-(5). /etc/modules* # cat /etc/modules pci_stub vfio vfio_iommu_type1 vfio_pci kvm kvm_intel *4-(6). /etc/default/grub* # cat /etc/default/grub ======================== # cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" ======================== *4-(7). Kernel module check* # lsmod | grep pci_stub pci_stub 12429 0 # lsmod | grep vfio vfio_pci 31388 0 vfio_iommu_type1 17118 0 vfio 18402 2 vfio_iommu_type1,vfio_pci # lsmod | grep kvm kvm_intel 139116 0 kvm 388784 1 kvm_intel *4-(8). virsh create windows7_test999_Radeon.xml* # virsh create windows7_test999_Radeon.xml Domain windows7_test999 created from windows7_test999_Radeon.xml *4-(9). virsh list* Id Name State ---------------------------------------------------- 2 windows7_test999 running *4-(10). qemu process check* # ps aux | grep qemu root 1283 20.4 24.1 6788084 3965048 ? SLl 16:45 16:17 qemu-system-x86_64 -enable-kvm -name windows7_test999 -S -machine pc-i440fx-2.1,accel=kvm,usb=off -m 3815 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid a2366bca-b992-4b02-b6ab-c6b2e8198362 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/windows7_test999.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/data/iso/win7.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/data/iso/virtio-win-0.1.118.iso,if=none,id=drive-ide0-1-1,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -drive file=/root/virsh/win7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=24,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=94:de:80:a4:4b:39,bus=pci.0,addr=0x3 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on root 2228 0.0 0.0 16640 2312 pts/2 S+ 18:05 0:00 grep qemu *4-(11). windows7_test999_Radeon.xml* ======================== <domain type='kvm' id='2'> <name>windows7_test999</name> <uuid>a2366bca-b992-4b02-b6ab-c6b2e8198362</uuid> <memory unit='KiB'>3906560</memory> <currentMemory unit='KiB'>3906252</currentMemory> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/data/iso/win7.iso'/> <backingStore/> <target dev='vdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/data/iso/virtio-win-0.1.118.iso'/> <backingStore/> <target dev='hdd' bus='ide'/> <readonly/> <alias name='ide0-1-1'/> <address type='drive' controller='0' bus='1' target='0' unit='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/root/virsh/win7.qcow2'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='94:de:80:a4:4b:39'/> <source network='default'/> <target dev='vnet0'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='no' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> * <hostdev mode='subsystem' type='pci' managed='yes'>* * <driver name='vfio'/>* * <source>* * <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>* * </source>* * <alias name='hostdev0'/>* * <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>* * </hostdev>* <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> ======================== *4-(12). cat /var/log/libvirt/qemu/windows7_test999.log* # cat /var/log/libvirt/qemu/windows7_test999.log 2016-09-06 09:21:38.826+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name windows7_test999 -S -machine pc-i440fx-2.1,accel=kvm,usb=off -m 3815 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid a2366bca-b992-4b02-b6ab-c6b2e8198362 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/windows7_test999.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/data/iso/win7.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/data/iso/virtio-win-0.1.118.iso,if=none,id=drive-ide0-1-1,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -drive file=/root/virsh/win7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=24,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=94:de:80:a4:4b:39,bus=pci.0,addr=0x3 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=onDomain id=2 is tainted: high-privileges

1 0

[libvirt-users] installing and accessing a VM? - newbie question maybe
by vrms＠netcologne.de 06 Sep '16

06 Sep '16

3 9

[libvirt-users] internal snapshot question
by vrms＠netcologne.de 03 Sep '16

03 Sep '16

I take an internal snapshot (VM is 'shutdown' when taking it) of a qcow2 image like this: $ qemu-img snapshot -c sn1 [my_image].qcow2 I see that snapshot when asking for: $ qemu-img info [my_image].qcow but do NOT see it with: $ virsh domblklist [my_domain] is that how it is meant to be?

3 4

[libvirt-users] Monitor guest vm memory usage
by journey journey 02 Sep '16

02 Sep '16

Hi All Is there a tool to monitor qemu-kvm guest vm memory usage ( free in guest vm)?Nowadays, I have already researched some methods:1. qemu-kvm process memory usage. Since qemu-kvm process memory usage always increases as time goes on, it will not reflect the memory usage in vm.2. virsh dommemstat Just as method 1.3. virsh qemu-monitor-command --hmp [domain name] "info mem" (1) when guest vm memory size less than 4Gbytes, it will output something like this: 7f882000-7f883000 00001000 urw 7fbf8000-7fbf9000 00001000 urw 88000000-88001000 00001000 -rw 88002000-88003000 00001000 urw 88004000-88005000 00001000 urw c9000000-c9001000 00001000 urw e8bfe000-e8bff000 00001000 urw ea000000-ea001000 00001000 urw ffbfc000-ffbfd000 00001000 -rw ffbfe000-ffbff000 00001000 urw it shows pde info of PG_PRESENT_MASK, maybe has some relation with guest vm memory usage. (2) when guest vm memory size larger than 4Gbytes, it will output noting. Please help!!

2 2