On Thursday 29 July 2004 06:05 pm, Steven Hand wrote:
> >Can I assume from the above that it had located the kernel and loaded it?
> What's your [xen]linux command line?
kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht noreboot
module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro
kernel (hd0,4)/boot/vmlinuz-smp root=/dev/sda5 devfs=mount acpi=ht
The Xen command line is exactly what was working two days ago, except that
(hd0,4) was (hd0,0) and /dev/sda5 was /dev/sda1. (This was cut & pasted from
my notes, so the chance of a typo in, say, com1 is reduced -- not eliminated,
of course. At this point I'm looking for 1/l O/0 sillies that could have
crept in, but haven't found anything yet.)
the linux-smp works fine, of course.
> You're not getting any start of
> day messages from dom0 which may mean that the console is set up
> incorrectly. The less likely alternative is that something is going wrong
> (and taking a long time to do so) before the first message that should be
> output from dom0...
> >> First, make sure your xen and vmlinuz-xen images are built from
> >> the same repo version.
> >This was a fresh bk clone on a new install -- what do you mean by "repo"?
> "repo" is short for the bk repository which you're using; if you're using
> a fresh clone you're probably up to date. The above comment was just
> stressing that it's important that the xen and xenlinux images are in
> sync (built from the same version), particularly with unstable.
Good to know.
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
Xen-devel mailing list