On Thu, Oct 15, 2009 at 08:47:51PM -0000, Dustin Kirkland wrote:
> Mathias hit this same problem last week.
Right. I ran into the same issue last week when I got some hardware
where the VT extensions were disabled. However the reported error from
the NC (hvm not supported) doesn't *always* mean that the BIOS has
disabled VT extensions.
I've run into this issue on some configuration that had already been
running a UEC infrastructure before. Upon reboot the NC would fail with
the same error message - this is the situation I described in my first
comment.
> I'm going to add a few more checks to /usr/bin/kvm-ok in the qemu-kvm package.
> 1) check that /dev/kvm exists
> 2) check the permissions on /dev/kvm
> 3) check dmesg for kvm disabled messages
>
> I see this sort of thing with KVM fairly frequently, and usually point
> people to run kvm-ok to get a hint. We should update these hints.
>
On Thu, Oct 15, 2009 at 08:47:51PM -0000, Dustin Kirkland wrote:
> Mathias hit this same problem last week.
Right. I ran into the same issue last week when I got some hardware
where the VT extensions were disabled. However the reported error from
the NC (hvm not supported) doesn't *always* mean that the BIOS has
disabled VT extensions.
I've run into this issue on some configuration that had already been
running a UEC infrastructure before. Upon reboot the NC would fail with
the same error message - this is the situation I described in my first
comment.
> I'm going to add a few more checks to /usr/bin/kvm-ok in the qemu-kvm package.
> 1) check that /dev/kvm exists
> 2) check the permissions on /dev/kvm
> 3) check dmesg for kvm disabled messages
>
> I see this sort of thing with KVM fairly frequently, and usually point
> people to run kvm-ok to get a hint. We should update these hints.
>
Sounds like a good option.
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://