----- Original Message -----
> From: "Gal Hammer" <ghammer(a)redhat.com>
> To: "Igor Lvovsky" <ilvovsky(a)redhat.com>
> Cc: apuimedo(a)redhat.com, users(a)ovirt.org
> Sent: Thursday, August 16, 2012 11:02:27 AM
> Subject: Re: [Users] Nested kvms
> On 16/08/2012 10:12, Igor Lvovsky wrote:
> > ----- Original Message -----
> >> From: "Antoni Segura Puimedon" <asegurap(a)redhat.com>
> >> To: users(a)ovirt.org
> >> Sent: Thursday, August 16, 2012 10:04:40 AM
> >> Subject: [Users] Nested kvms
> >> Hi list!
> >> I've been playing lately with nested VMs in a configuration where
> >> I
> >> have
> >> a VM for the ovirt-engine and another to be used as a host (both
> >> created
> >> with virt-manager).
> >> After adding the virtualized host to the engine, I could start VMs
> >> but
> >> their boot process was always hanging/kernel panicking. The cpu
> >> type
> >> I
> >> had set for the virtualized host was Sandy bridge.
> >> After some trial and error, I changed the cpu type of the
> >> virtualized
> >> host to Conroe (as well as the cluster cpu type) and suddenly I
> >> can
> >> run
> >> VMs well through installation and usage without any kind of
> >> trouble.
> >> My question is... Any similar experiences? Or is it possible that
> >> in
> >> the
> >> meantime some yum update to qemu-kvm fooled me?
> > Gal,
> > Is it an bug that you already solved (vendor parsing issue) ?
> > I just can't find it in gerrit.
> Do you mean this one? http://gerrit.ovirt.org/5035
(can't verify it
> the moment as gerrit.ovirt is not responsive at the moment).
Yes, I think it is.
Toni, did you had this patch on you vdsm when you tried nested hosts?
I was using the vdsm from the rpms in build SI13.2.
> >> Best,
> >> Toni
> >> _______________________________________________
> >> Users mailing list
> >> Users(a)ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users