Mailing List Archive

Interesting...

Does /dev/sda1 exist in dom0? (I'm guessing not as you'll be using udev or
devfs). What happens if you specify 0801 instead of /dev/sda1 in your config
file?

Cheers,
Mark

On Saturday 29 January 2005 05:56, Karl Higgins wrote:
> Hello,
>
> I have a gentoo box running xen 2.0.3 which is unable to boot the ttylinux
> image from sourceforge. I compiled xen, xen0, and xenU from sources.
>
> I have attempted to boot the xenU kernel with / in a file and a logical
> volume and get the same message either way.
>
> error message:
>
> VFS: Cannot open root device "sda1" or unknown-block(8,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,1)
>
> config file passed to "xm create ...":
>
> kernel = "/boot/vmlinuz-2.6.10-xenU"
> memory = 64
> name = "ttylinux"
> nics = 1
> #disk = [ 'phy:hdX_vg/ttylinux_lv,sda1,w' ]
> disk = [ 'file:/root/ttylinux-xen,sda1,w' ]
> root = "/dev/sda1 ro"
> restart = "never"
>
> --
> karl@packettrap.org
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Yes, /dev/sda1 does exist in dom0:

l500r root # ls -l /dev/sda1
brw-rw---- 1 root disk 8, 1 Oct 23 23:28 /dev/sda1
l500r root #

This box was setup as a "tweaked" udev box per the instructions in sections 1
and 2 of:

http://www.gentoo.org/doc/en/udev-guide.xml

It seems that the gentoo init scripts detect this configuration and construct
a set of devices early in the boot then start udevd (still running).

Using 0801 instead of /dev/sda1 yields the following for both the file and
lvm disk:

VFS: Cannot open root device "0801" or unknown-block(8,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)

--
karl@packettrap.org

On Saturday 29 January 2005 07:41, Mark Williamson wrote:
> Interesting...
>
> Does /dev/sda1 exist in dom0? (I'm guessing not as you'll be using udev or
> devfs). What happens if you specify 0801 instead of /dev/sda1 in your
> config file?
>
> Cheers,
> Mark
>
> On Saturday 29 January 2005 05:56, Karl Higgins wrote:
> > Hello,
> >
> > I have a gentoo box running xen 2.0.3 which is unable to boot the
> > ttylinux image from sourceforge. I compiled xen, xen0, and xenU from
> > sources.
> >
> > I have attempted to boot the xenU kernel with / in a file and a logical
> > volume and get the same message either way.
> >
> > error message:
> >
> > VFS: Cannot open root device "sda1" or unknown-block(8,1)
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(8,1)
> >
> > config file passed to "xm create ...":
> >
> > kernel = "/boot/vmlinuz-2.6.10-xenU"
> > memory = 64
> > name = "ttylinux"
> > nics = 1
> > #disk = [ 'phy:hdX_vg/ttylinux_lv,sda1,w' ]
> > disk = [ 'file:/root/ttylinux-xen,sda1,w' ]
> > root = "/dev/sda1 ro"
> > restart = "never"
> >
> > --
> > karl@packettrap.org
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > Tool for open source databases. Create drag-&-drop reports. Save time
> > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

> Using 0801 instead of /dev/sda1 yields the following for both the file and
> lvm disk:
>
> VFS: Cannot open root device "0801" or unknown-block(8,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,1)

Ooops, what I meant was: put 0801 in the disk=[] line. Leave the
root=/dev/sda1 as it is.

Cheers,
Mark

> --
> karl@packettrap.org
>
> On Saturday 29 January 2005 07:41, Mark Williamson wrote:
> > Interesting...
> >
> > Does /dev/sda1 exist in dom0? (I'm guessing not as you'll be using udev
> > or devfs). What happens if you specify 0801 instead of /dev/sda1 in your
> > config file?
> >
> > Cheers,
> > Mark
> >
> > On Saturday 29 January 2005 05:56, Karl Higgins wrote:
> > > Hello,
> > >
> > > I have a gentoo box running xen 2.0.3 which is unable to boot the
> > > ttylinux image from sourceforge. I compiled xen, xen0, and xenU from
> > > sources.
> > >
> > > I have attempted to boot the xenU kernel with / in a file and a logical
> > > volume and get the same message either way.
> > >
> > > error message:
> > >
> > > VFS: Cannot open root device "sda1" or unknown-block(8,1)
> > > Please append a correct "root=" boot option
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(8,1)
> > >
> > > config file passed to "xm create ...":
> > >
> > > kernel = "/boot/vmlinuz-2.6.10-xenU"
> > > memory = 64
> > > name = "ttylinux"
> > > nics = 1
> > > #disk = [ 'phy:hdX_vg/ttylinux_lv,sda1,w' ]
> > > disk = [ 'file:/root/ttylinux-xen,sda1,w' ]
> > > root = "/dev/sda1 ro"
> > > restart = "never"
> > >
> > > --
> > > karl@packettrap.org
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > > Tool for open source databases. Create drag-&-drop reports. Save time
> > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > Tool for open source databases. Create drag-&-drop reports. Save time
> > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

>Yes, /dev/sda1 does exist in dom0:
>
>l500r root # ls -l /dev/sda1
>brw-rw---- 1 root disk 8, 1 Oct 23 23:28 /dev/sda1
>l500r root #
>
>This box was setup as a "tweaked" udev box per the instructions in sections 1
>and 2 of:
>
>http://www.gentoo.org/doc/en/udev-guide.xml
>
>It seems that the gentoo init scripts detect this configuration and construct
>a set of devices early in the boot then start udevd (still running).
>
> Using 0801 instead of /dev/sda1 yields the following for both the file and
>lvm disk:
>
>VFS: Cannot open root device "0801" or unknown-block(8,1)
>Please append a correct "root=" boot option
>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)

Interesting - this message means what it says, viz.\ the guest kernel has
no idea about the device 0801 (/dev/sda1). It should have received info about
this via the control interface during boot -- what does /var/log/xend.log or
/var/log/xend-debug.log in domain0 say? (it may be useful to "tail -f" one or
both of them during the guest boot). Do you see "xen_blk: Initializing virtual
block device driver" on the guest console during boot?

cheers,

S.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

>
> Interesting - this message means what it says, viz.\ the guest kernel has
> no idea about the device 0801 (/dev/sda1). It should have received info
> about this via the control interface during boot -- what does
> /var/log/xend.log or /var/log/xend-debug.log in domain0 say? (it may be
> useful to "tail -f" one or both of them during the guest boot). Do you see
> "xen_blk: Initializing virtual block device driver" on the guest console
> during boot?
>
> cheers,
>
> S.
>

Yes, "xen_blk: Initializing virtual block device driver" appears on the guest
console but so does "register_blkdev: cannot get major 8 for sd".

the requested outputs are below:

guest console:

