Oops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Gerd Hoffmann (kraxel at suse.de) wrote:
> Chris Wright wrote:
> > 
> > This should not be needed, the console should be xcv0, completely decoupled
> > from serial.
> 
> You've made the whole thing even more complicated with the last commit.
> Enabling VT is possible now.  Good.  No way around that.  The kernel
> hangs now though.  Fix is attached:  better don't try to setup the vga
> console for xen guests which don't have the hardware.

I'm not really sure what, the last commit I did was lhype?

> Next problem:  The default for xencons (tty) conflicts with the virtual
> consoles.  I'm tempted to drop the complete xencons=foobar stuff into
> the waste basket and leave in xencons=xvc only.  And maybe xencons=off.
>  xencons=tty conflicts with the VT subsystem.  xencons=ttyS conflicts
> with the serial driver.  Disabling the offending drivers is completely
> out of question for a kernel which is supposed to work both native and
> paravirtualized.

Yes, all of tty ttyS xencons goes away.  Here the default is xvc.

> One more issue:  What should be the default console?  Right now it is
> the vt console (using the dummy device).  Not very good.  vgacon doesn't
> work.  fbcon doesn't work either (yet).  So you'll end up with a
> non-functional console by default.  Bummer.

default console should be xvc in the guest.

thanks,
-chris


[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux