- Original Message -
> From: "Dead Horse"
> To: "Ayal Baron"
> Cc: users@ovirt.org
> Sent: Sunday, April 22, 2012 6:28:48 PM
> Subject: Re: [Users] fedora qemu modern CPU recognition issues cause ovirt
> manged host to go non-operational
>
Built and verified that both the latest fedora rawhide qemu and the latest
QEMU from git do not resolve this.
Here: fedora/development/rawhide/source/SRPMS/q/qemu-1.0-15.fc18.src.rpm)
and
Here: http://git.qemu.org/qemu.git
I suspect that unless the patches made to RHEL qemu, mentioned by the qemu
Sounds like vdsm should just require a newer version of qemu-kvm as well?
Have you tested with a newer qemu-kvm?
- Original Message -
>
> Seeing an issue wherein ovirt moves a managed host to non-operational
> state.
> This occurs with the currently released version of ovirt and the
> lat
Seeing an issue wherein ovirt moves a managed host to non-operational state.
This occurs with the currently released version of ovirt and the latest
development builds.
The ovirt host is loaded with Fedora core 16 and equipped with most current
development version of the vdsm.
*Editorial node*
The
4 matches
Mail list logo
