I'm familiar with Gitco, and it is a very good repo, however, using Gitco to go to 3.4x killed my "standard" Centos installation and it (Xen) didn't work on 3.3x on my hardware.
I tried repo'ing in Gitco a couple of times, with yum priorities toggled on/off and different priority labels. Then I tried it with a fresh install, put on Yum AllowDowngrade util, but either I didn't have it config'd right, because it didn't allow a downgrade.
I was hoping that with a prerolled Xen binary, and a manual grub.conf entry, I could try it. But I just am clueless on depmod's impact on my "decent" installation.
I have two more Xen machines to build out, I could test on them I guess. I just would have felt a little more comfortable if Xen 3.4x deals with GPLPV as well as I have read (no PCI connection on Xen 3.1). The most very important thing is that the XenPV Shutdown Monitor does work, though disk speed doesn't seem to benefit from it. I must say Win2k8 is a disappointment over Win2k3 so far. Win2k3 was decent, fairly lean and very fast, virtual or "real."
Adam wrote:
Check out this repository for Xen 3.4
-Adam
On Thu, Oct 8, 2009 at 8:38 AM, Phil Schaffner <Philip.R.Schaffner@nasa.gov mailto:Philip.R.Schaffner@nasa.gov> wrote:
Ben M. wrote on 10/06/2009 01:24 PM: > I have a "fairly" stable Xen (CentOS 5.3 "standard" 3.1.x Xen) install > that I want to put into production within the next two weeks or so. > > I have some small (so far non-fatal) issues and tweaks that Xen 3.4.x > may address. E.g. AMD x64 IOMMU bios read, GPLPV PCI connection, HPET > clock, better GPLPV handling, and some others. > > My question is: that if I follow the directions at stacklet.com <http://stacklet.com> > (<http://stacklet.com/downloads/kernel>) to load up Xen 3.4 can/will > depmod overwrite dependencies needed for my "standard" Xen kernel that > will not be available by a simple edit of grub.conf to restore the > "standard" Xen kernel. I'm not familiar with depmod's actions. You shouldn't have to worry about depmod - it will only operate on the current running kernel, or the one you explicitly tell it to, and there should be no direct interaction with GRUB. I'd be much more worried about installing tarballs onto an RPM based system, as Stacklet seems to want to do from my brief look at the site you referenced. Be sure you have a good backup before proceeding with that. Phil _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org <mailto:CentOS-virt@centos.org> http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt