|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Xen 3.0.3 serial domU amd64
Hello there!
Thanks for the info.
Does this make Xen itself log to the serial port, or Dom0 log to the
serial port, or both?
We're having some "interesting" behavior with machines going entirely
offline and we're trying to figure out the best way to debug this
remotely.
Any help would be enormously appreciated.
On Nov 27, 2006, at 9:05 AM, Fabrice Coudert wrote:
I finally succeed to setup ttyS0 in domU.
It wasn't an issue on amd64 arch.
It was a mistake about the name of the parameter which tel what
interrupt line
to add in domU. All related post in this liste tels to use
"interrupt". But
this parameter name isn't defined in the script create.py. The good
one is
called "irq".
If someone like to know exactly about the setup I used :
in /boot/grub/menu.lst :
kernel /boot/xen-3.0.3-1-amd64.gz console=vga
module /boot/vmlinuz-2.6.18-1-xen-amd64 root=/dev/sda1 ro
xencons=tty
module /boot/initrd.img-2.6.18-1-xen-amd64
in dom0 :
rmmod 8250_pnp 8250 serial_core
in the config file of the domU :
irq = [ 3, 4]
ioports = ["3f8-3ff", "2f8-2ff"]
in domU :
modprob 8250_pnp 8250 serial_core
in dmseg you should see :
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
--
-- Tom Mornini, CTO
-- Engine Yard, Ruby on Rails Hosting
-- Reliability, Ease of Use, Scalability
-- (866) 518-YARD (9273)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|