- Users - libvirt List Archives

[libvirt-users] Broken OS when booting rootfs from 9p share
by Olivier Mauras 23 Feb '15

23 Feb '15

Hello, I've been trying to boot a VM with the rootfs being a 9P share from the host. The VM OS is centos 7. The OS boots but no services can work and it appears that the authentication system is broken. Now the funny thing is that booting the same OS on the same 9P share manually with Qemu works as expected with a fully functionnal OS... So I'm wondering what could libvirt do that render the OS on the share broken - Something with rights ? Selinux is disabled on the host, and accessmode to the share is set to passthrough in both cases. Here's my working Qemu line: qemu -kernel /srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64 -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img -fsdev local,id=r,path=/srv/overlay/run/irc,security_model=passthrough -device virtio-9p-pci,fsdev=r,mount_tag=root -nographic -m 256M -machine pc-i440fx-2.1,accel=kvm -netdev tap,id=net0 -device virtio-net,netdev=net0,mac=52:54:00:12:36:34 -smp 1,sockets=1,cores=1 -append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro rootfstype=9p console=ttyS0' And here my libvirt VM config: <domain type='kvm'> <name>irc</name> <uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type> <kernel>/srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64</kernel> <initrd>/srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img</initrd> <cmdline>root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro rootfstype=9p</cmdline> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <filesystem type='mount' accessmode='passthrough'> <source dir='/srv/overlay/run/irc'/> <target dir='root'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:00:36:34'/> <source bridge='br0'/> <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> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> My libvirt version is 1.2.9, and qemu is 2.1.2. Thanks for your help, Olivier

1 0

[libvirt-users] virtio nic dosent use 10gbe speed.
by Kalil de A. Carvalho 20 Feb '15

20 Feb '15

Hello all. We are moving from Xenserver 6.5 environment to KVM because we can't use 10gbe speed in our VM's so we decided to test KVM. To inicial test I've create script, using qemu commands, to build two VM's and test the nic speed. Each VM has one nic, using virtio, into it own bridge. In this bridge we associate one 10gbe physical nic. They can communicate each other. When we try do a copy, through SCP, the speed is 300mbps. And if we open another copy this speed been the half. What we are using: S.O: CentOS 7 Kernel 3.10.0-123.el7.x86_64 qemu-kvm.x86_64 10:1.5.3-60.el7 libvirt-daemon.x86_64 1.1.1-29.el7 Hardware: Dell PowerEdge R720 16GB RAM 2TB SAS Two Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Command to start VM's: /usr/libexec/qemu-kvm -m 1024 -enable-kvm -k en-us -hda teste1.img -net nic,model=virtio,macaddr=00:01:02:aa:bb:cc -net tap,ifname=tap1,script=no,downscript=no -vnc :0 What Do I doing wrong? Is my test right? Is my interpretation right? Is my enviroment correct? Can I improve or fix any think with my libvirt or command arguments? Best regards -- Atenciosamente, Kalil de A. Carvalho

3 2

[libvirt-users] encryption
by Henry Noack 16 Feb '15

16 Feb '15

Hello you guys, it is possible to decrypt a kvm volume only by using the command line after starting it? Best regards Henry

1 0

[libvirt-users] spice session locking
by Jon Doe 16 Feb '15

16 Feb '15

Hi List, Is it possible to prevent other clients from stealing my libvirtd hosted spice session? This is a problem for me where multiple co-workers access the same guest over a qemu+ssh:// connection. Instead of simply disconnecting clients, I'd like libvirtd to deny the new client. I've been looking at polkit acl rules and the vnc sharePolicy attribute but so far no luck.

2 3

[libvirt-users] libvirt live migration, qcow2 image, nbd server
by Edward Young 15 Feb '15

15 Feb '15

Hi all, When I live migrate a vm using "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system tcp://192.168.1.3" I got the following error WARNING: Image format was not specified for 'nbd://node2:49155/drive-virtio-disk0' and probing guessed raw. 258 Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. 259 Specify the 'raw' format explicitly to remove the restrictions. >From the error itself, I can tell that nbd server treat this image as raw, rather than qcow2. My platform is libvirt+qemu. the image type of this vm is indeed qcow2. I do not know how to let nbd know this image format. Thanks! Ed

