[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Windows 2008 SBS on Xen 3.4 does not install


  • To: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
  • From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
  • Date: Sat, 30 Oct 2010 04:25:06 +0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 29 Oct 2010 13:27:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YJ891Hm8rrBPfO+pdhs9LMw7VFKinUcWZjYWmfomaIVbBj7AasnPPvOCSeDcPr9TsV eVGFwl3TrmPQY/DUJ/2uutF9XHEvu7yVBJhlYqyWFsnNy+riBvN22myRsaebnq74LxrC OsEKBz8uypu7IN8PlC54vlEeg6uDbCdFf65lo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Sorry, not sure about OpenSuse package related to Xen.  Each Xen
version will have its correspond qemu git tree
(qemu-xen-3.3-testing.git, qemu-xen-3.4-testing.git,
qemu-xen-4.0-testing.git etc... ...) that can be updated over time.
Perhaps it might be the qemu related issue?  Not sure just wild guess
:p  Anyone?

Personally I preferred to run xen-3.4.x or xen-4.0.x with xenlinux
2.6.18.8 for HVM related.  Don't try pvops kernel if you just intend
to run HVM guests in production at least for now.  One thing about
pvops kernel is that you can't allocate dom0 mem to 512MB or even
less... that will cause memory oops prior to start your first HVM or
even PV guest.  I set mine to 1GB in order not to cause memory oops or
else the host is so slow until ssh session disconnected and a reboot
is required :(  Whereby for xenlinux
(http://xenbits.xen.org/linux-2.6.18-xen.hg) as dom0, I can allocate
dom0 mem to 256MB and it run fine and stable for months!  Even with 6
HVMs with windows 2K3 guests without issue.  Just personal experience.
 Sorry for being off-topic :p

Thanks.

Kindest regards,
Giam Teck Choon



On Sat, Oct 30, 2010 at 4:00 AM, Bart Coninckx <bart.coninckx@xxxxxxxxxx> wrote:
> Hi,
>
> I'm using the OpenSuse packages (on OpenSuse obviously). I get the "boot"
> thing, no worries. I've managed to install it on my laptop using Xen 4.0.
> Didn't work with a sparse file though, had to alocate all space before hand.
> On my production hypervisors I upgraded to 4.0 as well, but for now it doesn't
> work there. I suspect however that this has something to do with the
> underlying storage (iSCSI) so I'm now testing with local storage.
>
> I'm happy to hear that Al these versions are supposed to run fine.
> So what version of Xen do you prefer for running M$?
>
>
> thx!
>
>
> B.
>
> On Friday 29 October 2010 21:52:15 Teck Choon Giam wrote:
>> May I know your Xen is installed via source or ?
>>
>> Actually you need to set boot = 'cd' as the boot will boot drive c
>> then followed by drive d.  Without the c after successfully
>> installation, it will still go and boot to your drive d.  It is like
>> setting your BIOS boot order.  Someone correct me if I am wrong.  My
>> configuration never change during installation of any windows guest
>> OSes and after. It works fine for xen-3.3.x, xen-3.4.x and xen-4.0.x.
>> I have tested such installation for windows 2008, windows 2008 R2,
>> windows 7, windows XP, windows vista and RHEL6.  However, my host is
>> CentOS 5 though.
>>
>> Thanks.
>>
>> Kindest regards,
>> Giam Teck Choon
>>
>> On Fri, Oct 29, 2010 at 4:45 PM, Bart Coninckx <bart.coninckx@xxxxxxxxxx>
> wrote:
>> > On Thursday 28 October 2010 19:40:32 Bart Coninckx wrote:
>> >> Hi,
>> >>
>> >> trying to install Windows 2008 Small Business Server 64bit on Xen 3.4 on
>> >> opensuse 11.2.
>> >>
>> >> The install runs fine, but after the first reboot, the VNC console
>> >> shows:
>> >>
>> >> boot mgr is missing
>> >>
>> >> When I try to repair that with the install CD, I cannot see the
>> >> previously installed C: partition, as if drivers are missing or
>> >> something.
>> >>
>> >> Does any know of Windows 2008 SBS is installable at all? I've recently
>> >> installed a regular Windows 2008 Server on Xen 3.2 and that was not an
>> >> issue. R2 was of course.
>> >>
>> >> This is my config file:
>> >>
>> >> name="win1"
>> >> uuid="c157bc27-b978-0e46-c799-3b7bc64eb0ac"
>> >> memory=8192
>> >> maxmem=8192
>> >> vcpus=2
>> >> on_poweroff="destroy"
>> >> on_reboot="restart"
>> >> on_crash="destroy"
>> >> localtime=1
>> >>
>> >> builder="hvm"
>> >> extid=1
>> >> device_model="/usr/lib/xen/bin/qemu-dm"
>> >> kernel="/usr/lib/xen/boot/hvmloader"
>> >> boot="d"
>> >> #disk=[ 'phy:/dev/mapper/win1c,hda,w', 'phy:/dev/mapper/win1d,hdb,w',
>> >> 'file:/mnt/nfs1/DVD1_Installation.iso,hdc:cdrom,r', ]
>> >> disk=[ 'phy:/dev/mapper/win1c,hda,w',
>> >> 'file:/mnt/nfs1/DVD1_Installation.iso,hdc:cdrom,r', ]
>> >> vif=[ 'bridge=br0,model=rtl8139', ]
>> >>
>> >>
>> >> stdvga=0
>> >> vnc=1
>> >> vncunused=1
>> >> apic=1
>> >> acpi=1
>> >> pae=1
>> >>
>> >> usb=1
>> >> usbdevice='tablet'
>> >>
>> >> serial="pty"
>> >>
>> >>
>> >> Thx!
>> >>
>> >> Bart
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-users
>> >
>> > Further investigation revealed that the installation reboots while
>> > extracting files, so the installation does not get to finish entirely.
>> > I'm testing now on Xen 4.0. Up till now it gets simpley stuck while
>> > extracting the files, once at 16%, once at 74%. Trying to see if this
>> > has to do with free disk space on my test machine. But my guess is it
>> > won't work on Xen 3.4. 4.0 Remains a question.
>> >
>> > B.
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-users
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.