From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Ofsthun Subject: Re: Windows SMP Date: Wed, 07 Jan 2009 09:47:26 -0500 Message-ID: <4964C07E.1060804@virtualiron.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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <05bb01c9706c$956828a0$c03879e0$@com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Venefax Cc: xen-devel@lists.xensource.com, 'Andrew Lyon' , 'Dirk Utterback' , 'Keir Fraser' , 'James Harper' List-Id: xen-devel@lists.xenproject.org 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 > > -----Original Message----- > From: Steve Ofsthun [mailto:sofsthun@virtualiron.com] > 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 > > 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 > > I believe the proper sequence is: > > download the SLES10 SDK iso from you Novell support account: > > SLE-10-SP2-SDK-DVD-x86_64-GM-DVD1.iso > > Add this ISO as a yast installation source. > > install the xen-3.2.0_16718_14-0.4.src.rpm rpm via yast or: > > # rpm -i xen-3.2.0_16718_14-0.4.src.rpm > > Note that this is the .src.rpm not the binary rpm. > > Prep the source tree using: > > # rpmbuild -bc /usr/src/packages/SPECS/xen.spec > > This should build, patch and compile the package. If it fails due to dependencies, add the missing RPMs using yast. > > Once it succeeds, apply the attached patch (I attached the wrong one previously): > > # cd /usr/src/packages/BUILD/xen-3.2-testing > # patch -p0 < ~/xen-vioapic-callback-routing.patch > > Build the hypervisor: > > # cd /usr/src/packages/BUILD/xen-3.2-testing > # make xen > > try out the resulting xen/xen.gz manually. > > Steve > > >