If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get?
The documentation seems to indicate that I should get something that behaves like a telnet to a serial console.
What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that it does exit on the documented escape character ^[).
These virtual systems show as running, and in fact with virt-viewer I can get a VNC console to them.
Dom0 and the guests are Centos 5.5 x64, running on Intel processors with modern virtualization support (turned on in the bios, and it looks like Xen found it from xm dmesg output).
xm console ID [enter] [enter]
On Thu, Jul 15, 2010 at 10:00 PM, David Dyer-Bennet dd-b@dd-b.net wrote:
If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get?
The documentation seems to indicate that I should get something that behaves like a telnet to a serial console.
What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that it does exit on the documented escape character ^[).
These virtual systems show as running, and in fact with virt-viewer I can get a VNC console to them.
Dom0 and the guests are Centos 5.5 x64, running on Intel processors with modern virtualization support (turned on in the bios, and it looks like Xen found it from xm dmesg output).
-- David Dyer-Bennet, dd-b@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 15, 2010 at 3:00 PM, David Dyer-Bennet dd-b@dd-b.net wrote:
If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get?
The documentation seems to indicate that I should get something that behaves like a telnet to a serial console.
What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that it does exit on the documented escape character ^[).
These virtual systems show as running, and in fact with virt-viewer I can get a VNC console to them.
I had a similar problem and had to add the following to the /etc/inittab in the guest systems to get it working:
# Run gettys in standard runlevels co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
Reload the inittab once changed then try attaching via the xm again.
David Dyer-Bennet wrote:
If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get?
The documentation seems to indicate that I should get something that behaves like a telnet to a serial console.
What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that it does exit on the documented escape character ^[).
These virtual systems show as running, and in fact with virt-viewer I can get a VNC console to them.
Dom0 and the guests are Centos 5.5 x64, running on Intel processors with modern virtualization support (turned on in the bios, and it looks like Xen found it from xm dmesg output).
It works for para-virtualized guests (with xen kernel) not for fully-virtualized ones.
Theo
On 07/16/2010 05:06 AM, Theo Band wrote:
It works for para-virtualized guests (with xen kernel) not for fully-virtualized ones.
For fully-virtualized guests, make sure the guest definition contains:
<serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console>
If you add this, you'll need to redefine the guest, then shut it down completely ("poweroff" the guest, not reboot).
# virsh define /etc/libvirt/qemu/guest.xml
Once a serial console is defined in the guest, set up grub. Edit /boot/grub/grub.conf and replace the timeout, splashimage, and hiddenmenu lines with:
timeout=5 serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=5 serial console
Make sure all of the "kernel" lines contain a serial console arg:
kernel /boot/vmlinuz-... ro root=LABEL=/ console=ttyS0,115200
And finally make sure that /etc/inittab starts a getty on the serial console:
s0:2345:respawn:/sbin/agetty -L 115200 ttyS0 vt100
The last three are the same steps you'd take to set up a machine with a physical serial console.
On Fri, Jul 16, 2010 at 08:35:36AM -0700, Gordon Messmer wrote:
On 07/16/2010 05:06 AM, Theo Band wrote:
It works for para-virtualized guests (with xen kernel) not for fully-virtualized ones.
For fully-virtualized guests, make sure the guest definition contains:
<serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console>
If you add this, you'll need to redefine the guest, then shut it down completely ("poweroff" the guest, not reboot).
# virsh define /etc/libvirt/qemu/guest.xml
Once a serial console is defined in the guest, set up grub. Edit /boot/grub/grub.conf and replace the timeout, splashimage, and hiddenmenu lines with:
timeout=5 serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=5 serial console
Make sure all of the "kernel" lines contain a serial console arg:
kernel /boot/vmlinuz-... ro root=LABEL=/ console=ttyS0,115200And finally make sure that /etc/inittab starts a getty on the serial console:
s0:2345:respawn:/sbin/agetty -L 115200 ttyS0 vt100
The last three are the same steps you'd take to set up a machine with a physical serial console.
Also there's an entry about setting up the "xm console" serial console for Xen HVM guests at: http://wiki.xensource.com/xenwiki/XenCommonProblems
-- Pasi
-
David Dyer-Bennet -
Gordon Messmer -
Kwan Lowe -
Pasi Kärkkäinen -
Theo Band -
Yordan Georgiev