RE: [Xen-users] Unmodified guests on Dell 380

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Serge Dubrouski
> Sent: 30 May 2006 19:32
> To: Xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Unmodified guests on Dell 380
> 
> The only unmodified OS that I was able to install into DomU 
> on Dell 380 is Windows XP. :-) All Linuxes (I tried FC4 and 
> CentOS) hang at the installation time or at the boot time 
> after installation. Dom0 OS is CentOS 4.3, Xen 3.0.2.

Have either of you tried installing with "no graphics" (however you tell
that to the installer - I don't actually know). From what I understand,
there's some problems with some graphical installers, because they do
"weird things" (like big real-mode and such - which is hard on VT
because they don't have big-real mode - never mind that HVM is brokened
in that it checks for "realmode" and then uses the segment value as a
base address, and if it's NOT realmode, uses a zero-based segment always
- which isn't always right). I'm not SURE if this solves anything, but
I'd give it a try if you haven't... 

--
Mats
> 
> On 5/30/06, Luke <secureboot@xxxxxxxxx> wrote:
> > I'm trying to install and boot any VM guest from any 
> installation CD 
> > on a Dell 380, which seems to be reported as working in some of the 
> > VT-X status emails on this list. VMX is turned on in the BIOS. I'm 
> > using the config file attached here. My dom0 is running 
> Ubuntu dapper, 
> > with bin86 and bcc installed, as well as libvncserver-dev.
> > I've moved tls out of the way. I have an unformatted lvm partition, 
> > and an image of both an openBSD 3.9 boot image and an ubuntu 6.06
> > beta2 cd (changing things appropriately in the config file for the 
> > path of both images). I was under the impression that if 
> I'm booting 
> > and installing from a cdrom, I don't have to format the 
> disk partition 
> > ahead of time. I have 3 disk lines in the config file (one is the 
> > default). When I use the one with ioemu, the domain starts, 
> with the 
> > attached output in xend.log, and nothing in xm dmesg. When I run xm 
> > list, the domain still lists 0.0 cpu time used, and I can't connect 
> > via vnc. When I use the disk line without ioemu, the domain 
> starts and 
> > uses cpu time (as reported by xm), but the vnc output is 
> totally and 
> > completely garbled, and my mouse cursor is just a dot in 
> the window. 
> > The openBSD install starts okay with text, but freezes at the point 
> > where I'm asked to Install, Upgrade, etc. I also can't start the 
> > domains with the -c option, so that i can get information about the 
> > startup of the domains from a terminal, but i understand 
> that this is 
> > normal. What could be happening here? Is some other piece of 
> > information needed to debug this? Or does HVM support just not 
> > practically work at all yet?
> >
> >
> >
> >
> > _______________________________________________
> > 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
> 
> 


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