Daniel Kao wrote:
> Hi All,
> So I have a Intel DQ35JO board, CentOS5.2 x86_64 and I've
> tried to update Xen 3.1.2 to Xen 3.2.1 by using the method
> listed here:
> Unfortunately, (other than the fact that xen-unstable.hg now
> points to 3.3 so I used xen-3.2-testing.hg), the kernel from
> the mercurial repository of 2.6.18 is missing some modules
> that CentOS 5.2 has for the Intel DQ35JO. I can boot fine
> after compile & installation of the new kernel, but I'm
> missing modules that linux-2.6.18-xen.hg doesn't have which
> CentOS 5.2 kernels do have. They are:
> 1. The pata_marvell module for the ATA ports.
> 2. The e1000e module (not the e1000).
> 3. The video driver for the Intel Q35 IGP.
> I'm currently running kernel 2.6.18-92.1.6.el5xen and grabbed
> the SRPMS for it.
> After unpacking it, the directory structure looks like this
> in the BUILD folder:
> I've grabbed xen-3.2.1.tar.gz and I'm trying to follow
> directions from the following thread:
> But I'm not sure how to properly make the TARBALL of CentOS's
> Xenified kernel to feed to during the 3.2.1 compile (and the
> methods and hacks to use your own kernel source vs. Xen's),
> *and* enable the PCI-Device Backend Driver for Intel VT-d
> support. I think once I get past that point, I'd be able to
> continue from all of the rest of the documentation. If I'm
> successful, I'd be more than happy to create RPM's for CentOS
> 5.2 x86_64 for Xen 3.2.1 with VT-d support turned on in the kernel.
Don't use the xen kernel from xen.org just the hypervisor.
Download the 3.2 SRPM from xen.org, download the 3.2.1 tarball,
put the 3.2.1 tarball into the SOURCES directory, edit the
3.2 spec file and change the version to 3.2.1 then do an
rpmbuild of the spec.
This will produce RPMs that you can then substitute the CentOS
ones with and it won't compile the kernel just the hypervisor,
continue to use the CentOS supplied xen kernels with the
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.
Xen-users mailing list