l500r xen # xm create xm-ttylinux -c
Using config file "xm-ttylinux".
Started domain ttylinux, console on port 9621
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.10-xenU (root@l500r) (gcc version 3.3.4 20040623 (Gentoo
Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6))
#1 Wed Jan 26 23:13:13 CST 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI not present.
Built 1 zonelists
Kernel command line: root=0801 ro
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 498.496 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 60656k/65536k available (2571k kernel code, 4784k reserved, 906k data,
304k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: Intel Pentium III (Coppermine) stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
NET: Registered protocol family 16
PCI: Using configuration type Xen
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Initializing Cryptographic API
i8042.c: Can't read CTR while initializing i8042.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 2.6.2)
Intel(R) PRO/1000 Network Driver - version 5.5.4-k2
Copyright (c) 1999-2004 Intel Corporation.
pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.2.3-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Red Hat/Adaptec aacraid driver (1.1.2-lk2 Jan 26 2005)
3ware Storage Controller device driver for Linux v1.26.02.000.
register_blkdev: cannot get major 8 for sd
mice: PS/2 mouse device common for all mice
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 672.000 MB/sec
raid5: using function: pIII_sse (672.000 MB/sec)
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "0801" or unknown-block(8,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
<0>Rebooting in 1 seconds..
************ REMOTE CONSOLE EXITED *****************
l500r xen #

/var/log/xend.log:

[2005-01-29 10:21:05 xend] DEBUG (XendDomainInfo:720) init_domain> Created
domain=21 name=ttylinux memory=64
[2005-01-29 10:21:05 xend] INFO (console:92) Created console id=12 domain=21
port=9621
[2005-01-29 10:21:06 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=21
uname=phy:hdX_vg/ttylinux_lv
[2005-01-29 10:21:06 xend] DEBUG (blkif:146) Connecting blkif
<BlkifBackendInterface 21 0>
[2005-01-29 10:21:06 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=21
vif=0 mac=aa:00:00:5d:c8:05
[2005-01-29 10:21:06 xend] INFO (XendRoot:91) EVENT> xend.console.create [12,
21, 9621]
[2005-01-29 10:21:06 xend] WARNING (XendDomainInfo:1038) Unknown config field
restart
[2005-01-29 10:21:06 xend] INFO (XendRoot:91) EVENT> xend.domain.create
['ttylinux', '21']
[2005-01-29 10:21:06 xend] INFO (XendRoot:91) EVENT> xend.domain.unpause
['ttylinux', '21']
[2005-01-29 10:21:06 xend] INFO (console:42) Console connected 12 127.0.0.1
1100
[2005-01-29 10:21:06 xend] INFO (XendRoot:91) EVENT> xend.console.connect [12,
'127.0.0.1', 1100]
[2005-01-29 10:21:11 xend] DEBUG (blkif:192) Connecting blkif to event channel
<BlkifBackendInterface 21 0> ports=53:3
[2005-01-29 10:21:16 xend] DEBUG (XendDomain:244) XendDomain>reap> domain died
name=ttylinux id=21
[2005-01-29 10:21:16 xend] DEBUG (XendDomain:247) XendDomain>reap> shutdown
id=21 reason=reboot
[2005-01-29 10:21:16 xend] DEBUG (XendDomain:487) domain_restart_schedule> 21
reboot 0
[2005-01-29 10:21:16 xend] INFO (XendDomain:564) Destroying domain:
name=ttylinux
[2005-01-29 10:21:16 xend] DEBUG (XendDomainInfo:665) Destroying vifs for
domain 21
[2005-01-29 10:21:16 xend] DEBUG (netif:288) Destroying vif domain=21 vif=0
[2005-01-29 10:21:16 xend] DEBUG (XendDomainInfo:674) Destroying vbds for
domain 21
[2005-01-29 10:21:16 xend] DEBUG (blkif:541) Destroying blkif domain=21
[2005-01-29 10:21:16 xend] DEBUG (blkif:397) Destroying vbd domain=21 idx=0
[2005-01-29 10:21:16 xend] DEBUG (XendDomainInfo:634) Closing console, domain
21
[2005-01-29 10:21:16 xend] DEBUG (XendDomainInfo:622) Closing channel to
domain 21
[2005-01-29 10:21:16 xend] INFO (XendRoot:91) EVENT> xend.virq 4
[2005-01-29 10:21:16 xend] DEBUG (blkif:352) Unbinding vbd (type phy) from
hdX_vg/ttylinux_lv
[2005-01-29 10:21:16 xend] INFO (console:56) Console disconnected 12 127.0.0.1
1100
[2005-01-29 10:21:16 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
['ttylinux', '21', 'reboot']
[2005-01-29 10:21:16 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
['ttylinux', '21']
[2005-01-29 10:21:16 xend] INFO (XendRoot:91) EVENT> xend.console.disconnect
[12, '127.0.0.1', 1100]
[2005-01-29 10:21:17 xend] INFO (XendRoot:91) EVENT> xend.domain.died
['ttylinux', '21'

end of /var/log/xend-debug.log ("end" due to no time stamps)

Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDomainDir.py",
line 65, in op_create
deferred = self.xd.domain_create(config)
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomain.py", line 354, in
domain_create
deferred = XendDomainInfo.vm_create(config)
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py", line
192, in vm_create
return vm.construct(config)
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py", line
455, in construct
deferred = self.configure()
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py", line
974, in configure
d = self.create_devices()
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py", line
802, in create_devices
v = dev_handler(self, dev, dev_index)
File "/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py", line
1133, in vm_dev_vbd
defer = ctrl.attachDevice(idx, val, recreate=recreate)
File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 530,
in attachDevice
dev = self.addDevice(idx, config)
File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 515,
in addDevice
dev = BlkDev(idx, self, config )
File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 318,
in __init__
self.configure(config)
File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 335,
in configure
raise VmError('vbd: Device not found: %s' % self.dev)
VmError: vbd: Device not found: sda1

--
karl@packettrap.org


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

>> Interesting - this message means what it says, viz.\ the guest kernel has
>> no idea about the device 0801 (/dev/sda1). It should have received info
>> about this via the control interface during boot -- what does
>> /var/log/xend.log or /var/log/xend-debug.log in domain0 say? (it may be
>> useful to "tail -f" one or both of them during the guest boot). Do you see
>> "xen_blk: Initializing virtual block device driver" on the guest console
>> during boot?
>>
>> cheers,
>>
>> S.
>>
>
>Yes, "xen_blk: Initializing virtual block device driver" appears on the guest
>console but so does "register_blkdev: cannot get major 8 for sd".

Ok - the second message is interesting but probably not the main cause...
an easy thing to try is to boot a XenU kernel rather than a one with
device drivers built in (e.g. your boot messages show that you have
a bunch of 'real' device drivers (CISS, e100, pcnet32, aacraid, 3ware, etc)
which won't work).

However as mentioned the real problem is probably:

File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 335,
>in configure
> raise VmError('vbd: Device not found: %s' % self.dev)
>VmError: vbd: Device not found: sda1

Looks like there is no /dev/sda1 in domain0, which is odd since you
previously mentioned there was.

Mark's potential fix (i.e. use 0801 in place of sda1 in the 'disk=['
line in the config) is probably worth a try.


cheers,

S.




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

On Saturday 29 January 2005 11:19, Steven Hand wrote:

<snip>

>
> Ok - the second message is interesting but probably not the main cause...
> an easy thing to try is to boot a XenU kernel rather than a one with
> device drivers built in (e.g. your boot messages show that you have
> a bunch of 'real' device drivers (CISS, e100, pcnet32, aacraid, 3ware, etc)
> which won't work).
>

<snip>

You're right ... recompiling the XenU kernel without drivers for 'real'
drivers solves the problem. I now have two ttylinux domains up and running.

Regards,

--
karl@packettrap.org


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel