On 03/03/2010 10:20 PM, Lawrence Tsang wrote:
> Hi All,
>
> I am a newbie using VirtualBox 3.1.4 on a Ubuntu 9.10 (Karmic)
> i386 host. I have problem starting a new virtual machine that I have
> not yet installed any system on it.
>
> When the VM is started, a dialog appears saying that :
>
> Failed to start the virtual machine WinXP Pro (for VirtualBox 3.1.4).
> VirtualBox can't operate in VMX root mode. Please disable the KVM
> kernel extension, recompile your kernel and reboot
> (VERR_VMX_IN_VMX_ROOT_MODE).
First, run:
lsmod | grep kvm
I bet you have either kvm_intel or kvm_amd loaded as a module.
if either show up, then run:
sudo modprobe -r kvm_intel
or
sudo modprobe -r kvm_amd
then you should be able to start your guest OS.
If you still cannot or kvm_* modules are not loaded, then check your
PC's BIOS to make sure hardware virtualization is enabled.
>
> Details :
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}
>
> The settings of my new VM are :
>
> General
> Name: WinXP Pro (for VirtualBox 3.1.4)
> OS Type: Windows XP
> 
> System
> Base Memory: 256 MB
> Processor(s): 1
> Boot Order: Floppy, CD/DVD-ROM, Hard Disk
> VT-x/AMD-V: Disabled
> Nested Paging: Disabled
> 
> Display
> Video Memory: 16 MB
> 3D Acceleration: Disabled
> 2D Video Acceleration: Disabled
> Remote Display Server: Disabled
> 
> Storage
> IDE Controller
> IDE Primary Master: Win XP Pro.vdi (Normal, 10.00 GB)
> IDE Secondary Master (CD/DVD): Host Drive HL-DT-ST DVD-RAM GSA-H54N
> (sr0)
> Floppy Controller
> Floppy Device 0: Empty
> 
> Audio
> Host Driver: PulseAudio
> Controller: ICH AC97
> 
> Network
> Adapter 1: PCnet-FAST III (NAT)
> 
> Serial Ports
> Disabled
> 
> USB
> Device Filters: 0 (0 active)
> 
> Shared Folders
> None
>
> My motherboard has the amd64 architecture with 2GB ram. However,
> I am using the Ubuntu Karmic Desktop i386 (32bit) as a host with the
> "vmlinuz-2.6.31-19-generic" kernel that I think it is the most current
> stable release.
>
> Could anyone suggest a solution to fix this problem?
>
> Regards
> Lawrence
>
>
> _______________________________________________
> vbox-users mailing list
> vbox-users@virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-users
>
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
