Bug 251392 - serial console for paravirt guests not working
Summary: serial console for paravirt guests not working
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen   
(Show other bugs)
Version: 5.1
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Xen Maintainance List
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-08 18:32 UTC by Gurhan Ozen
Modified: 2013-11-04 01:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-10 15:32:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Gurhan Ozen 2007-08-08 18:32:37 UTC
Description of problem:
  After booting guests kernels with "console=tty0 console=xvc0" arguments, the
{virsh,xm} console domId commands seem to go nowhere. 
Version-Release number of selected component (if applicable):
# rpm -q kernel-xen libvirt xen

How reproducible:

Steps to Reproduce:
1. Create a paravirt guest. 
2. Boot it up with console=xvc0 console=tty0 arguments in the kernel line
3. Try to connect to the domain with virsh console or xm console.
Actual results:
Can't get serial port output.

Expected results:
Should have it. 

Additional info:

Comment 1 Daniel Berrange 2007-08-08 18:45:15 UTC
What guest kernel are you running ?

The kernel-xen-2.6.18-36.el5  kernel run as a guest works just fine, without any
 'console' args, or with 'console=xvc0 console=tty0', or with 'console=tty0
console=xvc0'. Supplying any console arg is completely redundant anyway, because
RHEL-5.1 guest kernels 'do the right thing' out of the box .

Comment 2 Daniel Berrange 2007-08-08 18:47:52 UTC
Please also provide the guest config file from /etc/xen  and the

Comment 3 Gurhan Ozen 2007-08-10 15:32:41 UTC
This was an -EUSERERROR it looks like. I had "console=xvc0 console=tty0" as
opposed to "console=tty0 console=xvc0" which caused the problem. Having the
console args in right order fixed it. 

Note You need to log in before you can comment on or make changes to this bug.