[Users] 3.2 beta and f18 host on dell R815 problem
during install of server I get this Host installation failed. Fix installation issues and try to Re-Install In deploy log 2013-01-31 12:17:30 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.hardware hardware._isVirtualizationEnabled:144 virtualization support GenuineIntel (cpu: False, bios: True) 2013-01-31 12:17:30 DEBUG otopi.context context._executeMethod:127 method exception Traceback (most recent call last): File "/tmp/ovirt-SfEARpd3h4/pythonlib/otopi/context.py", line 117, in _executeMethod method['method']() File "/tmp/ovirt-SfEARpd3h4/otopi-plugins/ovirt-host-deploy/vdsm/hardware.py", line 170, in _validate_virtualization _('Hardware does not support virtualization') RuntimeError: Hardware does not support virtualization 2013-01-31 12:17:30 ERROR otopi.context context._executeMethod:136 Failed to execute stage 'Setup validation': Hardware does not support virtualization note the GenuineIntel above... ?? But actually it is AMD [root@f18ovn03 ~]# lsmod|grep kvm kvm_amd 59623 0 kvm 431794 1 kvm_amd cat /proc/cpuinfo ... processor : 47 vendor_id : AuthenticAMD cpu family : 16 model : 9 model name : AMD Opteron(tm) Processor 6174 stepping : 1 microcode : 0x10000d9 cpu MHz : 800.000 cache size : 512 KB physical id : 3 siblings : 12 core id : 5 cpu cores : 12 apicid : 59 initial apicid : 59 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips : 4400.44 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate Any hint? Gianluca
On Thu, Jan 31, 2013 at 12:24 PM, Gianluca Cecchi wrote:
during install of server I get this Host installation failed. Fix installation issues and try to Re-Install
In deploy log
2013-01-31 12:17:30 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.hardware hardware._isVirtualizationEnabled:144 virtualization support GenuineIntel (cpu: False, bios: True) 2013-01-31 12:17:30 DEBUG otopi.context context._executeMethod:127 method exception Traceback (most recent call last): File "/tmp/ovirt-SfEARpd3h4/pythonlib/otopi/context.py", line 117, in _executeMethod method['method']() File "/tmp/ovirt-SfEARpd3h4/otopi-plugins/ovirt-host-deploy/vdsm/hardware.py", line 170, in _validate_virtualization _('Hardware does not support virtualization') RuntimeError: Hardware does not support virtualization 2013-01-31 12:17:30 ERROR otopi.context context._executeMethod:136 Failed to execute stage 'Setup validation': Hardware does not support virtualization
full log here: https://docs.google.com/file/d/0BwoPbcrMv8mvdURXWFF6X0NMRzg/edit BTW: I did use this same host in this hw configuration from a bios point of view as a host for a RHEV 3.0 beta about one year ago...
On Thu, Jan 31, 2013 at 12:30 PM, Gianluca Cecchi wrote:
BTW: I did use this same host in this hw configuration from a bios point of view as a host for a RHEV 3.0 beta about one year ago...
screenshots of bios setting for this r815 server: https://docs.google.com/file/d/0BwoPbcrMv8mvbno5b2w3RmJNdTQ/edit https://docs.google.com/file/d/0BwoPbcrMv8mvdE5VUDZzNFIzUkU/edit https://docs.google.com/file/d/0BwoPbcrMv8mvOXJ6WWVPb0l3N2M/edit Gianluca
Output of command # virsh capabilities on this host https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit
On Thu, Jan 31, 2013 at 12:57:38PM +0100, Gianluca Cecchi wrote:
Output of command # virsh capabilities on this host
https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit
I, and list archive viewers, prefer in-lining such output. It seems to be lacking "svm" - could it be that you need to enable it in BIOS? <host> <uuid>44454c4c-5600-1059-8047-cac04f4e344a</uuid> <cpu> <arch>x86_64</arch> <model>Opteron_G3</model> <vendor>AMD</vendor> <topology sockets='1' cores='6' threads='1'/> <feature name='nodeid_msr'/> <feature name='wdt'/> <feature name='skinit'/> <feature name='ibs'/> <feature name='osvw'/> <feature name='3dnowprefetch'/> <feature name='cr8legacy'/> <feature name='extapic'/> <feature name='cmp_legacy'/> <feature name='3dnow'/> <feature name='3dnowext'/> <feature name='pdpe1gb'/> <feature name='fxsr_opt'/> <feature name='mmxext'/> <feature name='ht'/> <feature name='vme'/> </cpu>
On Sun, Feb 3, 2013 at 11:54 AM, Dan Kenigsberg wrote:
On Thu, Jan 31, 2013 at 12:57:38PM +0100, Gianluca Cecchi wrote:
Output of command # virsh capabilities on this host
https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit
I, and list archive viewers, prefer in-lining such output. It seems to be lacking "svm" - could it be that you need to enable it in BIOS?
<host> <uuid>44454c4c-5600-1059-8047-cac04f4e344a</uuid> <cpu> <arch>x86_64</arch> <model>Opteron_G3</model> <vendor>AMD</vendor> <topology sockets='1' cores='6' threads='1'/> <feature name='nodeid_msr'/> <feature name='wdt'/> <feature name='skinit'/> <feature name='ibs'/> <feature name='osvw'/> <feature name='3dnowprefetch'/> <feature name='cr8legacy'/> <feature name='extapic'/> <feature name='cmp_legacy'/> <feature name='3dnow'/> <feature name='3dnowext'/> <feature name='pdpe1gb'/> <feature name='fxsr_opt'/> <feature name='mmxext'/> <feature name='ht'/> <feature name='vme'/> </cpu>
Hi Dan, keep in mind that my error was to point in webadmin gui to an ip that was not the one of the intended node... but this virsh capabilities command was indeed run on the Opteron node (that I was able to activate when using right ip in webadmin...) Indeed this thing that connecting to the node and running this command I didn't see the "svm" flag was one that contributed in my not being aware of my first time error.... But as you saw in another mail of this thread, the host has virtualization feature enabled in bios. Screenshots' links of bios settings posted here: http://lists.ovirt.org/pipermail/users/2013-January/011976.html As I wrote in another thread related to the same host, it is indeed not well identified: http://lists.ovirt.org/pipermail/users/2013-January/011997.html it appears as 8-sockets 6-cores while it actually has 4-sockets 12-core each screenshot of host in gui already posted is anyway here: https://docs.google.com/file/d/0BwoPbcrMv8mvdjdYNjVfT2NWY0U/edit I'm available to further debug if requested... Gianluca
On Sun, Feb 03, 2013 at 12:57:29PM +0100, Gianluca Cecchi wrote:
On Sun, Feb 3, 2013 at 11:54 AM, Dan Kenigsberg wrote:
On Thu, Jan 31, 2013 at 12:57:38PM +0100, Gianluca Cecchi wrote:
Output of command # virsh capabilities on this host
https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit
I, and list archive viewers, prefer in-lining such output. It seems to be lacking "svm" - could it be that you need to enable it in BIOS?
<host> <uuid>44454c4c-5600-1059-8047-cac04f4e344a</uuid> <cpu> <arch>x86_64</arch> <model>Opteron_G3</model> <vendor>AMD</vendor> <topology sockets='1' cores='6' threads='1'/> <feature name='nodeid_msr'/> <feature name='wdt'/> <feature name='skinit'/> <feature name='ibs'/> <feature name='osvw'/> <feature name='3dnowprefetch'/> <feature name='cr8legacy'/> <feature name='extapic'/> <feature name='cmp_legacy'/> <feature name='3dnow'/> <feature name='3dnowext'/> <feature name='pdpe1gb'/> <feature name='fxsr_opt'/> <feature name='mmxext'/> <feature name='ht'/> <feature name='vme'/> </cpu>
Hi Dan, keep in mind that my error was to point in webadmin gui to an ip that was not the one of the intended node...
but this virsh capabilities command was indeed run on the Opteron node (that I was able to activate when using right ip in webadmin...)
Indeed this thing that connecting to the node and running this command I didn't see the "svm" flag was one that contributed in my not being aware of my first time error.... But as you saw in another mail of this thread, the host has virtualization feature enabled in bios. Screenshots' links of bios settings posted here: http://lists.ovirt.org/pipermail/users/2013-January/011976.html
As I wrote in another thread related to the same host, it is indeed not well identified: http://lists.ovirt.org/pipermail/users/2013-January/011997.html
it appears as 8-sockets 6-cores while it actually has 4-sockets 12-core each screenshot of host in gui already posted is anyway here: https://docs.google.com/file/d/0BwoPbcrMv8mvdjdYNjVfT2NWY0U/edit
I'm available to further debug if requested...
I see that /proc/cpuinfo DOES have svm, but libvirt does not recognize it. Maybe our friendly libvirt developers (CCed) could help with the debugging. Which version of libvirt are you using? Could you dump your /proc/cpuinfo somewhere? Dan.
On Sun, Feb 3, 2013 at 2:40 PM, Dan Kenigsberg wrote:
I see that /proc/cpuinfo DOES have svm, but libvirt does not recognize it. Maybe our friendly libvirt developers (CCed) could help with the debugging. Which version of libvirt are you using? Could you dump your /proc/cpuinfo somewhere?
Dan.
libvirt-0.10.2.2-3.fc18.x86_64 full cpuinfo output here: https://docs.google.com/file/d/0BwoPbcrMv8mvMUVkNWp0SC11MTQ/edit?usp=sharing BTW: when I configure a server as an oVirt node its libvirtd.conf is modified by vdsm, so that I can't run anymore the command virsh capabilities My host, after successfully install now gives me: [root@f18ovn03 ~]# virsh capabilities Please enter your authentication name: do I have to pass any particular connection parameters for vdsm to get the output again? What to use as authentication name and password? Gianluca
Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
[root@f18ovn03 ~]# virsh capabilities Please enter your authentication name:
do I have to pass any particular connection parameters for vdsm to get the output again? What to use as authentication name and password?
If I'm right it is vdsm@ovirt and the passwd is in libvirt.conf, or try google. Can't remember at the moment. I have it somewhere written down but can access it tomorrow . Joop -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
On Sun, Feb 03, 2013 at 04:55:11PM +0100, Gianluca Cecchi wrote:
On Sun, Feb 3, 2013 at 2:40 PM, Dan Kenigsberg wrote:
I see that /proc/cpuinfo DOES have svm, but libvirt does not recognize it. Maybe our friendly libvirt developers (CCed) could help with the debugging. Which version of libvirt are you using? Could you dump your /proc/cpuinfo somewhere?
Dan.
libvirt-0.10.2.2-3.fc18.x86_64
full cpuinfo output here: https://docs.google.com/file/d/0BwoPbcrMv8mvMUVkNWp0SC11MTQ/edit?usp=sharing
I suppose that the problem you are seeing is indeed the libvirt issue pointed out by Kaul.
BTW: when I configure a server as an oVirt node its libvirtd.conf is modified by vdsm, so that I can't run anymore the command
virsh capabilities
My host, after successfully install now gives me:
[root@f18ovn03 ~]# virsh capabilities Please enter your authentication name:
do I have to pass any particular connection parameters for vdsm to get the output again? What to use as authentication name and password?
You can pass -r (read-only), or use `-c qemu+tcp://hostname/system`. Not that the latter option would allow you to change things under the feet of oVirt, which does not end well usually. Dan.
Hi Gianluca can you post/attach/provide the output of cpuid? # cpuid In case it's not installed it's provided by the rpm: cpuid-20120601-2.fc18.x86_64 Thanks, -- Federico ----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "users" <users@ovirt.org> Sent: Thursday, January 31, 2013 12:24:41 PM Subject: [Users] 3.2 beta and f18 host on dell R815 problem
during install of server I get this Host installation failed. Fix installation issues and try to Re-Install
In deploy log
2013-01-31 12:17:30 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.hardware hardware._isVirtualizationEnabled:144 virtualization support GenuineIntel (cpu: False, bios: True) 2013-01-31 12:17:30 DEBUG otopi.context context._executeMethod:127 method exception Traceback (most recent call last): File "/tmp/ovirt-SfEARpd3h4/pythonlib/otopi/context.py", line 117, in _executeMethod method['method']() File "/tmp/ovirt-SfEARpd3h4/otopi-plugins/ovirt-host-deploy/vdsm/hardware.py", line 170, in _validate_virtualization _('Hardware does not support virtualization') RuntimeError: Hardware does not support virtualization 2013-01-31 12:17:30 ERROR otopi.context context._executeMethod:136 Failed to execute stage 'Setup validation': Hardware does not support virtualization
note the GenuineIntel above... ?? But actually it is AMD
[root@f18ovn03 ~]# lsmod|grep kvm kvm_amd 59623 0 kvm 431794 1 kvm_amd
cat /proc/cpuinfo
participants (4)
-
Dan Kenigsberg -
Federico Simoncelli -
Gianluca Cecchi -
Joop