I had what was checked in a few days ago working quite well, so I decided to wipe the machine and try out two partitions (swap + /) and domains 1+ on loopback. Now, after xen finished booting, the machine reboots. The only think that''s really different is my swap partition is on /dev/sda1 and my root partition is on /dev/sda5. But the grub menu looks ok as far as I can tell... I''m running on a dual P3. bk | head, /etc/fstab, /boot/grub/menu.lst, and ls /boot provided below. Anything look obvious? Thanks, Barry ---------------------------------------- bk | head [rountree@dom0 xeno-unstable.bk]$ bk changes | head ChangeSet@1.1143, 2004-07-28 16:35:54+01:00, smh22@tempest.cl.cam.ac.uk don''t use common slab/page allocators for ia64 (it uses 2.6 stuff in arch directory) ---------------------------------------- cat /etc/fstab /dev/sda5 / xfs defaults 1 1 none /dev/pts devpts mode=0620 0 0 #/dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0 #none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 none /proc proc defaults 0 0 /dev/sda1 swap swap defaults 0 0 ---------------------------------------- cat /boot/grub/menu.lst timeout 10 color black/cyan yellow/cyan default 0 title Xen kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro title linux-smp kernel (hd0,4)/boot/vmlinuz-smp root=/dev/sda5 devfs=mount acpi=ht resume=/dev/sda1 max_loop=128 initrd (hd0,4)/boot/initrd-smp.img ---------------------------------------- ls -l /boot boot.0800 config config-2.4.26-xen0 config-2.4.26-xenU config-2.6.3-7mdk config-2.6.3-7mdksmp diag1.img diag2.img grub initrd-2.6.3-7mdk.img initrd-2.6.3-7mdksmp.img initrd.img initrd-smp.img kernel.h kernel.h-2.6.3-7mdk kernel.h-2.6.3-7mdksmp map message message-graphic message-text System.map System.map-2.4.26-xen0 System.map-2.4.26-xenU System.map-2.6.3-7mdk System.map-2.6.3-7mdksmp us.klt vmlinux-syms-2.4.26-xen0 vmlinux-syms-2.4.26-xenU vmlinuz vmlinuz-2.4.26-xen0 vmlinuz-2.4.26-xenU vmlinuz-2.6.3-7mdk vmlinuz-2.6.3-7mdksmp vmlinuz-smp xen.gz xen-syms ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I had what was checked in a few days ago working quite well, so I decided to > wipe the machine and try out two partitions (swap + /) and domains 1+ on > loopback. > > Now, after xen finished booting, the machine reboots. > > The only think that''s really different is my swap partition is on /dev/sda1 > and my root partition is on /dev/sda5. But the grub menu looks ok as far as > I can tell...I''d be very surprised if this was a Xen issue rather than a configuration problem. I suspect Xen boots fine, starts dom0, but then dom0 bails, probably because it can''t mount root or such like. If you boot xen with the ''noreboot'' cmdline option you''ll get a chance to read why dom0 is exiting. First, make sure your xen and vmlinuz-xen images are built from the same repo version. Best, Ian ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thursday 29 July 2004 05:26 pm, Ian Pratt wrote:> > Now, after xen finished booting, the machine reboots.> I''d be very surprised if this was a Xen issue rather than a > configuration problem.I agree -- but I''d run out of places to look. Is booting to an xfs partition allowed? Hmmm... based on what xen is reporting, it looks like it loaded the kernel ok...> > I suspect Xen boots fine, starts dom0, but then dom0 bails, > probably because it can''t mount root or such like. > > If you boot xen with the ''noreboot'' cmdline option you''ll get a > chance to read why dom0 is exiting.[Transcribed] (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=1.3,VIRT_BASE=0xC0000000'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 02800000->02b0b8fc (XEN) Initrd image: 00000000->00000000 (XEN) Dom0 alloc.: 02c00000->0ac00000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c0458988 (XEN) Init. ramdisk: c0459000->c0459000 (XEN) Phys-Mach map: c0459000->c0479000 (XEN) Page tables: c0479000->c047c000 (XEN) Start Info: c047c000->c047d000 (XEN) Boot stack: c047d000->c047e000 (XEN) TOTAL: c00000000->c0800000 (XEN) ENTRY ADDRESS: c0100000 (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to swith input to Xen). [long pause.] (XEN) Domain 0 shutdown: rebooting machine! (XEN) Reboot disabled on cmdline: require manual reset Can I assume from the above that it had located the kernel and loaded it?> > 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"?> > Best, > IanThanks Barry> > > ------------------------------------------------------- > 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 > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
>[Transcribed] >(XEN) *** LOADING DOMAIN 0 *** >(XEN) Xen-ELF header found: >''GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=1.3,VIRT_BASE=0xC0000000'' >(XEN) PHYSICAL MEMORY ARRANGEMENT: >(XEN) Kernel image: 02800000->02b0b8fc >(XEN) Initrd image: 00000000->00000000 >(XEN) Dom0 alloc.: 02c00000->0ac00000 >(XEN) VIRTUAL MEMORY ARRANGEMENT: >(XEN) Loaded kernel: c0100000->c0458988 >(XEN) Init. ramdisk: c0459000->c0459000 >(XEN) Phys-Mach map: c0459000->c0479000 >(XEN) Page tables: c0479000->c047c000 >(XEN) Start Info: c047c000->c047d000 >(XEN) Boot stack: c047d000->c047e000 >(XEN) TOTAL: c00000000->c0800000 >(XEN) ENTRY ADDRESS: c0100000 >(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to swith input to >Xen). >[long pause.] >(XEN) Domain 0 shutdown: rebooting machine! >(XEN) Reboot disabled on cmdline: require manual reset > >Can I assume from the above that it had located the kernel and loaded it?What''s your [xen]linux command line? 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. cheers, S.
> On Thursday 29 July 2004 05:26 pm, Ian Pratt wrote: > > > > Now, after xen finished booting, the machine reboots. > > > I''d be very surprised if this was a Xen issue rather than a > > configuration problem. > > I agree -- but I''d run out of places to look.You''re using a serial console, right? Add "console=ttyS0" to the linux command line: title Xen kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200,8n1 noht module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro console=ttyS0> Is booting to an xfs partition allowed?Sure, providing XFS is configured in the kernel.> Hmmm... based on what xen is > reporting, it looks like it loaded the kernel ok...Yep, it''s loading fine, but then dom0 is exits in an orderly fashion. Ian ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
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?I''m using title Xen 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 and title linux-smp kernel (hd0,4)/boot/vmlinuz-smp root=/dev/sda5 devfs=mount acpi=ht resume=/dev/sda1 max_loop=128 initrd (hd0,4)/boot/initrd-smp.img 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.> cheers, > > S.Thanks, Barry ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thursday 29 July 2004 06:09 pm, Ian Pratt wrote:> > On Thursday 29 July 2004 05:26 pm, Ian Pratt wrote: > > > > Now, after xen finished booting, the machine reboots. > > > > > > I''d be very surprised if this was a Xen issue rather than a > > > configuration problem. > > > > I agree -- but I''d run out of places to look. > > You''re using a serial console, right?Well, I will be now... ;-P> Add "console=ttyS0" to the > linux command line:Ok, let me get this set up and I''ll post what happens. Barry ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thursday 29 July 2004 06:30 pm, Barry Rountree wrote:> > Add "console=ttyS0" to the > > linux command line: > > Ok, let me get this set up and I''ll post what happens.Here''s the output from the serial console: Restarting system. [rebooting from linux-smp into xen] kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht noreboot [Multiboot-elf, <0x100000:0x40c4c:0x344f4>, shtab=0x176078, entry=0x100000] module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro console=ttyS0 [Multiboot-module @ 0x177000, 0x30b8fc bytes] That''s it. To sum up, things that have changed from the last time this worked: (Slightly) newer code. Using XFS instead of ext2. Only two partitions (1GB swap and 15GB) instead of several smaller ones. I was in a bit more of a hurry... Let me know if there''s anything else useful I can try. Otherwise, I''ll wipe the drive and start over in the morning. Barry ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
My machine rebooted under similar circumstances, although I might have got something from dom0, but I put noacpi in the xen boot line in grub and it fixed it right up. james From: Barry Rountree Sent: Fri 30/07/2004 10:16 AM To: xen-devel@lists.sourceforge.net Subject: Re: [Xen-devel] dom0 won''t boot On Thursday 29 July 2004 06:30 pm, Barry Rountree wrote:> > Add "console=ttyS0" to the > > linux command line: > > Ok, let me get this set up and I''ll post what happens.Here''s the output from the serial console: Restarting system. [rebooting from linux-smp into xen] kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht noreboot [Multiboot-elf, <0x100000:0x40c4c:0x344f4>, shtab=0x176078, entry=0x100000] module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro console=ttyS0 [Multiboot-module @ 0x177000, 0x30b8fc bytes] That''s it. To sum up, things that have changed from the last time this worked: (Slightly) newer code. Using XFS instead of ext2. Only two partitions (1GB swap and 15GB) instead of several smaller ones. I was in a bit more of a hurry... Let me know if there''s anything else useful I can try. Otherwise, I''ll wipe the drive and start over in the morning. Barry ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> On Thursday 29 July 2004 06:30 pm, Barry Rountree wrote: > > > > Add "console=ttyS0" to the > > > linux command line: > > > > Ok, let me get this set up and I''ll post what happens. > > Here''s the output from the serial console: > > Restarting system. > [rebooting from linux-smp into xen] > kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht noreboot > [Multiboot-elf, <0x100000:0x40c4c:0x344f4>, shtab=0x176078, entry=0x100000] > module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro console=ttyS0 > [Multiboot-module @ 0x177000, 0x30b8fc bytes]All of that output is from grub, you''re not seeing anything from Xen. Try "com1=115200,8n1" and make sure that you''ve got the baudrate at the other end set correctly (I thought grub defaulted to 9600?) Ian> That''s it. > > To sum up, things that have changed from the last time this worked: > > (Slightly) newer code. > Using XFS instead of ext2. > Only two partitions (1GB swap and 15GB) instead of several smaller ones. > I was in a bit more of a hurry... > > Let me know if there''s anything else useful I can try. Otherwise, I''ll wipe > the drive and start over in the morning. > > Barry > > > > > ------------------------------------------------------- > 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 > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thursday 29 July 2004 08:29 pm, Ian Pratt wrote:> All of that output is from grub, you''re not seeing anything from > Xen. > > Try "com1=115200,8n1" and make sure that you''ve got the baudrate > at the other end set correctly (I thought grub defaulted to 9600?)It''s set correctly -- I had never done this before, so there was a bit of a learning curve. I practiced on the smp kernel that I usually boot into and when I was able to capture everything in minicom there I switched over to xen. If I had gotten no output at all, it would have been suspicious. However, I did get output, no characters were garbled, no sentences cut in half, etc. For whatever it''s worth, here''s the entry in grub: title Xen-Serial serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 terminal serial 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 console=ttyS0 But still, a good point. Barry> > Ian------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thursday 29 July 2004 08:25 pm, James Harper wrote:> My machine rebooted under similar circumstances, although I might have got > something from dom0, but I put noacpi in the xen boot line in grub and it > fixed it right up. >Hmmm.... just tried that, didn''t work. Good idea though. Barry> james------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> On Thursday 29 July 2004 08:29 pm, Ian Pratt wrote: > > > All of that output is from grub, you''re not seeing anything from > > Xen. > > > > Try "com1=115200,8n1" and make sure that you''ve got the baudrate > > at the other end set correctly (I thought grub defaulted to 9600?) > > It''s set correctly -- I had never done this before, so there was a bit of a > learning curve. I practiced on the smp kernel that I usually boot into and > when I was able to capture everything in minicom there I switched over to > xen. If I had gotten no output at all, it would have been suspicious. > However, I did get output, no characters were garbled, no sentences cut in > half, etc. > > For whatever it''s worth, here''s the entry in grub: > > title Xen-Serial > serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 > terminal serial > 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 console=ttyS0You''re setting the serial baud rate to 9600 in grub, then 115200 in Xen? That doesn''t sound sane. The baudrate mismatch is so gross that you probably wouldn''t even see garbage. Try com1=9600,8n1 (I can''t remember whether the '',8n1'' is mandatory but let''s assume it is...) Ian ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > All of that output is from grub, you''re not seeing anything from > > Xen. > > > > Try "com1=115200,8n1" and make sure that you''ve got the baudrate > > at the other end set correctly (I thought grub defaulted to 9600?) > > It''s set correctly -- I had never done this before, so there was a bitof> a > learning curve. I practiced on the smp kernel that I usually bootinto> and > when I was able to capture everything in minicom there I switched overto> xen. If I had gotten no output at all, it would have been suspicious. > However, I did get output, no characters were garbled, no sentencescut in> half, etc. > > For whatever it''s worth, here''s the entry in grub: > > title Xen-Serial > serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 > terminal serial > 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 roconsole=ttyS0 Your grub and xen serial speed settings are different. Try setting them to the same value which also has to match your terminal program setting. Presumably you want ''com1=9600,8n1'' on the kernel line rolf> But still, a good point. > > Barry > > > > Ian > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changeson> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open SourceTechnology> Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Your Grub config shows you''re passing: com1=115200 to Xen. I suspect Xen would reject that format and not produce any serial output. You really do need the full: com1=115200,8n1 or it might not work. Unfortunately, having the serial console working in Linux is not quite enough because Xen has control of the serial port and XenLinux has to go through Xen. You should at least be seeing something of Xen output on the serial line even if Linux isn''t booting. Thanks for your patience, you should be up and running again soon. HTH, Mark ------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Friday 30 July 2004 03:27 am, Ian Pratt wrote:> > On Thursday 29 July 2004 08:29 pm, Ian Pratt wrote: > > > All of that output is from grub, you''re not seeing anything from > > > Xen. > > > > > > Try "com1=115200,8n1" and make sure that you''ve got the baudrate > > > at the other end set correctly (I thought grub defaulted to 9600?) > > > > It''s set correctly --[snip an embarrassing moment of hubris]> > title Xen-Serial > > serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 > > terminal serial > > 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 console=ttyS0 > > You''re setting the serial baud rate to 9600 in grub, then 115200 > in Xen? That doesn''t sound sane. The baudrate mismatch is so > gross that you probably wouldn''t even see garbage. >DOH! Yup, absolutely right.> Try com1=9600,8n1 (I ca''t remember whether the '',8n1'' is > mandatory but let''s assume it is...)The interesting bit: FAT: bogus logical sector size 0 UMSDOS: msdos_read_super failed, mount aborted. FAT: bogus logical sector size 0 FAT: bogus logical sector size 0 Kernel panic: VFS: Unable to mount root fs on 08:05 <0>Rebooting in 1 seconds..(XEN) Domain 0 shutdown: rebooting machine! (XEN) Reboot disabled on cmdline: require manual reset The damning line from the kernel .config file: # CONFIG_XFS_FS is not set while /etc/fstab wants /dev/sda5 / xfs defaults 1 1 Oooops....<blush> Thanks to everybody who helped; I''ll see if I can come up with a more interesting problem next time... Barry> Ian------------------------------------------------------- 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 Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel