Re: Recompiling VirtualBox kernel module [FAILED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2010-04-09 at 11:14 -0500, Dennis Gilmore wrote:

> 
> its a amd specific flag that signifies hardware virtualisation.  intels is vmx so 
> you would run "cat /proc/cpuinfo |grep vmx" if you get a result you have 
> hardware virtulaisation in your cpu.  it could still be disabled in the bios.


Believe me, I have already been through all this. The Pentium 4 does not
have hardware virtualization.


> what parts of it don't work?

I already explained this. On the Pentium 4, which does not have hardware
virtualization, KVM is so slow that it is unusable (it takes 10 minutes
to boot a Windows XP VM). Therefore I use VirtualBox instead. 

On the Core Duo at work, which does have hardware virtualization, KVM
performance is good, but the VM crashes as soon as I access it in the
morning if it is left idle overnight, and I have to reboot the VM. This
is fine for a Windows XP VM that I use just so that I can run a couple
of required proprietary applications at work; usually I remember to
hibernate it before I go home, and it restores just fine. So I continue
to use KVM on my work desktop. But this would not be acceptable in high
availability situations, so I use Xen to run production VM servers.

--Greg


-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux