Bharat Kumar Rayudu
2007-Aug-05 18:25 UTC
[Xen-users] Re: Xen-users Digest, Vol 30, Issue 15
Hi, we are facing a serious problem in setting up XEN Gest upgradationf from SLES10 to SLES10 SP1 Two things we need to perform.(SUSE 1) upgrade the HOST OS from SLES10 to sles10 SP1 and 2) Upgrade the Guest OS from SLES10 to SLES10 SP1 please can anyone help us in resolving this Thanks in advance bharat On 8/5/07, xen-users-request@lists.xensource.com < xen-users-request@lists.xensource.com> wrote:> > Send Xen-users mailing list submissions to > xen-users@lists.xensource.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users > or, via email, send a message with subject or body ''help'' to > xen-users-request@lists.xensource.com > > You can reach the person managing the list at > xen-users-owner@lists.xensource.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xen-users digest..." > > > Today''s Topics: > > 1. Etch Xen3.0.3: HVM XP with LVM problems (Denny Schierz) > 2. Re: xen and windows xp (Bob Gamble) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 05 Aug 2007 12:13:29 +0200 > From: Denny Schierz <linuxmail@4lin.net> > Subject: [Xen-users] Etch Xen3.0.3: HVM XP with LVM problems > To: "''xen-users@lists.xensource.com''" <xen-users@lists.xensource.com> > Message-ID: <46B5A2C9.80706@4lin.net> > Content-Type: text/plain; charset="iso-8859-15" > > hi, > > i created a hvm config for XP. The disk is a LVM Volume with 2GB space, > but after starting the installation, windows shows only 1MB as partition > space: > > kernel = "hvmloader" > builder = ''hvm'' > memory = 512 > name = ''winxp'' > boot = "d" > on_reboot = ''destroy'' > vif = [ ''type=ioemu'' ] > disk = [ ''phy:daten/xp,hda,w'',''file:/mnt/xp.iso,hdc:cdrom,r'' ] > shadow_memory = 8 > device_model = ''qemu-dm'' > sdl = 0 > vnc = 1 > vnclisten = "0.0.0.0" > usb = 1 > usbdevice = ''tablet'' > stdvga = 0 > audio = 0 > > > any suggestions? > > cu denny > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 252 bytes > Desc: OpenPGP digital signature > Url : > http://lists.xensource.com/archives/html/xen-users/attachments/20070805/142660f1/signature.pgp > > ------------------------------ > > Message: 2 > Date: Sun, 5 Aug 2007 02:46:01 -0800 > From: "Bob Gamble" <kiksadiweb@gmail.com> > Subject: Re: [Xen-users] xen and windows xp > To: Ana <christiana@hipointcoffee.com> > Cc: xen-users@lists.xensource.com > Message-ID: > <678294a50708050346t1bfddfbawd4d45a86ee45f058@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Thank you all for your help. For whatever reason it took me some time to > get a working config for windows xp. I did end up uninstalling Centos'' > version of Xen and went with xensource''s open source 3.1 version. I used > > http://blog.fupps.com/2007/07/05/your-computer-will-be-more-reliable/#comment-1141as > a reference. Here is the config I got to work: > > name = "winxp" > builder = "hvm" > memory = "500" > disk = [ > ''file:/xen/win/winxp.img,hda,w'', > ''file:/home/bob/WindowsXP/winxp_sp2.iso,hdc:cdrom,r'' ] > boot=''c'' > vif = [ ''type=ioemu, mac=00:16:3e:0e:b6:e5, bridge=xenbr0'' ] > uuid = "c74d2249-9907-5c68-f7ac-314dd11ae7aa" > device_model = "/usr/lib64/xen/bin/qemu-dm" > kernel = "/usr/lib/xen/boot/hvmloader" > vnc=0 > vncunused=0 > apic=0 > acpi=0 > sdl=1 > vcpus=2 > serial = "pty" # enable serial console > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > usb=1 > audio=1 > > I hope this helps someone. > > On 6/30/07, Ana <christiana@hipointcoffee.com> wrote: > > > > On Fri, Jun 29, 2007 at 11:47:22AM +0200, Petersson, Mats wrote: > > > > Does anyone have an idea of what may be preventing me from > > > > running this Windows XP 64 system in a DOMu? I have also > > > > tried a 32 bit system with the same results. Thank you. > > > > > > I don''t see why 32-bit XP shouldn''t work in this setup - I''m pretty > > > certain that it should work. I can also with almost certainty say that > > > 3.0.3 doesn''t support 64-bit XP version. You need 3.0.4 for that (I > > > would recommend an upgrade to 3.1, as it has a bunch of other > > > improvements too). > > > > I had trouble with installing 32-bit WinXP on a Debian 64-bit AMD system > > until I installed 3.1. Since then it''s been smooth sailing. > > > > - Ana > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.xensource.com/archives/html/xen-users/attachments/20070805/ce05a4e9/attachment.html > > ------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > End of Xen-users Digest, Vol 30, Issue 15 > ***************************************** >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Horn
2007-Aug-06 06:38 UTC
Re: [Xen-users] upgrade dom0+domU SLES10->SLES10SP1, was: Re: Xen-users Digest, Vol 30, Issue 15
On Sun, Aug 05, 2007 at 11:55:50PM +0530, Bharat Kumar Rayudu wrote:> > we are facing a serious problem in setting up XEN Gest upgradationf from > SLES10 to SLES10 SP1 > > Two things we need to perform.(SUSE > 1) upgrade the HOST OS from SLES10 to sles10 SP1 and > 2) Upgrade the Guest OS from SLES10 to SLES10 SP1 > > please can anyone help us in resolving thisThis is now fun, upgrading a dom0 to SP1 with yast and an internet-connection is complicated (involves handing over your dom0 to another suse-update-server) and didnt work for me. I ended up updating the installed packages with the ones from the SP1-cd-isos by hand (rpm -Fvh) and checking with SPident (from SP1) that the new packages are complete. If the updating with yast to SP1 doesnt work for you your could also open up a call at suse, after all you pay for the enterprise-stuff. Didnt want to do that. For later updating its good to set up a yup (yast update proxy), this requires the credentials of one sles10sp1-machine to fetch updates. rug on other SP1-servers and domU can then be configured to use the internal yup for updating (just used this in the SLES10 and SLES10SP1-lines though, not the upgrade to SP1). Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users