3 5

[libvirt-users] way to see the bootmenu via serial?
by mail list 13 Feb '15

13 Feb '15

Maybe this should go to the qemu mail list, but I have domains configured to dump to serial. Works fine I see Grub menu/kernel messages and the like, but the "bootmenu" listing only shows up over vnc. Is there a way to have that show up over serial? I definitely can hit up the qemu mail list as well if inappropriate for here

3 4

[libvirt-users] spice session locking
by Jon Doe 13 Feb '15

13 Feb '15

Hi List, Is it possible to prevent other clients from stealing my libvirtd hosted spice session? This is a problem for me where multiple co-workers access the same guest over a qemu+ssh:// connection. Instead of simply disconnecting clients, I'd like libvirtd to deny the new client. I've been looking at polkit acl rules and the vnc sharePolicy attribute but so far no luck.

1 0

[libvirt-users] QEMU 2.2.0 managedsave: Unknown savevm section type 5
by Paul Apostolescu 13 Feb '15

13 Feb '15

Hello, I am running into issues restoring VMs during reboot for some of my XP VMs - the environment is QEMU 2.2.0, libvirt 1.2.12 on CentOS 6.5 with KVM and libvirt-guests is set to suspend at shutdown. The weird part is Windows 7 is restored properly from the managedsave however XP does not, doing a start from virsh shows this: virsh # start xp-check error: Failed to start domain xp-check error: internal error: early end of file from monitor: possible problem: Unknown savevm section type 5 2015-02-04T23:55:37.117515Z qemu-kvm: load of migration failed: Invalid argument (qemu-kvm is a link to qemu-system-x86_64). Any ideas how to fix this ? Thanks

4 4

[libvirt-users] vm live storage migration with snapshots
by Edward Young 13 Feb '15

13 Feb '15

Hi all, I'm investigating the ways to improve the live migration performance in libvirt. I have a question about the vm live storage migration. the platform is libvirt + qemu + kvm If we want to migrate a running vm with its virtual disk images to another node. we can use 'virsh migrate ....' commands. What if this vm has a number of disk-only external snapshots? In the current version, how can live migrate this vm? Is it possible to blockcommit the snapshots to the base image and later perform the migration, without shutting down the running vm? Or is it possible to iteratively transfer all the snapshots to the destination and later live migrate only the latest new data? Thanks in advance. Best, Ed

2 6

[libvirt-users] libvirt/virsh change boot order
by Robb Walker 11 Feb '15

11 Feb '15

Hello, hope all are well. Am I missing something? If I add a cdrom and change boot order in a running vm with virsh edit, I have to shutdown the vm and restart to see the change in boot order. I can not just restart the vm via reboot inside the vm or virsh reboot vm. I don't see anything under /var/lib/libvirt/qemu/saved where I might expect conflict if I was battling against a saved configuration. If obvious, DUH, apologies and virtually bonk me on the head. Note: This is actually okay. Just don't want to miss on something that would allow me to just cycle the vm after make changes. on ubu -- 14.04 ii libvirt-bin 1.2.2-0ubuntu13.1.9 amd64 programs for the libvirt library ii libvirt-dev 1.2.2-0ubuntu13.1.9 amd64 development files for the libvirt library ii libvirt-doc 1.2.2-0ubuntu13.1.9 all documentation for the libvirt library ii libvirt0 1.2.2-0ubuntu13.1.9 amd64 library for interfacing with different virtualization systems <os> <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/home/foo/Downloads/archlinux-2015.02.01-dual.iso'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> Thanks and Kind Regards all This e-mail and any attachments may contain information that is confidential and proprietary and otherwise protected from disclosure. If you are not the intended recipient of this e-mail, do not read, duplicate or redistribute it by any means. Please immediately delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail or any attachments. The DRW Companies make no representations that this e-mail or any attachments are free of computer viruses or other defects.

2 2