On Sat 06 Sep at 00:22:16 +0300 [EMAIL PROTECTED] said: > On Fri, Sep 5, 2008 at 11:28 PM, Tim Pepper <[EMAIL PROTECTED]> wrote: > >....snip > > > > > The host specifics are standard current fedora/livna: > > kernel-2.6.25.14-108.fc9.i686 > > qemu-0.9.1-6.fc9.i386 > > kmod-kqemu-1.3.0-0.38.lvn9.i686 > > kmod-kqemu-2.6.25.14-108.fc9.i686-1.3.0-0.38.lvn9.i686 > > kqemu-1.3.0-0.7.pre11.lvn9.noarch > > And the host hardware is Intel core duo. > >....snip > > I am not currently running fedora so I'd like to know what version of > kvm (kernel modules and userspace) are you running? > > Anyways, the vmexit is caused because the guest is in an invalid state > and fails VMX entry checks. I'll look further into the output to see > where exactly the guest fails.
Is this what you're looking for: $ qemu-kvm --help QEMU PC emulator version 0.9.1 (kvm-65), Copyright (c) 2003-2008 Fabrice Bellard The kernel is 2.6.25.14, but it's fedora's -108. If desired, I can grab the src rpm and see if there are any patches that might be kvm related. The rpm's changelog doesn't show any since they'd rebased from 2.6.15.14, but that doesn't necessarily mean anything... -- Tim Pepper <[EMAIL PROTECTED]> IBM Linux Technology Center -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
