Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi
I'm working with KVM on Centos 5.4 and everything is ok. but when I compiled a new kernel ( 2.6.30.9) I've got this error KVM: no hardware support, my processor support virtualization and in bios is enabled.
I know that the kvm module not loaded and my processor support virtualization, but I've got the "kvm: no hardware support" error before the booting Centos and in the first page. please help me.
are you sure AMD-V is enabled in the BIOS? If you just enabled it now, you have to not just save the BIOS and restart, you need to do a full powercycle of the server.
Hi,
I want to use kvm as VMM for virtualization, my os is Centos 5.4 and everything is fine when I'm using "2.6.18-164.el5". but for my project I need to compile a kernel so I compile 2.6.31.5 kernel and boot it.
and kvm kernel modules are loaded.
If you want a fresher kernel, why use CentOS? go for Fedora
anyhow, it is possible to debug your issue, or maybe even better - file a BZ for KVM, but why bother when there are distros out there that would just work
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.
Hi
thanks for your replies
I want to make some changes to linux kernel for my M.S project. my problem is with kernel not Centos or Fedora. working with fedora does not solve my problem.
Thing is, since you're using a customer kernel, there's no promise your kernel will work with the default kvm module. If you are doing things from scratch, you better compile kvm from scratch as well
Thing is, since you're using a customer kernel, there's no promise your kernel will work with the default kvm module. If you are doing things from scratch, you better compile kvm from scratch as well
You definetlly should compile the kvm module again. But this is broken with kernel 2.6.31-5 (at least it was on sunday evening). If you find any good walkthrough that gets you to build kvm module on kernel 2.6.31-5 please let me now (I'm tired of searching. I just wait till they update either the kernel or kvm)
I was a bit to fast with calling kvm in 2.6.31-5 broken. Just the way I did it it was broken cause I did not had the proper understanding of the packages one can download on the sourceforge packe of kvm.
The KVM module can be compiled right into the kernel and no extra packages is needed (beside qemu, but I'm talking compiling a new kernel). Just take the old config of your kernel (either from /boot/vmlinu.2.6.x-config or from /proc/config) and jump down to the last one above "Load Configuration" where it says "Virtualization". There you have all the glory of kvm right inside kernel
Just for the cause. I got my undetaking done. Just sharing also it my not help out.
Plan was to get pci pass through to work but the guidelines should be the same to just get a self compiled kernel to have kvm working. (this is on nearly fresh debian lenny with some minor apt-get things like qemu and tasksel installed Desktop)
1.) download kernel (stable version 2.6.31.6)
2.) untar
3.) cd to kernel dir
4.) get config from os (cp /boot/config-2.6.26-2-amd64 ./config)
5.) make menuconfig and "Load configuration" config
6.) Enable all sorts of virtualistation (will fill this out tomorrow)
7.) "Save configuration" as .config
8.) exit configuration
9.) make
10.) make modules_install && make install
11.) update-grup (might need to mkinitramfs *tomorrow*)
12.) restart
13.) the all acknowledged get something to drink && eat ( better suited while waiting for kernel to compile. see 9)
14.) get qemu-kvm from sourceforge (http://sourceforge.net/projects/kvm/...ar.gz/download)
15.) untar and compile qemu-kvm (tar -xzf; cd ...; ./configure && make && make install
16.) /usr/local/bin/qemu-system-x86_64 -m 512 -hda ....
This should get you going. I'll see if I can get some decent tutorial up during the week.
Hope this gets this thread going to build the kernel and install qemu-kvm ...
Lad, your cpuinfo has to have the flag vmx. If it does not have vmx then your CPU is not VT-compatible and it will not provide hardware virtualization. Usually the very expensive CPU's have this such as the Xeon or the newest AMDs 64bit. If you only have the vme flag then that will not be good enough; you need to have vmx in order to have hardware virtualization.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.