| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] guest domain not booting
Hi Marcus,
Answers are scattered throughout the email : ) In short, there is no
obvious reason why it doesn't work. I was thinking today I might try xen
testing.
Enlightenment is most certainly a long and arduous journey... : )
On Mon, 2005-07-25 at 18:03 +1000, Marcus Brown wrote:
> Hi Marco,
>
> I'm using a similar setup on Debian with dom0 using sid
> and multiple domUs using sarge. (Can't remember why now;))
> All domains use kernel 2.6.11.12 (xen testing),
> but each compiled with different options.
> [end long story]
> I haven't really got any answers for you I'm afraid
> so hopefully my questions below won't send you
> off on a wild good chase!
>
> Marco La Rosa wrote:
>
> >Hi all,
> >
> >I'm having problems booting a guest OS. I've used xen-2.0.6-src.tgz.
> >
> >I've compiled a 2.6.11.10-xen0 kernel on both Ubuntu 5.04 and Debian
> >unstable using the stock debian .config files (for 2.6.11). Both of
> >these attempts worked and allow me to boot into dom0.
> >
> >
> I assume you just copied your config to xen/linux-2.6.11.10-xen0
> and did a 'make dist' or 'make kernel-2.6' ?
> If you did it manually make sure to do a
> make ARCH=xen oldconfig (or menuconfig....etc).
> Did you use a Debianised kernel source for your Debianised config?
> (just apt-get a kernel-source and copy it into your xen source root)
I've tried both the stock kernel downloaded by xen and the debianised
version - both with debian .configs. In each case I added the Xen stuff
to the config file then did a make ARCH=xen oldconfig and removed all
the ISA stuff which wouldn't compile (error:
`isa_virt_to_bus_is_UNSUPPORTED' see:
http://lists.xensource.com/archives/html/xen-devel/2004-11/msg00590.html).
Following this, from the top-level directory I issue make kernels &&
make kernels-install.
>
> >The problem is when I try to start a guest domain. LVM2 has been used to
> >create a root device and a swap device which have both been initialised
> >and set up (debian bootstrap used to create the root filesystem - all of
> >the necessary configuration of this guest OS has been done). The
> >xen config file is as follows:
> >
> >#***********************************
> ># -*- mode: python; -*-
> >
> >kernel = "/boot/vmlinuz-2.6.11-xenU"
> >ramdisk = "/boot/initrd.img-2.6.11-xenU"
> >
> >
> Are you sure you need an initrd?
I tried with and without just to be sure. Neither work.
>
> >memory = 256
> >
> >
> Is this much memory free?
> (ie. your system has > 384MB ram?)
Ram is not an issue - I've got 1Gb in the machine. I should've said that
it's a mini-Dell box (Optiplex SX280 if that helps) with integrated
everything - including Intel pci graphics. I've noticed that intel_agp
and agpgart modules get loaded (dom0) at boot time. Knowing that xen-2
and agp don't mix well, I've tried removing them (in fact, I have
removed every single non-essential module - and shutdown all
non-essential dom0 services) but to no avail (note this is a bare bones
debian - no X, no gui, no graphics).
>
> >name = "dom01"
> >cpu = -1 # leave to Xen to pick
> >
> >
> Might as well leave it blank then?
point taken : )
>
> >disk = [ 'phy:xen/dom01root,sda1,w',
> > 'phy:xen/dom01swap,sda2,w']
> >root = "/dev/sda1"
> >#************************************
> >
> >I can start the xend service and query it:
> >
> >
> >
> >>xm list
> >>
> >>
> >Name Id Mem(MB) CPU State Time(s) Console
> >Domain-0 0 123 0 r---- 26.1
> >
> >However, when I try to start the guest domain using:
> >
> >xm create /etc/xen/dom01.conf -c
> >
> >
> If you don't like typing that much:
> xm create dom01
>
> >All i see is the following line of output:
> >
> >Using config file "/etc/xen/dom01.conf".
> >
> >And the machine locks up. I then have to power cycle it. No errors are
> >reported in any of the xen log files.
> >
> >
> Do your syslogs tell you anything?
> Perhaps you could do multiple ssh logins to your dom0
> from another machine and watch a few logs simultaneously?
>
nudda!
krypton:/var/log# tail -f messages
--> nothing
krypton:/var/log# tail -f xend-debug.log
--> nothing
krypton:/var/log# tail -f syslog
--> nothing
Thanx, Marco.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home