(top posting to keep thread consistent)
Then you should remember to pass the qemu options to
start the VM as a XEN DomU, not as a software VM inside
your current (Dom0) VM.
I think (from reading qemu --help) that you may need
to do that via something called xend, there is probably
a manual somew
Hi Dave,
You do know that I'm running a Xen hypervisor and not KVM?
I'm not wedded to Xen and would consider using KVM if it's more likely
to solve my problem, but it would be good to get the Xen solution
working properly.
Regards,
Terry.
Dave Gosselin writes:
> Hi Terry,
>
> It appears that
Hi Terry,
It appears that the kernel driver hasn't been started. You can do this
manually, before starting qemu, by running this as the root user:
modprobe kvm
You can confirm that the modprobe command started via the lsmod
command: lsmod | grep -i kvm
If you see any entries, it's loaded;
Hi Dave,
With -enable-kvm I get.
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
Where to next? I'm willing to help diagnose it in whatever way I can.
Regards,
Terry.
Dave Gosselin writes:
> Try supplying the -enable-kvm opti
Try supplying the -enable-kvm option to your qemu arguments. If it doesn't work
then the support may not be compiled in to qemu or the driver may not be loaded
into the kernel. Let me know.
Dave Gosselin
Sent from my iPhone
> On May 9, 2015, at 18:52, Terry Glanfield wrote:
>
>
> Hi,
>
> I
