- Users - libvirt List Archives

[libvirt-users] libvirt equivalent for VMWare for SCSI mode = independent-persistent?
by Juha Anttila 20 May '16

20 May '16

Hi, I'm attempting to add virtual SCSI disks to my KVM guests the same way as I did with VMWare, but I'm having issues. Without knowing any better, I'm assuming it has something to do with me attaching the disk incorrectly, and when I'm looking at the VMWare config one thing I noticed was the SCSI mode "independent-persistent" which I cannot find in libvirt documentation by quick look. Would anyone know how to achieve this? In the VMWare VMX file I have: scsi1:4.present = "TRUE" scsi1:4.fileName = "SCSI1.vmdk" scsi1:4.mode = "independent-persistent" scsi1:4.deviceType = "scsi-hardDisk" and I attempted the below configuration, but when I tried to use the disk as a IO Fencing disk for veritas cluster file system, it failed saying that the device is not SCSI-3 compliant. With VMWare same works fine. SCSI Controller: <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0e' function='0x0'/> </controller> Disk: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/home/VM/VMImages/IOFencing1.img'/> <target dev='sda' bus='scsi'/> <shareable/> <alias name='scsi0-0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk>

2 1

[libvirt-users] libvirt on Raspberry Pi, block by parameter "-S"
by Xu Ding 20 May '16

20 May '16

Hi I have used libvirt on Raspberry Pi Debian. I can start the vm, but it just starts and doesn't continue. I find the qemu-system-arm command generated by virsh has a parameter "-S", when I copy the command, remove the parameter, run it in the console, the vm can run normally. But I don't know how to remove the parameter in the xml file, or in virsh. Regards Thank you Xu Here's the qemu-system-arm command, generated by libvirt: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/local/bin/qemu-system-arm -name test -S -machine vexpress-a15,accel=kvm,usb=off -cpu host -m 500 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid cab134ea-eed8-42e7-88cb-403ee2801e22 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=off,strict=on -kernel /home/pi/src/vexpress-zImage -append "root=/dev/vda rw console=ttyAMA0" -dtb /home/pi/src/vexpress-v2p-ca15-tc1.dtb -usb -drive file=/home/pi/src/test.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-device,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/home/pi/src/opensuse.img,if=none,media=cdrom,id=drive-virtio-disk1,readonly=on,format=raw -device virtio-blk-device,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1 -net nic,macaddr=00:16:3e:5d:aa:a8,vlan=0,model=lan9118,name=net0 -net tap,fd=23,vlan=0,name=hostnet0 -serial file:/var/log/libvirt/qemu/console.log -serial pty -msg timestamp=on Here's my xml file: <domain type='kvm'> <name>test</name> <uuid>cab134ea-eed8-42e7-88cb-403ee2801e22</uuid> <memory unit='KiB'>512000</memory> <currentMemory unit='KiB'>512000</currentMemory> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> </cputune> <os> <type arch='armv7l' machine='vexpress-a15'>hvm</type> <kernel>/home/pi/src/vexpress-zImage</kernel> <cmdline>"root=/dev/vda rw console=ttyAMA0"</cmdline> <dtb>/home/pi/src/vexpress-v2p-ca15-tc1.dtb</dtb> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode='host-model'> <model fallback='allow'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/bin/qemu-system-arm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/home/pi/src/test.qcow2'/> <target dev='hda' bus='virtio'/> <address type='virtio-mmio'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/home/pi/src/opensuse.img'/> <target dev='hdb' bus='virtio'/> <readonly/> <address type='virtio-mmio'/> </disk> <interface type='bridge'> <mac address='00:16:3e:5d:aa:a8'/> <source bridge='br0'/> <model type='lan9118'/> </interface> <serial type='file'> <source path='/var/log/libvirt/qemu/console.log'/> <target port='0'/> </serial> <serial type='pty'> <target port='1'/> </serial> <console type='file'> <source path='/var/log/libvirt/qemu/console.log'/> <target type='serial' port='0'/> </console> </devices> </domain>

2 1

[libvirt-users] Cannot get Sound-Output via pulseaudio
by arne 18 May '16

18 May '16

Hi, i am currently trying to get my qemu-bashscripts to run via libvirt. It took some time but my first VM seems to work okay. My main problem is Sound. I run a pulse audio service and when starting the vm via Commandline it sends sound to the pulseaudioserver just fine However when i start the vm via libvirt i cannot get any sound output, pavucontrol shows no connected application. When looking at the /var/log/libvirt/<vmname>.log i can see that the vm is started with ‚QEMU_AUDIO_DRV=none‘ . How can i set this to QEMU_AUDIO_DRV=pa ? Hope someone might help me. Cheers

1 0

[libvirt-users] Cannot get Sound-Output via pulseaudio
by arne 18 May '16

18 May '16

