On Wed, Mar 4, 2009 at 9:13 AM, Michael DeHaan <mdehaan(a)redhat.com> wrote:
Todd Zullinger wrote:
> Michael DeHaan wrote:
>
>> What does everyone think about automatically adding console=ttyS0 to
>> KVM guests when --no-gfx is used?
>>
>> Currently this flag is meaningless for KVM and only works for Xen,
>> leaving KVM less than useful with no X (i.e. virsh shell does not
>> work).
>>
>
> Does it cause any harm to enable it for KVM even when --no-gfx isn't
> supplied? I added the ks options to start up ttyS0 to my profiles on
> a box where I was working remotely and didn't want/need the graphical
> tools. But, the remote side was at a friend's house where he could
> easily use virt-manager to view and access things graphically.
>
> Can the two co-exist or does setting console=ttyS0 preclude using
> virt-manager? (I don't think we tested with virt-manager since I
> enabled ttyS0 on the guests.)
>
I believe it disables virt-manager usage, need to confirm. (Really
though it would be cool if virt-manager just opened up a text console in
those cases, wouldn't it?)
Personally I'm a console person so I think having no graphics should be
the default, but I hate flip-flopping on options and syntax.
Here is how you please both camps. Add this to the kernel commandline:
console=ttyS0 console=tty0
Note that the ordering is important for some reason and serial needs
to be first. That works on real installs to send output to serial and
a tty. I was surprised to see cobbler doesn't do this by default
actually. Count this as another +1.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com