When booting XenoLinux directly on my home desktop I get a crash at: DOM0: Guest OS virtual load address is c000000 For setup I followed Bin Ren''s howto. I''ve attached the .config from the xenolinux build. my grub entry: title Xen / XenoLinux 2.4.22 root (hd0,0) kernel /xen.gz dom0_mem=131072 noreboot noht noacpi ifname=dummy ignorebiostables module /xenolinux.gz root=/dev/hda3 ro hdc=ide-scsi (I know some of the qualifiers are redundant, I was getting desperate) df output: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda3 37848096 8105612 27819908 23% / /dev/hda1 101089 24778 71092 26% /boot none 515608 0 515608 0% /dev/shm My machine is a low-end UP P4 with 1GB of RAM. Any pointers would be much appreciated. -Kip
> When booting XenoLinux directly on my home desktop I get > a crash at: > DOM0: Guest OS virtual load address is c000000Add ''console=tty0'' to xenolinux command line. Otherwise console output by default is directed via Xen and thru to the serial line (COM1). If you want output to go both to screen and serial, use ''console=tty0 console=xencons0''. For low-level development you will find it very helpful to attach a serial terminal as it makes it easier to capture crash dumps. -- Keir ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Add ''console=tty0'' to xenolinux command line. Otherwise console output > by default is directed via Xen and thru to the serial line (COM1). > If you want output to go both to screen and serial, use > ''console=tty0 console=xencons0''.Great - thanks. I''m now happily up and running XenoLinux.> > For low-level development you will find it very helpful to attach a > serial terminal as it makes it easier to capture crash dumps. >Agreed. -Kip ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Mon, Jan 12, 2004 at 01:02:28AM -0800, Kip Macy wrote:> > Add ''console=tty0'' to xenolinux command line. Otherwise console output > > by default is directed via Xen and thru to the serial line (COM1). > > If you want output to go both to screen and serial, use > > ''console=tty0 console=xencons0''. > > Great - thanks. I''m now happily up and running XenoLinux.What fixed it, Kip? Steve -- Stephen G. Traugott (KG6HDQ) UNIX/Linux Infrastructure Architect, TerraLuna LLC stevegt@TerraLuna.Org http://www.stevegt.com -- http://Infrastructures.Org ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Here is my home config: title Xen / XenoLinux 2.4.23 root (hd0,0) kernel /xen.gz dom0_mem=262144 noreboot module /xenolinux.gz root=/dev/hda3 ro hdc=ide-scsi console=tty0 console=xencons0 - adding console=tty0 did the trick, without it wouldn''t display to the screen Here is my work config: title Xen / XenoLinux 2.4.22 kernel /xen.gz dom0_mem=131072 ser_baud=9600 ifname=eth1 module /xenolinux.gz root=/dev/sda2 ro console=tty0 console=xencons0 - needed to switch network device to eth1 because eth0 was unsupported I think that you''re having a different problem. The only issue I encountered that I haven''t resolved yet is that the console appears to be read-only. That may be fixed by 1.2, but I need to get the iscsi luns that I''m going to export to the individual domains as VBDs setup on the filer first before I can think about domain management. -Kip On Fri, 16 Jan 2004 stevegt@TerraLuna.Org wrote:> On Mon, Jan 12, 2004 at 01:02:28AM -0800, Kip Macy wrote: > > > Add ''console=tty0'' to xenolinux command line. Otherwise console output > > > by default is directed via Xen and thru to the serial line (COM1). > > > If you want output to go both to screen and serial, use > > > ''console=tty0 console=xencons0''. > > > > Great - thanks. I''m now happily up and running XenoLinux. > > What fixed it, Kip? > > Steve > > -- > Stephen G. Traugott (KG6HDQ) > UNIX/Linux Infrastructure Architect, TerraLuna LLC > stevegt@TerraLuna.Org > http://www.stevegt.com -- http://Infrastructures.Org > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
You''re doing hdc=ide-scsi just to support hyperSCSI, right? Steve On Fri, Jan 16, 2004 at 05:51:05PM -0800, Kip Macy wrote:> Here is my home config: > title Xen / XenoLinux 2.4.23 > root (hd0,0) > kernel /xen.gz dom0_mem=262144 noreboot > module /xenolinux.gz root=/dev/hda3 ro hdc=ide-scsi console=tty0 console=xencons0 > > - adding console=tty0 did the trick, without it wouldn''t display to the > screen > > Here is my work config: > title Xen / XenoLinux 2.4.22 > kernel /xen.gz dom0_mem=131072 ser_baud=9600 ifname=eth1 > module /xenolinux.gz root=/dev/sda2 ro console=tty0 console=xencons0 > > - needed to switch network device to eth1 because eth0 was unsupported > > I think that you''re having a different problem. The only issue I > encountered that I haven''t resolved yet is that the console appears to > be read-only. That may be fixed by 1.2, but I need to get the iscsi luns > that I''m going to export to the individual domains as VBDs setup on the > filer first before I can think about domain management. > > > -Kip > > > > On Fri, 16 Jan 2004 stevegt@TerraLuna.Org wrote: > > > On Mon, Jan 12, 2004 at 01:02:28AM -0800, Kip Macy wrote: > > > > Add ''console=tty0'' to xenolinux command line. Otherwise console output > > > > by default is directed via Xen and thru to the serial line (COM1). > > > > If you want output to go both to screen and serial, use > > > > ''console=tty0 console=xencons0''. > > > > > > Great - thanks. I''m now happily up and running XenoLinux. > > > > What fixed it, Kip? > > > > Steve > > > > -- > > Stephen G. Traugott (KG6HDQ) > > UNIX/Linux Infrastructure Architect, TerraLuna LLC > > stevegt@TerraLuna.Org > > http://www.stevegt.com -- http://Infrastructures.Org > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > >-- Stephen G. Traugott (KG6HDQ) UNIX/Linux Infrastructure Architect, TerraLuna LLC stevegt@TerraLuna.Org http://www.stevegt.com -- http://Infrastructures.Org ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel