From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Venefax" Subject: RE: Windows SMP Date: Wed, 7 Jan 2009 09:57:08 -0500 Message-ID: <065c01c970d8$3753dea0$a5fb9be0$@com> References: <069e01c96b55$3c834d80$b589e880$@com> <4962588D.7080204@virtualiron.com> <03d101c96f68$eec4da10$cc4e8e30$@com> <496267EF.5070508@virtualiron.com> <03e901c96f72$3029a400$907cec00$@com> <4963CB1D.60501@virtualiron.com> <05bb01c9706c$956828a0$c03879e0$@com> <4964C07E.1060804@virtualiron.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4964C07E.1060804@virtualiron.com> Content-Language: en-us List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: 'Steve Ofsthun' Cc: 'Dirk Utterback' , xen-devel@lists.xensource.com, 'Andrew Lyon' , 'Keir Fraser' List-Id: xen-devel@lists.xenproject.org It booted fine, but then I found out that I actually went back in my = version. Please let me know if I should go ahead or not. I downloaded = the source file that you instructed me, xen-3.2.0_16718_14-0.4.src.rpm, = but it turns out that I was using 3.2.0_16718_18-0.3.src.rpm, which I = could not find in Google or Novell. I applied the patch and after = rebooting I found that I am of course using _14-0.4 instead of 18-0.3. = So the question is, does it matter? Or is it better to use this lower = version with the patch? If it matters indeed, how do I get the _18.03 = source rpm? The other question is: is it possible to update the whole xen + tools to = 3.3.1rc4 in Suse 10 SP2 and is this patch still valid in that scenario? Federico -----Original Message----- From: xen-devel-bounces@lists.xensource.com = [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Steve = Ofsthun Sent: Wednesday, January 07, 2009 9:47 AM To: Venefax Cc: xen-devel@lists.xensource.com; 'Andrew Lyon'; 'Dirk Utterback'; = 'Keir Fraser'; 'James Harper' Subject: Re: [Xen-devel] Windows SMP Venefax wrote: > I went as far as "make xen". The question is now what do I do to use = this new, patched hypervisor, I mean, how do I put in production? A = simple reboot? Please advise. As we don't want to assume that this test xen will even boot, the safest = thing is to edit your /boot/grub/menu.lst (or use yast [System -> Boot = Loader]) to copy your current xen boot entry. Leave everything = identical between the two entries except for the hypervisor (change = /boot/xen.gz to /boot/xen-test.gz) and the title line to indicate the = test entry (add something like "- test" to the end of the title line). = If you use yast, the title entry is in the label column. Copy your newly created xen.gz to /boot/xen-test.gz (be careful not to = copy your new file on top of any existing /boot/xen.gz). Reboot the node and manually select the test selection. If the boot = succeeds, try your experiment. If the boot fails, just reboot normally = and verify your changes to the menu.lst. > Federico >=20 > -----Original Message----- > From: Steve Ofsthun [mailto:sofsthun@virtualiron.com]=20 > Sent: Tuesday, January 06, 2009 4:20 PM > To: Venefax > Cc: 'Keir Fraser'; 'Andrew Lyon'; 'James Harper'; 'Dirk Utterback'; = xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] Windows SMP >=20 > Venefax wrote: >> Dear Gentlemen >> One silly question, maybe, how do I apply the patch supplied in SLES = SP2? I have not compiled anything from sources. >> Federico >=20 > I believe the proper sequence is: >=20 > download the SLES10 SDK iso from you Novell support account: >=20 > SLE-10-SP2-SDK-DVD-x86_64-GM-DVD1.iso >=20 > Add this ISO as a yast installation source. >=20 > install the xen-3.2.0_16718_14-0.4.src.rpm rpm via yast or: >=20 > # rpm -i xen-3.2.0_16718_14-0.4.src.rpm >=20 > Note that this is the .src.rpm not the binary rpm. >=20 > Prep the source tree using: >=20 > # rpmbuild -bc /usr/src/packages/SPECS/xen.spec >=20 > This should build, patch and compile the package. If it fails due to = dependencies, add the missing RPMs using yast. >=20 > Once it succeeds, apply the attached patch (I attached the wrong one = previously): >=20 > # cd /usr/src/packages/BUILD/xen-3.2-testing > # patch -p0 < ~/xen-vioapic-callback-routing.patch >=20 > Build the hypervisor: >=20 > # cd /usr/src/packages/BUILD/xen-3.2-testing > # make xen >=20 > try out the resulting xen/xen.gz manually. >=20 > Steve >=20 >=20 >=20 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel