Re: [Users] DL380 G5 - Fails to Activate

2013-01-25 Thread Tom Brown 

 I have a couple of old DL380 G5's and i am putting them into their own 
 cluster for testing various things out.
 The install of 3.1 from dreyou goes fine onto them but when they try to 
 activate i get the following
 
 Host xxx.xxx.net.uk moved to Non-Operational state as host does not meet the 
 cluster's minimum CPU level. Missing CPU features : model_Conroe, nx
 
 KVM appears to run just fine on these host and their cpu's are
 
 Intel(R) Xeon(R) CPU5140  @ 2.33GHz
 
 Is it possible to add these in to a 3.1 cluster ??
 
 and now i have managed to find a similar post
 
 # vdsClient -s 0 getVdsCaps | grep -i flags
   cpuFlags = 
 fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,dca,lahf_lm,dts,tpr_shadow
 
 # virsh -r capabilities
 capabilities
 
   host
 uuid134bd567-da9f-43f9-8a2b-c259ed34f938/uuid
 cpu
   archx86_64/arch
   modelkvm32/model
   vendorIntel/vendor
   topology sockets='1' cores='2' threads='1'/
   feature name='lahf_lm'/
   feature name='lm'/
   feature name='syscall'/
   feature name='dca'/
   feature name='pdcm'/
   feature name='xtpr'/
   feature name='cx16'/
   feature name='ssse3'/
   feature name='tm2'/
   feature name='est'/
   feature name='vmx'/
   feature name='ds_cpl'/
   feature name='monitor'/
   feature name='dtes64'/
   feature name='pbe'/
   feature name='tm'/
   feature name='ht'/
   feature name='ss'/
   feature name='acpi'/
   feature name='ds'/
   feature name='vme'/
 /cpu
 power_management
   suspend_disk/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transporttcp/uri_transport
   /uri_transports
 /migration_features
 topology
   cells num='1'
 cell id='0'
   cpus num='2'
 cpu id='0'/
 cpu id='1'/
   /cpus
 /cell
   /cells
 /topology
   /host
 
   guest
 os_typehvm/os_type
 arch name='i686'
   wordsize32/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.3.0/machine
   machine canonical='rhel6.3.0'pc/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
   domain type='kvm'
 emulator/usr/libexec/qemu-kvm/emulator
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   pae/
   nonpae/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest
 
   guest
 os_typehvm/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.3.0/machine
   machine canonical='rhel6.3.0'pc/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
   domain type='kvm'
 emulator/usr/libexec/qemu-kvm/emulator
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest
 
 /capabilities

Hi - any clues here or am i out of luck with these hosts?

thanks


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] DL380 G5 - Fails to Activate

2013-01-25 Thread Alexandre Santos 
2013/1/25 Tom Brown t...@ng23.net:

 I have a couple of old DL380 G5's and i am putting them into their own
 cluster for testing various things out.
 The install of 3.1 from dreyou goes fine onto them but when they try to
 activate i get the following

 Host xxx.xxx.net.uk moved to Non-Operational state as host does not meet the
 cluster's minimum CPU level. Missing CPU features : model_Conroe, nx

 KVM appears to run just fine on these host and their cpu's are

 Intel(R) Xeon(R) CPU5140  @ 2.33GHz

 Is it possible to add these in to a 3.1 cluster ??


 and now i have managed to find a similar post

 # vdsClient -s 0 getVdsCaps | grep -i flags
 cpuFlags =
 fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,dca,lahf_lm,dts,tpr_shadow

 # virsh -r capabilities
 capabilities

   host
 uuid134bd567-da9f-43f9-8a2b-c259ed34f938/uuid
 cpu
   archx86_64/arch
   modelkvm32/model
   vendorIntel/vendor
   topology sockets='1' cores='2' threads='1'/
   feature name='lahf_lm'/
   feature name='lm'/
   feature name='syscall'/
   feature name='dca'/
   feature name='pdcm'/
   feature name='xtpr'/
   feature name='cx16'/
   feature name='ssse3'/
   feature name='tm2'/
   feature name='est'/
   feature name='vmx'/
   feature name='ds_cpl'/
   feature name='monitor'/
   feature name='dtes64'/
   feature name='pbe'/
   feature name='tm'/
   feature name='ht'/
   feature name='ss'/
   feature name='acpi'/
   feature name='ds'/
   feature name='vme'/
 /cpu
 power_management
   suspend_disk/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transporttcp/uri_transport
   /uri_transports
 /migration_features
 topology
   cells num='1'
 cell id='0'
   cpus num='2'
 cpu id='0'/
 cpu id='1'/
   /cpus
 /cell
   /cells
 /topology
   /host

   guest
 os_typehvm/os_type
 arch name='i686'
   wordsize32/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.3.0/machine
   machine canonical='rhel6.3.0'pc/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
   domain type='kvm'
 emulator/usr/libexec/qemu-kvm/emulator
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   pae/
   nonpae/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest

   guest
 os_typehvm/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulator/usr/libexec/qemu-kvm/emulator
   machinerhel6.3.0/machine
   machine canonical='rhel6.3.0'pc/machine
   machinerhel6.2.0/machine
   machinerhel6.1.0/machine
   machinerhel6.0.0/machine
   machinerhel5.5.0/machine
   machinerhel5.4.4/machine
   machinerhel5.4.0/machine
   domain type='qemu'
   /domain
   domain type='kvm'
 emulator/usr/libexec/qemu-kvm/emulator
   /domain
 /arch
 features
   cpuselection/
   deviceboot/
   acpi default='on' toggle='yes'/
   apic default='on' toggle='no'/
 /features
   /guest

 /capabilities


 Hi - any clues here or am i out of luck with these hosts?

 thanks



 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


Hi,
how about the kvm-ok tool result? Is it responding:

INFO: /dev/kvm exists
KVM acceleration can be used

Alex
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] DL380 G5 - Fails to Activate

2013-01-25 Thread Tom Brown 
 
 
 I have a couple of old DL380 G5's and i am putting them into their own
 cluster for testing various things out.
 The install of 3.1 from dreyou goes fine onto them but when they try to
 activate i get the following
 
 Host xxx.xxx.net.uk moved to Non-Operational state as host does not meet the
 cluster's minimum CPU level. Missing CPU features : model_Conroe, nx
 
 KVM appears to run just fine on these host and their cpu's are
 
 Intel(R) Xeon(R) CPU5140  @ 2.33GHz
 
 Is it possible to add these in to a 3.1 cluster ??
 
 
 and now i have managed to find a similar post
 
 # vdsClient -s 0 getVdsCaps | grep -i flags
 cpuFlags =
 fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,dca,lahf_lm,dts,tpr_shadow
 
 # virsh -r capabilities
 capabilities
 
  host
uuid134bd567-da9f-43f9-8a2b-c259ed34f938/uuid
cpu
  archx86_64/arch
  modelkvm32/model
  vendorIntel/vendor
  topology sockets='1' cores='2' threads='1'/
  feature name='lahf_lm'/
  feature name='lm'/
  feature name='syscall'/
  feature name='dca'/
  feature name='pdcm'/
  feature name='xtpr'/
  feature name='cx16'/
  feature name='ssse3'/
  feature name='tm2'/
  feature name='est'/
  feature name='vmx'/
  feature name='ds_cpl'/
  feature name='monitor'/
  feature name='dtes64'/
  feature name='pbe'/
  feature name='tm'/
  feature name='ht'/
  feature name='ss'/
  feature name='acpi'/
  feature name='ds'/
  feature name='vme'/
/cpu
power_management
  suspend_disk/
/power_management
migration_features
  live/
  uri_transports
uri_transporttcp/uri_transport
  /uri_transports
/migration_features
topology
  cells num='1'
cell id='0'
  cpus num='2'
cpu id='0'/
cpu id='1'/
  /cpus
/cell
  /cells
/topology
  /host
 
  guest
os_typehvm/os_type
arch name='i686'
  wordsize32/wordsize
  emulator/usr/libexec/qemu-kvm/emulator
  machinerhel6.3.0/machine
  machine canonical='rhel6.3.0'pc/machine
  machinerhel6.2.0/machine
  machinerhel6.1.0/machine
  machinerhel6.0.0/machine
  machinerhel5.5.0/machine
  machinerhel5.4.4/machine
  machinerhel5.4.0/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
  /domain
/arch
features
  cpuselection/
  deviceboot/
  pae/
  nonpae/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest
 
  guest
os_typehvm/os_type
arch name='x86_64'
  wordsize64/wordsize
  emulator/usr/libexec/qemu-kvm/emulator
  machinerhel6.3.0/machine
  machine canonical='rhel6.3.0'pc/machine
  machinerhel6.2.0/machine
  machinerhel6.1.0/machine
  machinerhel6.0.0/machine
  machinerhel5.5.0/machine
  machinerhel5.4.4/machine
  machinerhel5.4.0/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
  /domain
/arch
features
  cpuselection/
  deviceboot/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest
 
 /capabilities
 
 
 Hi - any clues here or am i out of luck with these hosts?
 
 thanks
 
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
 
 Hi,
 how about the kvm-ok tool result? Is it responding:
 
 INFO: /dev/kvm exists
 KVM acceleration can be used

for posterity - 

http://www.linkedin.com/groups/Rhev-3-Beta-Proliant-DL380-2536011.S.93285316

This solved it for me - 

cheers

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] DL380 G5 - Fails to Activate

2013-01-24 Thread Tom Brown 

 
 
 
 I have a couple of old DL380 G5's and i am putting them into their own 
 cluster for testing various things out.
 The install of 3.1 from dreyou goes fine onto them but when they try to 
 activate i get the following
 
 Host xxx.xxx.net.uk moved to Non-Operational state as host does not meet the 
 cluster's minimum CPU level. Missing CPU features : model_Conroe, nx
 
 KVM appears to run just fine on these host and their cpu's are
 
 Intel(R) Xeon(R) CPU5140  @ 2.33GHz
 
 Is it possible to add these in to a 3.1 cluster ??

and now i have managed to find a similar post

# vdsClient -s 0 getVdsCaps | grep -i flags
cpuFlags = 
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,dca,lahf_lm,dts,tpr_shadow

# virsh -r capabilities
capabilities

  host
uuid134bd567-da9f-43f9-8a2b-c259ed34f938/uuid
cpu
  archx86_64/arch
  modelkvm32/model
  vendorIntel/vendor
  topology sockets='1' cores='2' threads='1'/
  feature name='lahf_lm'/
  feature name='lm'/
  feature name='syscall'/
  feature name='dca'/
  feature name='pdcm'/
  feature name='xtpr'/
  feature name='cx16'/
  feature name='ssse3'/
  feature name='tm2'/
  feature name='est'/
  feature name='vmx'/
  feature name='ds_cpl'/
  feature name='monitor'/
  feature name='dtes64'/
  feature name='pbe'/
  feature name='tm'/
  feature name='ht'/
  feature name='ss'/
  feature name='acpi'/
  feature name='ds'/
  feature name='vme'/
/cpu
power_management
  suspend_disk/
/power_management
migration_features
  live/
  uri_transports
uri_transporttcp/uri_transport
  /uri_transports
/migration_features
topology
  cells num='1'
cell id='0'
  cpus num='2'
cpu id='0'/
cpu id='1'/
  /cpus
/cell
  /cells
/topology
  /host

  guest
os_typehvm/os_type
arch name='i686'
  wordsize32/wordsize
  emulator/usr/libexec/qemu-kvm/emulator
  machinerhel6.3.0/machine
  machine canonical='rhel6.3.0'pc/machine
  machinerhel6.2.0/machine
  machinerhel6.1.0/machine
  machinerhel6.0.0/machine
  machinerhel5.5.0/machine
  machinerhel5.4.4/machine
  machinerhel5.4.0/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
  /domain
/arch
features
  cpuselection/
  deviceboot/
  pae/
  nonpae/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

  guest
os_typehvm/os_type
arch name='x86_64'
  wordsize64/wordsize
  emulator/usr/libexec/qemu-kvm/emulator
  machinerhel6.3.0/machine
  machine canonical='rhel6.3.0'pc/machine
  machinerhel6.2.0/machine
  machinerhel6.1.0/machine
  machinerhel6.0.0/machine
  machinerhel5.5.0/machine
  machinerhel5.4.4/machine
  machinerhel5.4.0/machine
  domain type='qemu'
  /domain
  domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
  /domain
/arch
features
  cpuselection/
  deviceboot/
  acpi default='on' toggle='yes'/
  apic default='on' toggle='no'/
/features
  /guest

/capabilities


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users