Hi, i am currently trying to get my qemu-bashscripts to run via libvirt. It took some time but my first VM seems to work okay. My main problem is Sound. I run a pulse audio service and when starting the vm via Commandline it sends sound to the pulseaudioserver just fine However when i start the vm via libvirt i cannot get any sound output, pavucontrol shows no connected application. When looking at the /var/log/libvirt/<vmname>.log i can see that the vm is started with ‚QEMU_AUDIO_DRV=none‘ . How can i set this to QEMU_AUDIO_DRV=pa ? Hope someone might help me. Cheers

1 0

[libvirt-users] Disable certain VMs from being launched
by Sureshkumar Kaliannan 18 May '16

18 May '16

The VMs are launched using a pre-defined domain.xml + raw disk. All VMs (whitelisted + backlisted) ones are launched the same way (virsh define followed by virsh start) I want to be able to disable launching of certain VMs(blacklisted ones) unless explicitly allowed. What is the best way to accomplish this? I am exploring the selinux path for this requirement. The current implementation(understandably) isolates each guest into their own MCS categories but by default the resources are always relabeled. Unless, I change the libvirtd code, the auto relabelling can't be disabled(?) Still trying to understand the various virt selinux policies, and XML seclabel options to accomplish this. Are there better alternatives? thanks Suresh

1 0

[libvirt-users] How to set virtual pci slot address > 3 on creating VM?
by Eddie Yen 17 May '16

17 May '16

Hello everyone, this is my first time post this question at this mailing list. And I'm not so well in English, so apologize first if I got any sentence wrong or the question doesn't mean so well. OK, I'm now trying the KVMGT on QEMU and it works well even I didn't set any virtual display. For now KVMGT only can launch with QEMU command line, I know that libvirt didn't support it yet. So I have to set command line for KVMGT features in one of the shell script (i.e /usr/bin/kvm). The problem is, KVMGT set itself as VGA device, that means the default virtual PCI address gave from QEMU is 0000:00:02.0. If I set KVMGT feature command on shell script file (i.e -vga vgt), I will get this error while creating the VM from virt-manager. qemu-system-x86_64: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2: PCI: slot 2 function 0 not available for virtio-balloon-pci, in use by vgt-vga qemu-system-x86_64: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x2: Device 'virtio-balloon-pci' could not be initialized So I have to create the VM without KVMGT first, then manually edit virtual PCI address to avoid 0000:00:02.0 But I want to make it automatically for each creation in some reasons. How can I do? And appreciate first for every reply. Many thanks, Eddie.

1 0

[libvirt-users] Nested Virtualization not working
by Daniel Sanabria 16 May '16

16 May '16

Hi, I wonder if someone can provide pointers on what might be wrong with my setup. I'm running a kvm host Fedora23 with rawhide kernel on top of a skylake cpu - Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (family: 0x6, model: 0x4e, stepping: 0x3) As part of an experiment, I have enabled Nested virt support on the host and created a fedora23 guest with virt-manager using host-passthrough as the cpu model. The guest comes up fine and was updated without issues. Now if I install VirtualBox 5.0 and try to start a vm (fedora 23 again) I end up with a protection fault in the console (below) and the vm does not boot. A similar fault appeared when trying with a centos7.2 guest and a ubuntu vm but in that case just after the fault the guest reboots itself. What could be the problem here? Any help is very appreciated. Thanks, Daniel [ 77.538312] general protection fault: 0000 [#1] SMP [ 77.539235] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) ebtable_broute bridge stp llc ebtable_filter ebtable_nat ebtables ip6table_mangle ip6table_security ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables iptable_mangle iptable_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack snd_hda_codec_generic vboxdrv(OE) iosf_mbi kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device joydev snd_pcm ppdev irqbypass crct10dif_pclmul crc32_pclmul snd_timer snd acpi_cpufreq virtio_balloon parport_pc tpm_tis soundcore tpm i2c_piix4 parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c virtio_console virtio_net virtio_blk qxl drm_kms_helper ttm drm crc32c_intel serio_raw virtio_pci virtio_ring virtio ata_generic pata_acpi [ 77.548011] CPU: 0 PID: 1991 Comm: EMT Tainted: G OE 4.4.9-300.fc23.x86_64 #1 [ 77.548719] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.2-20150714_191134- 04/01/2014 [ 77.549715] task: ffff8800b4e8dd00 ti: ffff8800b4fdc000 task.ti: ffff8800b4fdc000 [ 77.550320] RIP: 0010:[<ffffffffa05ee506>] [<ffffffffa05ee506>] 0xffffffffa05ee506 [ 77.551053] RSP: 0018:ffff8800b4fdfd70 EFLAGS: 00050206 [ 77.551548] RAX: 00000000003406f0 RBX: 00000000ffffffdb RCX: 000000000000009b [ 77.552193] RDX: 0000000000000000 RSI: ffff8800b4fdfd00 RDI: ffff8800b4fdfcc8 [ 77.552952] RBP: ffff8800b4fdfd90 R08: 0000000000000004 R09: 00000000003406f0 [ 77.553498] R10: 0000000049656e69 R11: 000000000f8bfbff R12: 0000000000000020 [ 77.554042] R13: 0000000000000000 R14: ffffc90001c0207c R15: ffffffffa04c5220 [ 77.554594] FS: 00007fc70f128700(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 [ 77.555208] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 77.555650] CR2: 00007fc70eecb000 CR3: 00000000ba695000 CR4: 00000000003406f0 [ 77.556195] Stack: [ 77.556360] 0000000000000000 ffffffff00000000 0000000000000000 0000000000000002 [ 77.556985] ffff8800b4fdfdb0 ffffffffa0603db1 ffffc90001c02010 ffff88013822f6d0 [ 77.557597] ffff8800b4fdfe30 ffffffffa048b2f6 ffff8800b4ebc5c0 ffff8800b4fdc000 [ 77.558210] Call Trace: [ 77.558421] [<ffffffffa048b2f6>] ? supdrvIOCtl+0x2d36/0x3250 [vboxdrv] [ 77.558964] [<ffffffff813c2e45>] ? copy_user_enhanced_fast_string+0x5/0x10 [ 77.559526] [<ffffffffa04845b0>] ? VBoxDrvLinuxIOCtl_5_0_20+0x150/0x250 [vboxdrv] [ 77.560133] [<ffffffff81241648>] ? do_vfs_ioctl+0x298/0x480 [ 77.560593] [<ffffffff81338393>] ? security_file_ioctl+0x43/0x60 [ 77.561081] [<ffffffff812418a9>] ? SyS_ioctl+0x79/0x90 [ 77.561503] [<ffffffff817a0f2e>] ? entry_SYSCALL_64_fastpath+0x12/0x71 [ 77.562033] Code: 88 e4 fc ff ff b9 3a 00 00 00 0f 32 48 c1 e2 20 89 c0 48 09 d0 48 89 05 f9 db 0e 00 0f 20 e0 b9 9b 00 00 00 48 89 05 d2 db 0e 00 <0f> 32 48 c1 e2 20 89 c0 b9 80 00 00 c0 48 09 d0 48 89 05 cb db [ 77.564260] RIP [<ffffffffa05ee506>] 0xffffffffa05ee506 [ 77.564701] RSP <ffff8800b4fdfd70> [ 77.565103] ---[ end trace 9cf480524482767b ]---

1 1

[libvirt-users] Guest still receive packet with vlan tag (SR-IOV transparent VLAN)
by Long Hoang 16 May '16

16 May '16

Hello everyone, I'm having problem with SR-IOV transparent VLAN. My host is Fedora 22 and my guest is: pfSense 2.3. The NIC is Intel 82576. I'm using pfSense Packet Capture to check the packet and find that inbound packet still have the vlan tag. The outbound packet seem fine because the router can receive DHCP discover packet from the guest and then send DHCP offer and ARP request packet to the guest (which still have the vlan tag so the guest does not response). Loading Ubuntu LiveCD in the same VM does not have this issue so I do not know what is the cause? Any idea to diagnose? Another problem I have is libvirt does not correctly restore the vf mac address to all zero and then some occasion, there will be duplicate mac address in different vfs which will trigger spoof checking. I found the related mail here https://www.redhat.com/archives/libvir-list/2015-December/msg00478.html which point to this bug https://bugzilla.redhat.com/show_bug.cgi?id=1302166 . The bug only mention to mellanox cards. Do anyone have the same problem (with igb/igbvf driver) ? Or is it fixed in upstream?

2 2

[libvirt-users] More recent libvirt builds for CentOS 7
by Le Nucksi 16 May '16

16 May '16

Hello list, is there a way to get more recent libvirt builds for CentOS 7 that include support for the xl (modern Xen) toolstack? I tried to build libvirt from the SRPM, which succeeded, however, without the mentioned Xen parts. I have also found two repos from people who provide upstream libvirt builds for CentOS 7, again, without the Xen parts. - https://copr.fedorainfracloud.org/coprs/jmliger/virt7-upstream/ and - https://build.opensuse.org/package/show/home:aevseev/libvirt Within the CentOS virtualization SIG builds for Xen there is a 1.3.x build of libvirt that includes support for the modern Xen toolstack. Would it be possible to inline this into the upstream to enable building it with Xen features on CentOS 7 such that the aforementioned people's RPMs would contain it? I appreciate any enlightment on the topic. Cheers, Le

2 2

[libvirt-users] More recent libvirt builds for CentOS 7
by Le Nucksi 15 May '16

15 May '16

Hello list, is there a way to get more recent libvirt builds for CentOS 7 that include support for the xl (modern Xen) toolstack? I tried to build libvirt from the SRPM, which succeeded, however, without the mentioned Xen parts. I have also found two repos from people who provide upstream libvirt builds for CentOS 7, again, without the Xen parts. - https://copr.fedorainfracloud.org/coprs/jmliger/virt7-upstream/ and - https://build.opensuse.org/package/show/home:aevseev/libvirt Within the CentOS virtualization SIG builds for Xen there is a 1.3.x build of libvirt that includes support for the modern Xen toolstack. Would it be possible to inline this into the upstream to enable building it with Xen features on CentOS 7 such that the aforementioned people's RPMs would contain it? I appreciate any enlightment on the topic. Cheers, Le

1 0