Re: [virt-tools-list] Nested VM images fail/freeze during booting
Hi Cole, Both the physical host, L1 VM, and L2 VM are CentOS 7.0 (3.10.0-123.20.1.el7.x86_64). Thanks, Steve Amerige Principal Software Developer, Fraud and Compliance Solutions Development SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 On 4/2/2015 12:00 PM, Cole Robinson wrote: What distro is your physical host, L1 VM, and L2 VM running? - Cole On 04/02/2015 10:33 AM, Steve Amerige wrote: Hi all, *Problem:* Nested VM images fail/freeze during booting. *Details:* *Hardware:* * Model: Dell R620 * CPU: 2 x 6 x 2 (ht) Intel E5-2667 o flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl *vmx *smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid * Memory: 192GB * Disk: 7.0T local filesystem *Physical Hypervisor Configuration:* * /etc/modprobe.d/kvm-nested.conf (see below) * /etc/libvirt/qemu/virtual-hypervisor.xml (see below) o Runs without any problems o Includes: *Virtual Hypervisor Configuration:* * virt-manager opens without any problems * The virtual guest within the virtual hypervisor VM fails to boot o I see the screen in which the boot choices are shown. After the selection is made (either by waiting for the selection timeout, or by explicit selection), the next screen shows a screen dump (see below) * /etc/libvirt/qemu/virtual-guest.xml (see below) o Uses virbr0 o There is no /var/log/libvirt/qemu logfile as the boot up doesn't get far enough. I tried placing the virtual-guest.xml and image on the physical hypervisor and it does boot up without any problems. I've scoured the web and can't figure out why boot up is failing for the nested VM. Can anyone think of a solution or help out in any way? Thanks, Steve Amerige Principal Software Developer, Fraud and Compliance Solutions Development SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 *Physical Hypervisor Configuration:* */etc/modprobe.d/kvm-nested.conf:* options kvm_intel nested=1 */etc/libvirt/qemu/virtual-hypervisor.xml:* virtual-hypervisor 5bded4c9-e00a-4c33-8d68-f79ef9bf6daa 16777216 33554432 4 hvm SandyBridge Intel destroy restart restart /usr/libexec/qemu-kvm *Virtual Guest Configuration:* virtual-guest.xml 863ffbe3-1d4e-4ca6-b86f-bb13e32fed6b 2097152 2097152 1 hvm destroy restart restart /usr/libexec/qemu-kvm *virt-manager display of Virtual Machine showing failure: * ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] Nested VM images fail/freeze during booting
Hi all, *Problem:* Nested VM images fail/freeze during booting. *Details:* *Hardware:* * Model: Dell R620 * CPU: 2 x 6 x 2 (ht) Intel E5-2667 o flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl *vmx *smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid * Memory: 192GB * Disk: 7.0T local filesystem *Physical Hypervisor Configuration:* * /etc/modprobe.d/kvm-nested.conf (see below) * /etc/libvirt/qemu/virtual-hypervisor.xml (see below) o Runs without any problems o Includes: *Virtual Hypervisor Configuration:* * virt-manager opens without any problems * The virtual guest within the virtual hypervisor VM fails to boot o I see the screen in which the boot choices are shown. After the selection is made (either by waiting for the selection timeout, or by explicit selection), the next screen shows a screen dump (see below) * /etc/libvirt/qemu/virtual-guest.xml (see below) o Uses virbr0 o There is no /var/log/libvirt/qemu logfile as the boot up doesn't get far enough. I tried placing the virtual-guest.xml and image on the physical hypervisor and it does boot up without any problems. I've scoured the web and can't figure out why boot up is failing for the nested VM. Can anyone think of a solution or help out in any way? Thanks, Steve Amerige Principal Software Developer, Fraud and Compliance Solutions Development SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 *Physical Hypervisor Configuration:* */etc/modprobe.d/kvm-nested.conf:* options kvm_intel nested=1 */etc/libvirt/qemu/virtual-hypervisor.xml:* virtual-hypervisor 5bded4c9-e00a-4c33-8d68-f79ef9bf6daa 16777216 33554432 4 hvm SandyBridge Intel destroy restart restart /usr/libexec/qemu-kvm function='0x0'/> function='0x2'/> function='0x1'/> function='0x0'/> function='0x0'/> function='0x0'/> function='0x0'/> *Virtual Guest Configuration:* virtual-guest.xml 863ffbe3-1d4e-4ca6-b86f-bb13e32fed6b 2097152 2097152 1 hvm destroy restart restart /usr/libexec/qemu-kvm function='0x0'/> function='0x2'/> function='0x1'/> function='0x0'/> function='0x0'/> function='0x0'/> function='0x0'/> *virt-manager display of Virtual Machine showing failure: * ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] virt-manager: Warning on startup for CentOS 7
Hi all, On our CentOS 7 hypervisors (current 3.10.0-123.20.1.el7.x86_64 kernel), I note that we now always get the following warning message: ** (virt-manager:22899): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-9EjiOC2ERr: Connection refused when we start *virt-manager*. It doesn't seem to affect performance, but it is annoying and it causes users to submit support tickets that then take time to address. It also reduces confidence that everything is working the way it should. I have searched for a solution and haven't found one yet. Does anyone know (1) what is going on, and (2) how to remedy this problem so that the issue is addressed and the warning message is no longer emitted? Many thanks, Steve Amerige Principal Software Developer, Fraud and Compliance Solutions Development SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] Console for specific VMs only
Hi all, I've just joined this list. I've been using KVM for a couple of years now and have just joined the list. I use virt-manager as well as command line tools and custom software that we've written to manage a KVM server farm based on CentOS 6.6 and CentOS 7.0. My first question for the group is this: While I, as an administrator, use virt-manager and can open the console to a particular VM, I frequently have internal customers that I want to give access to a specific VM only so that they can have console access to their VM. If virt-manager had a way of being restricted to showing just one VM, then I could provide a secure script that calls virt-manager in this way. Is this possible? Is there any way today to open from the command line the console for a specific VM? Thanks, Steve Amerige Principal Software Developer, Fraud and Compliance Solutions Development SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
