On Friday 09 April 2010 09:22:44 am Greg Woods wrote: > On Fri, 2010-04-09 at 08:15 -0500, Dennis Gilmore wrote: > > what do you get for "cat /proc/cpuinfo |grep svm" what model cpus do you > > have? > > No output at all. Dual core Pentium 4: > > model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz 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. > > it seems vmware and virtual box regularly > > break because there kernel modules don't build and you are left on your > > own to fix it. > > There are definite advantages to using things that are part of the > mainline kernel. When they work. For me, KVM often doesn't work, so I > have to use something else. It's that simple. what parts of it don't work? I use only kvm and run lots of guests. including ones that see a significant work load. and have not experienced issues. im using rhel5 and fedora 12 hosts. and a mixture of os's as guests. from fedora to rhel, to debian, and open solaris. im not running windows guests so im not sure how they work. > For what it's worth, Xen is supported by Red Hat in RHEL 5 (and > therefore by CentOS 5 as well), despite not being part of mainline. > VirtualBox is of course "on your own", but I have never had a problem > getting the kernel modules to build. I *have* had that problem with > VMware which, along with the $300 price tag for VMware Workstation, was > the reason for switching to VirtualBox in the first place. > > --Greg
Attachment:
signature.asc
Description: This is a digitally signed message part.
-- 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
