Jürgen Keil wrote: > Edward Pilatowicz wrote: >> On Tue, May 20, 2008 at 04:08:21AM -0700, Jürgen Keil wrote: > >>> title Solaris xVM, Console ttyb >>> kernel$ /boot/$ISADIR/xen.gz com2=9600,8n1 console=com2 >>> module$ >>> /platform/i86xpv/kernel/$ISADIR/unix/platform/i86xpv/kernel/$ISADIR/unix -B >>> console=ttyb -kv >>> module$ /platform/i86pc/$ISADIR/boot_archive >> actually, in the scenario above the "-B console=ttyb" option to unix is >> unnecessary. by default, solaris detects what xen is using for it's console >> device and uses the same thing. (you can of course override that with the >> -B or an entry in bootenv.rc, if you want the consoles to go to >> different devices.) > > Hmm, no, I can't omit the -B console=ttyb open when the > hypervisor has it's output redirected to the com2 port; otherwise > I get hypervisor console output on the serial line, and solaris dom0 > console messages on the VGA card (that is, exactly the problem > Alexandra was complaining about).
I think "-B console=hypervisor" on the unix line is the right thing to do if you've set a console for xen. -Ryan > > I have SXCE snv_85 installed, and bfu'ed that multiple times. > In /boot/solaris/bootenv.rc I find this line: > > setprop console 'text' > > > I seems the snv_85 installer has defined that console > property; my old (more or less unmodified) snv_85 UFS > root already has it defined. > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > [email protected] _______________________________________________ xen-discuss mailing list [email protected]
