MAGENHEIMER,DAN (HP-FtCollins,ex1)
2004-Mar-25 20:56 UTC
[Xen-devel] xen/dom0 console problems
I''m trying out some of the (not-so-new) console stuff on the unstable tree and having a heckuva time trying to get what I want: 1a) All Xen boot output and all dom0 boot output on the vga screen, or 1a) All Xen boot output and all dom0 boot output on com1, or 1b) All Xen boot output on vga and all dom0 boot output on com1 2) The ability to use the Xen "handlers" (e.g. to press "D" to get to the debugger) 3) pdb communication on com1 (or com2 for case 1a or 1b) I was using "ser_baud=9600nr8 pdb=com1" on the Xen command line and "console=xencons0 console=ttyS0" for xenolinux before and all this worked (and continues to work, except for the warning that ser_baud is deprecated); output going both to vga and com1 and I was able to use ctrl-A-ctrl-A-ctrl-A-D over com1 to get to the debugger. I was going to move pdb to com2 and decided to switch over to the newer (non-deprecated) syntax first, but none of the obvious command line options seems to get me where I was before! I didn''t write down all the different options I tried, but if I was able to get Xen/dom0 boot output, I wasn''t able to get to any Xen handlers; and in many cases I wasn''t able to get dom0 boot output (or in some cases even xen boot output) even though I was using what I expected to be the obvious right way (e.g. console=com1 console=vga or no com= option for Xen, console=xencons0 console=ttyS0 (or tty0) for xenolinux). I haven''t yet gotten to any of the new console stuff for non-dom0 domains... all of this is just with Xen and domain0. Thanks for any suggestions/help! Dan ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
i am using the following (with grub): kernel (nd)/usr/groups/srgboot/revs/xen.gz dom0_ip=DOM0IP dom0_mem=65536 com1=115200,8n1 console=com1 pdb=com1H module (nd)/usr/groups/srgboot/revs/xenolinux.gz ip=DOM0IP:NFSSERVERIP:GW:255.255.240.0:hostname:eth0:off root=nfs nfsroot=/roots/root0 all xen & dom0 boot output appear on com1, i can use either telnet or xencons to retrieve the output. i can also type ''D'' to communicate with xen and force it into pdb. my test machine is in another room so i haven''t checked to see if anything appears on the console. .a On Thu, 25 Mar 2004 15:56:50 -0500 "MAGENHEIMER,DAN (HP-FtCollins,ex1)" <dan.magenheimer@hp.com> wrote:> I''m trying out some of the (not-so-new) console stuff > on the unstable tree and having a heckuva time trying > to get what I want: > > 1a) All Xen boot output and all dom0 boot output on > the vga screen, or > 1a) All Xen boot output and all dom0 boot output on com1, or > 1b) All Xen boot output on vga and all dom0 boot output > on com1 > 2) The ability to use the Xen "handlers" (e.g. to press > "D" to get to the debugger) > 3) pdb communication on com1 (or com2 for case 1a or 1b) > > I was using "ser_baud=9600nr8 pdb=com1" on the Xen > command line and "console=xencons0 console=ttyS0" for > xenolinux before and all this worked (and continues to > work, except for the warning that ser_baud is deprecated); > output going both to vga and com1 and I was able to > use ctrl-A-ctrl-A-ctrl-A-D over com1 to get to the > debugger. I was going to move pdb to com2 and decided > to switch over to the newer (non-deprecated) syntax first, > but none of the obvious > command line options seems to get me where I was before! > I didn''t write down all the different options I tried, > but if I was able to get Xen/dom0 boot output, I wasn''t > able to get to any Xen handlers; and in many cases > I wasn''t able to get dom0 boot output (or in some cases > even xen boot output) even though I was using what > I expected to be the obvious right way (e.g. console=com1 > console=vga or no com= option for Xen, console=xencons0 > console=ttyS0 (or tty0) for xenolinux). > > I haven''t yet gotten to any of the new console stuff for > non-dom0 domains... all of this is just with Xen and > domain0. > > Thanks for any suggestions/help! > Dan > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
MAGENHEIMER,DAN (HP-FtCollins,ex1)
2004-Mar-25 23:06 UTC
RE: [Xen-devel] xen/dom0 console problems
That''s the first thing I tried and IIRC I was getting garbage when I typed the ctrl-a''s. Now, trying again, it seems to work. Perhaps I had some transient serial port problem?!?! Or maybe a typo in the com1= argument? Anyway, all looks good now. Sorry for the interruption :-}> -----Original Message----- > From: Alex Ho [mailto:alex.ho@cl.cam.ac.uk] > Sent: Thursday, March 25, 2004 3:14 PM > To: MAGENHEIMER,DAN (HP-FtCollins,ex1) > Cc: xen-devel@lists.sourceforge.net > Subject: Re: [Xen-devel] xen/dom0 console problems > > > > i am using the following (with grub): > > kernel (nd)/usr/groups/srgboot/revs/xen.gz dom0_ip=DOM0IP > dom0_mem=65536 com1=115200,8n1 console=com1 pdb=com1H > module (nd)/usr/groups/srgboot/revs/xenolinux.gz > ip=DOM0IP:NFSSERVERIP:GW:255.255.240.0:hostname:eth0:off > root=nfs nfsroot=/roots/root0 > > all xen & dom0 boot output appear on com1, i can use either > telnet or xencons to retrieve the output. > i can also type ''D'' to communicate with xen and force it > into pdb. my test machine is in another room > so i haven''t checked to see if anything appears on the console. > > .a > > > On Thu, 25 Mar 2004 15:56:50 -0500 > "MAGENHEIMER,DAN (HP-FtCollins,ex1)" <dan.magenheimer@hp.com> wrote: > > > I''m trying out some of the (not-so-new) console stuff > > on the unstable tree and having a heckuva time trying > > to get what I want: > > > > 1a) All Xen boot output and all dom0 boot output on > > the vga screen, or > > 1a) All Xen boot output and all dom0 boot output on com1, or > > 1b) All Xen boot output on vga and all dom0 boot output > > on com1 > > 2) The ability to use the Xen "handlers" (e.g. to press > > "D" to get to the debugger) > > 3) pdb communication on com1 (or com2 for case 1a or 1b) > > > > I was using "ser_baud=9600nr8 pdb=com1" on the Xen > > command line and "console=xencons0 console=ttyS0" for > > xenolinux before and all this worked (and continues to > > work, except for the warning that ser_baud is deprecated); > > output going both to vga and com1 and I was able to > > use ctrl-A-ctrl-A-ctrl-A-D over com1 to get to the > > debugger. I was going to move pdb to com2 and decided > > to switch over to the newer (non-deprecated) syntax first, > > but none of the obvious > > command line options seems to get me where I was before! > > I didn''t write down all the different options I tried, > > but if I was able to get Xen/dom0 boot output, I wasn''t > > able to get to any Xen handlers; and in many cases > > I wasn''t able to get dom0 boot output (or in some cases > > even xen boot output) even though I was using what > > I expected to be the obvious right way (e.g. console=com1 > > console=vga or no com= option for Xen, console=xencons0 > > console=ttyS0 (or tty0) for xenolinux). > > > > I haven''t yet gotten to any of the new console stuff for > > non-dom0 domains... all of this is just with Xen and > > domain0. > > > > Thanks for any suggestions/help! > > Dan > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President > and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel