Here are a couple of Xen 3.2 patches for CentOS 5.1. Just download and install the Xen 3.2 source tarball from xen.org, copy the xen.spec into SPECS and the patches into SOURCE and rebuild. These will 1) allow libvirt to work with 3.2, 2) fix the handling of localtime in 3.2 HVMs. -Ross ______________________________________________________________________ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross S. W. Walker wrote:> Here are a couple of Xen 3.2 patches for CentOS 5.1. > > Just download and install the Xen 3.2 source tarball from xen.org, > copy the xen.spec into SPECS and the patches into SOURCE and > rebuild. > > These will 1) allow libvirt to work with 3.2, 2) fix the handling > of localtime in 3.2 HVMs. >Thanks! Will try them!. Do you know of a way to build the xen-lib RPM for both i386 and x86_64 on a x86_64 system? The usual trick with "--target i386" failed with a conflict in x86_64 and i386 GCC options. Regards, Bas. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bas Mevissen wrote:> > Ross S. W. Walker wrote: > > Here are a couple of Xen 3.2 patches for CentOS 5.1. > > > > Just download and install the Xen 3.2 source tarball from xen.org, > > copy the xen.spec into SPECS and the patches into SOURCE and > > rebuild. > > > > These will 1) allow libvirt to work with 3.2, 2) fix the handling > > of localtime in 3.2 HVMs. > > > > Thanks! Will try them!. Do you know of a way to build the xen-lib RPM > for both i386 and x86_64 on a x86_64 system? The usual trick with > "--target i386" failed with a conflict in x86_64 and i386 GCC options.Why would you need to? Problem is that the xen module needs the kernel headers for your current running platform which will not be accurate when you are setarch''d to i386. Maybe if you can get the i386 xen kernel headers installed, if you use mock you will have better luck I believe. Or run a build under an identical i386 PVM. -Ross ______________________________________________________________________ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross S. W. Walker wrote:>> Thanks! Will try them!. Do you know of a way to build the xen-lib RPM >> for both i386 and x86_64 on a x86_64 system? The usual trick with >> "--target i386" failed with a conflict in x86_64 and i386 GCC options. > > Why would you need to? >Because of dependancies: sudo rpm --test -e xen-libs-3.2.0-0xs.centos5.i386 error: Failed dependencies: libxenstore.so.3.0 is needed by (installed) libvirt-0.2.3-9.el5.i386 Ah, just found out that libvirt.i386 is (no longer?) a dependancy for something I have installed. OK, so now it is purely academic :-)> Problem is that the xen module needs the kernel headers for your > current running platform which will not be accurate when you > are setarch''d to i386. > > Maybe if you can get the i386 xen kernel headers installed, if you > use mock you will have better luck I believe. Or run a build under > an identical i386 PVM. >Hmmm, A CentOS i386 DomU on a x86_64 system. Does that work nowadays? Bas. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bas Mevissen wrote:> > Ross S. W. Walker wrote: > > >> Thanks! Will try them!. Do you know of a way to build the xen-lib RPM > >> for both i386 and x86_64 on a x86_64 system? The usual trick with > >> "--target i386" failed with a conflict in x86_64 and i386 GCC options. > > > > Why would you need to? > > > > Because of dependancies: > > sudo rpm --test -e xen-libs-3.2.0-0xs.centos5.i386 > error: Failed dependencies: > libxenstore.so.3.0 is needed by (installed) libvirt-0.2.3-9.el5.i386 > > Ah, just found out that libvirt.i386 is (no longer?) a dependancy for > something I have installed. OK, so now it is purely academic :-)Yes, I removed the silly artificial dependency with libvirt that RH created, because 3.2 no longer needs libvirt to properly function. It will work with libvirt though. Are you trying to run a 32-bit dom0 with a 64-bit hypervisor? You''re doing it the "poor-man''s method" where you run a 64-bit Xen, 64-bit dom0 and 32-bit userland aren''t you? Technically though one should be able to install the full 32-bit OS, kernel and userland, and then copy the 64-bit /boot/xen.gz and boot that up. It works with 3.1, but 3.2 complains about not enough memory and panics. Probably to do with PAE/non-PAE or some other compile time option.> > Problem is that the xen module needs the kernel headers for your > > current running platform which will not be accurate when you > > are setarch''d to i386. > > > > Maybe if you can get the i386 xen kernel headers installed, if you > > use mock you will have better luck I believe. Or run a build under > > an identical i386 PVM. > > > Hmmm, A CentOS i386 DomU on a x86_64 system. Does that work nowadays?It does with 3.2. -Ross ______________________________________________________________________ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross S. W. Walker wrote:> >> Ah, just found out that libvirt.i386 is (no longer?) a dependancy for >> something I have installed. OK, so now it is purely academic :-) > > Yes, I removed the silly artificial dependency with libvirt that > RH created, because 3.2 no longer needs libvirt to properly function. >Something else (forgot what) was depending on libvirt.i386. So now I could already remove it without breaking something.> Are you trying to run a 32-bit dom0 with a 64-bit hypervisor? >No. All 64-bit until now.> You''re doing it the "poor-man''s method" where you run a 64-bit Xen, > 64-bit dom0 and 32-bit userland aren''t you? >Is is an x86_64 CentOS 5.1 install which also has some i386 stuff installed (by the installer). So the majority of the userland is 64-bit.>> Hmmm, A CentOS i386 DomU on a x86_64 system. Does that work nowadays? > > It does with 3.2. >Great! Will give it a try. Regards, Bas. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bas Mevissen wrote:> Ross S. W. Walker wrote: >> Here are a couple of Xen 3.2 patches for CentOS 5.1. >> >> Just download and install the Xen 3.2 source tarball from xen.org, >> copy the xen.spec into SPECS and the patches into SOURCE and >> rebuild. >> >> These will 1) allow libvirt to work with 3.2, 2) fix the handling >> of localtime in 3.2 HVMs. >> > > Thanks! Will try them!. Do you know of a way to build the xen-lib RPM > for both i386 and x86_64 on a x86_64 system? The usual trick with > "--target i386" failed with a conflict in x86_64 and i386 GCC options.Besides building a 32-bit domain and compiling inside it? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia wrote:> Besides building a 32-bit domain and compiling inside it? >Too easy :-) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bas Mevissen wrote:> Ross S. W. Walker wrote: > > > >> Ah, just found out that libvirt.i386 is (no longer?) a dependancy for > >> something I have installed. OK, so now it is purely academic :-) > > > > Yes, I removed the silly artificial dependency with libvirt that > > RH created, because 3.2 no longer needs libvirt to properly function. > > > > Something else (forgot what) was depending on libvirt.i386. So now I > could already remove it without breaking something. > > > Are you trying to run a 32-bit dom0 with a 64-bit hypervisor? > > No. All 64-bit until now.Oh, OK, I misunderstood. I guess the i386 libvirt was brought in because of another 32-bit app.> > You''re doing it the "poor-man''s method" where you run a 64-bit Xen, > > 64-bit dom0 and 32-bit userland aren''t you? > > Is is an x86_64 CentOS 5.1 install which also has some i386 stuff > installed (by the installer). So the majority of the userland > is 64-bit. > > >> Hmmm, A CentOS i386 DomU on a x86_64 system. Does that work nowadays? > > > > It does with 3.2. > > Great! Will give it a try.Well let the list know how it works for you. -Ross ______________________________________________________________________ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross S. W. Walker wrote on Tue, 22 Apr 2008 10:13:02 -0400:> xen-3.2.0-obey-localtime.patch - ATT701982.txtthanks for posting, however, there''s no file /xen/lowlevel/xc/xc.c on the system, not even a directory xc. /usr/lib/python2.4/site-packages/xen/lowlevel /usr/lib/python2.4/site-packages/xen/lowlevel/__init__.py /usr/lib/python2.4/site-packages/xen/lowlevel/__init__.pyc /usr/lib/python2.4/site-packages/xen/lowlevel/__init__.pyo /usr/lib/python2.4/site-packages/xen/lowlevel/acm.so /usr/lib/python2.4/site-packages/xen/lowlevel/flask.so /usr/lib/python2.4/site-packages/xen/lowlevel/ptsname.so /usr/lib/python2.4/site-packages/xen/lowlevel/xc.so /usr/lib/python2.4/site-packages/xen/lowlevel/xs.so This is all I have there. And, yes, it''s surely Xen 3.2. The other patch is the one I already tried and didn''t change the behavior. I applied it manually, though, I''ll try if using patch is better. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>Here are a couple of Xen 3.2 patches for CentOS 5.1. > >Just download and install the Xen 3.2 source tarball from xen.org, >copy the xen.spec into SPECS and the patches into SOURCE and >rebuild. > >These will 1) allow libvirt to work with 3.2, 2) fix the handling >of localtime in 3.2 HVMs. > >-RossHey Ross, I am trying to help another guy out building some rpm''s, would the addition of these files in the respective directories under a mock build environment allow rpm''s to be made from the srpm patched with your changes? Thanks! jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, just put the patches in the SOURCE directory and spec file in the SPEC directory and do an rpmbuild, with or without mock, and it should work. You won''t need these though if you build 3.2.1 as they are included. Just download the tarball into SOURCE and change the name of the tarball in the spec file to match (removing any patches that no longer apply of course). -Ross ----- Original Message ----- From: Joseph L. Casale <jcasale@ActiveNetwerx.com> To: Ross S. W. Walker; xen-users@lists.xensource.com <xen-users@lists.xensource.com> Sent: Sat May 03 19:44:22 2008 Subject: RE: CentOS 5.1 Xen 3.2 patches>Here are a couple of Xen 3.2 patches for CentOS 5.1. > >Just download and install the Xen 3.2 source tarball from xen.org, >copy the xen.spec into SPECS and the patches into SOURCE and >rebuild. > >These will 1) allow libvirt to work with 3.2, 2) fix the handling >of localtime in 3.2 HVMs. > >-RossHey Ross, I am trying to help another guy out building some rpm''s, would the addition of these files in the respective directories under a mock build environment allow rpm''s to be made from the srpm patched with your changes? Thanks! jlc ______________________________________________________________________ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think that we need 3.2 RPM’s for Centos 5.1 or RHEL 5.1 64 Bits that work, tested. I am just not smart enough to install the 3.2 version myself. From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ross S. W. Walker Sent: Monday, May 05, 2008 9:38 AM To: jcasale@ActiveNetwerx.com; xen-users@lists.xensource.com Subject: [Xen-users] Re: CentOS 5.1 Xen 3.2 patches Yes, just put the patches in the SOURCE directory and spec file in the SPEC directory and do an rpmbuild, with or without mock, and it should work. You won''t need these though if you build 3.2.1 as they are included. Just download the tarball into SOURCE and change the name of the tarball in the spec file to match (removing any patches that no longer apply of course). -Ross ----- Original Message ----- From: Joseph L. Casale <jcasale@ActiveNetwerx.com> To: Ross S. W. Walker; xen-users@lists.xensource.com <xen-users@lists.xensource.com> Sent: Sat May 03 19:44:22 2008 Subject: RE: CentOS 5.1 Xen 3.2 patches>Here are a couple of Xen 3.2 patches for CentOS 5.1. > >Just download and install the Xen 3.2 source tarball from xen.org, >copy the xen.spec into SPECS and the patches into SOURCE and >rebuild. > >These will 1) allow libvirt to work with 3.2, 2) fix the handling >of localtime in 3.2 HVMs. > >-RossHey Ross, I am trying to help another guy out building some rpm''s, would the addition of these files in the respective directories under a mock build environment allow rpm''s to be made from the srpm patched with your changes? Thanks! jlc _____ 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users