Hi, all,
I'm attempting to run a Windows 2003 (32-bit) VM under CentOS 5.4, generally following:
http://wiki.centos.org/HowTos/KVM
I've seen nice performance benefits with the VirtIO driver under Fedora, so I'd like to get that running with CentOS as well. I have the September drivers build .iso.
According to:
http://www.linux-kvm.org/page/Virtio
I need a KVM version 60 or later - fair enough. Back at the wiki there's a note about later KVM in -testing, and sure enough there's a -66 there, but it's only built for an old kernel.
I got that SRPM and tried to build it against the current kernel, but get kmod build errors, ala:
/root/rpmbuild/BUILD/kvm-kmod-66/_kmod_build_/kernel/external-module-compat.h:421: error: redefinition of typedef 'bool' ...
/root/rpmbuild/BUILD/kvm-kmod-66/_kmod_build_/kernel/external-module-compat.h:734:1: warning: "__aligned" redefined
The wiki also has a note about -84 being in Levente Farkas's repo, but those don't appear to be there any longer.
So, questions: 1) what are folks generally using for VirtIO-capable KVM on CentOS 5.4? 2) given that the upstream has Windows drivers available, I'm curios how they're handling the issue, and if we're in sync. 3) does anybody have the SRPM that was at Farkas's repo or know if it went elsewhere? I assume the build issues have been solved there already.
I'd be happy to update the Wiki with info from responses here.
Thanks, -Bill
Bill McGonigle wrote:
Hi, all,
I'm attempting to run a Windows 2003 (32-bit) VM under CentOS 5.4, generally following:
ARGHH ... forget that page as it was written during the first kvm tests and ïsn't current anymore see http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtualiz... for accurate documentation (as http://www.centos.org/docs is outdated and doesn't even cover kvm)
I've seen nice performance benefits with the VirtIO driver under Fedora, so I'd like to get that running with CentOS as well. I have the September drivers build .iso.
According to:
http://www.linux-kvm.org/page/Virtio
I need a KVM version 60 or later - fair enough. Back at the wiki there's a note about later KVM in -testing, and sure enough there's a -66 there, but it's only built for an old kernel.
I got that SRPM and tried to build it against the current kernel, but get kmod build errors, ala:
/root/rpmbuild/BUILD/kvm-kmod-66/_kmod_build_/kernel/external-module-compat.h:421: error: redefinition of typedef 'bool' ...
/root/rpmbuild/BUILD/kvm-kmod-66/_kmod_build_/kernel/external-module-compat.h:734:1: warning: "__aligned" redefined
The wiki also has a note about -84 being in Levente Farkas's repo, but those don't appear to be there any longer.
So, questions:
- what are folks generally using for VirtIO-capable KVM on CentOS 5.4?
The standard kvm from 5.4 and not the *old* one from extras
- given that the upstream has Windows drivers available, I'm curios how
they're handling the issue, and if we're in sync. 3) does anybody have the SRPM that was at Farkas's repo or know if it went elsewhere? I assume the build issues have been solved there already.
I'd be happy to update the Wiki with info from responses here.
Thanks, -Bill
On 01/21/2010 04:08 PM, Fabian Arrotin wrote:
The standard kvm from 5.4 and not the*old* one from extras
Hrm, this is probably where I'm going wrong. I have kvm -36 from -extras (which bails if you specify a virtio type device). I'm not seeing kvm in the repos for 5.4 or updates/5.4 on mirror.centos.org, i.e.:
http://mirror.centos.org/centos-5/5.4/os/i386/CentOS/
Which version should I be seeing for 5.4?
-Bill
On 01/21/2010 10:59 PM, Bill McGonigle wrote:
On 01/21/2010 04:08 PM, Fabian Arrotin wrote:
The standard kvm from 5.4 and not the*old* one from extras
Hrm, this is probably where I'm going wrong. I have kvm -36 from -extras (which bails if you specify a virtio type device). I'm not seeing kvm in the repos for 5.4 or updates/5.4 on mirror.centos.org, i.e.:
http://mirror.centos.org/centos-5/5.4/os/i386/CentOS/Which version should I be seeing for 5.4?
AFAIK Red Hat only supports KVM for the x86_64 architecture so if you want to use it on i386 you have to build your own packages.
Regards, Dennis
On 01/21/2010 11:04 PM, Dennis J. wrote:
AFAIK Red Hat only supports KVM for the x86_64 architecture so if you want to use it on i386 you have to build your own packages.
Has anyone tried building the kvm packages shipped by redhat on i386 ? apart from the spec file, are there any other changes required ?
- KB
On 01/21/2010 07:01 PM, Karanbir Singh wrote:
Has anyone tried building the kvm packages shipped by redhat on i386 ? apart from the spec file, are there any other changes required ?
I'm working on this right now but running into missing packages as seen here:
http://lists.centos.org/pipermail/centos-devel/2009-November/005178.html
I did find, e.g. kvm in updates/5.4, but not in 5.4/os. Perhaps something was fixed for updates that missed the initial build and the ones without updates are still missing?
yum-builddep is at least asking for iasl and qspice, qspice requiring qcairo, but I'm stuck at that point.
-Bill
On Thu, Jan 21, 2010 at 4:32 PM, Bill McGonigle bill@bfccomputing.com wrote:
On 01/21/2010 07:01 PM, Karanbir Singh wrote:
Has anyone tried building the kvm packages shipped by redhat on i386 ? apart from the spec file, are there any other changes required ?
I'm working on this right now but running into missing packages as seen here:
http://lists.centos.org/pipermail/centos-devel/2009-November/005178.html
I did find, e.g. kvm in updates/5.4, but not in 5.4/os. Perhaps something was fixed for updates that missed the initial build and the ones without updates are still missing?
yum-builddep is at least asking for iasl and qspice, qspice requiring qcairo, but I'm stuck at that point.
In fact, there is a bug report about missing source rpms:
http://bugs.centos.org/view.php?id=4042
Akemi
On 01/22/2010 12:40 AM, Akemi Yagi wrote:
This one I can fix :)
п'ятниця 22 січень 2010 02:01:12 Karanbir Singh ви написали:
On 01/21/2010 11:04 PM, Dennis J. wrote:
AFAIK Red Hat only supports KVM for the x86_64 architecture so if you want to use it on i386 you have to build your own packages.
Has anyone tried building the kvm packages shipped by redhat on i386 ? apart from the spec file, are there any other changes required ?
- KB
server % rpmbuild -bb --sign kvm.spec ~/rpmbuild/SPECS Enter pass phrase: Pass phrase is good. error: Architecture is not included: i386
On 01/22/2010 01:01 AM, Karanbir Singh wrote:
On 01/21/2010 11:04 PM, Dennis J. wrote:
AFAIK Red Hat only supports KVM for the x86_64 architecture so if you want to use it on i386 you have to build your own packages.
Has anyone tried building the kvm packages shipped by redhat on i386 ? apart from the spec file, are there any other changes required ?
yes, but the qslice and other dependencies and not build on 32 bit (or at least require moire work). anyway who like to run the host on 32 bit and why?
On 01/22/2010 07:08 AM, Farkas Levente wrote:
anyway who like to run the host on 32 bit and why?
In my case it's on a small business server - kvm is meant to replace VMWare with a better/Free option. That server is multi-purpose, including running a proprietary database (app vendor requirement), so switching arches would require an expensive and time-consuming re-validation of the entire system. Switching virt methods only requires re-validating the virtualized system and minimizes downtime.
But that's probably only one of myriad scenarios. When the package problem is fixed, I'll have a go at building them, perhaps seeing what Fedora is doing differently if there's something that doesn't work.
If that proves too difficult, I'd probably take this system and convert it to a 32-bit guest and then just run a the VM's in parallel. That's closer to an ideal solution, but again more expensive and more downtime.
-Bill
On 01/21/2010 09:42 PM, Bill McGonigle wrote:
- does anybody have the SRPM that was at Farkas's repo or know if it
went elsewhere? I assume the build issues have been solved there already.
i remove all of my rpm because in 5.4 everything is working and supported by rh. which is much better to use and maintain then a separate set of packages.
-
Akemi Yagi -
Bill McGonigle -
Dennis J. -
Fabian Arrotin -
Farkas Levente -
Karanbir Singh -
Sergiy Yegorov