Thanks again for all your responses. So far
Using #> egrep '(vmx|svm|vme)' --color=always /proc/cpuinfo I have vme and vmx as you can see below: Paul Leeming Teleca Sunley House, 46 Jewry Street, Winchester, Hampshire, SO23 8RY Phone: +441962868225, Fax: +441962868867 [email protected] http://www.teleca.com/ Teleca Limited, a company registered in England & Wales, registration number 2773878, registered office at 137 Barlow Moor Road, Didsbury, Manchester M20 2PW. VAT registration number GB 674 6583 90 Follow what's going on at Teleca's blog on http://www.whatsyourideaoftomorrow.blogspot.com/. The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited. ___________________________________________________________________ flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow ___________________________________________________________________ Using an intel processor ID tool I found out that my processor can handle virtualization. The related output is below: ___________________________________________________________________ Intel(R) Processor Identification Utility Processor Name: Intel(R) Core(TM)2 Duo CPU T5600 @ 1.83GHz ... Intel(R) Virtualization Technology: Yes ___________________________________________________________________ However, when I do #> modprobe kvm-intel ___________________________________________________________________ FATAL: Error inserting kvm_intel (/lib/modules/2.6.32.11-99.fc12.i686/kernel/arch/x86/kvm/kvm-intel.ko): Operation not permitted ___________________________________________________________________ When researching this error. Much of the information points to using the bios settings to enable virtualization, and indicates that if you don't have the bios setting available (I don't) then its not possible to do this. I have also updated my bios, as it was quite old, but there is still no settings relating to virtualization in the updated version. Paul -----Original Message----- From: Ameya Palande [mailto:[email protected]] Sent: Thu 5/6/2010 10:28 To: ext Sylvia Liu Cc: Paul Leeming; [email protected] Subject: Re: [MeeGo-dev] Image Creation Troubles On Thu, 2010-05-06 at 07:46 +0200, ext Sylvia Liu wrote: > Hi Paul, > 2. My CPU only supports "vme", not "vmx". (see from /proc/cpuinfo) > So I cannot add kvm-intel module. But I still added the kvm module > successfully, and try the qemu-kvm command. Of course I got the same > warnings: > > open /dev/kvm: No such file or directory > > Could not initialize KVM, will disable KVM support > But I can still start the image successfully, the only problem is that > it is really slow. You can check if your cpu support virtualization by checking existence of "vmx (for intel) or svm (for amd)" flags in /proc/cpuinfo. To enable kvm functionality you need 2 modules: 1. kvm 2. kvm-intel or kvm-amd Cheers, Ameya.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
