----- Original Message -----
From: "Greg Sheremeta" <gshereme@redhat.com> To: "Thomas Suckow" <thomas.suckow@pnnl.gov> Cc: users@ovirt.org Sent: Sunday, September 15, 2013 5:43:42 PM Subject: Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19
----- Original Message -----
From: "Thomas Suckow" <thomas.suckow@pnnl.gov> To: users@ovirt.org Sent: Friday, September 13, 2013 8:14:32 PM Subject: Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19
On 09/13/2013 09:28 AM, Suckow, Thomas J wrote:
On 09/13/2013 04:29 AM, Greg Sheremeta wrote:
Did this get resolved? Is there a BZ? (I can't find one.) I am also seeing "The Hosts emulated machines are <UNKNOWN>" on yesterday's nightly build. The host I'm trying to add is a VM.
[host2 $] vdsClient -s 0 getVdsCaps | grep emulatedMachines emulatedMachines = []
Greg
I am uncertain if it did, I took down our production system (Low availability requirements) yesterday so I could fiddle with an all-in-one install trial today on another hard disk. I wonder if it is a certain hardware configuration, ours is an old Dell Precision.
My previous attempt was "normal" install and then tried to add localhost. I wonder if the all in one would give different results.
- Thomas
I just finally got the All-In-One installed. It seems to be working. I noticed that the all-in-one set the CPU type in the cluster settings, you could try setting that...
Thanks -- it didn't work. I reported this as a bug. I suspect it's a vdsm bug related to the host being virtualized. But just guessing. https://bugzilla.redhat.com/show_bug.cgi?id=1008243
Greg
Following up. Thanks to Assaf Muller for the tip: running a yum update on a host works around the "The Hosts emulated machines are <UNKNOWN> and the cluster is [rhel6.4.0, pc-1.0]}". I guess it's just best to do that on all my new hosts from now on. Not sure if it's officially recommended or documented to do that. Follow BZ1008243 if you're interested in the root cause. Greg