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

RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel


  • To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Matej Zary <zary@xxxxxxxxx>
  • Date: Tue, 20 Apr 2010 11:27:40 +0200
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Tue, 20 Apr 2010 02:29:18 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acrf0Il5TRtnXMz5SiiUoMN+ZaqUvAAmIh+A
  • Thread-topic: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel

Well, it seems, problem is the IO ports Kouwell PCI card - 01:0a.0 
Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 
01).

COM ports work in standard Lenny kernel like charm, but when I remove these 
modules, they caese to work - so it seems they need special driver to work - so 
I assume that's the reason they don't work during xen boot process (or I'm 
wrong? :) ). 

lsmod 

parport_serial         11264  0
parport_pc             31016  1 parport_serial
parport                41776  1 parport_pc


Any ideas? (or advice on proven PCI card with COM ports that are usable for 
monitoring xen boot process)?


Regards

Matej


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Matej Zary
Sent: Monday, April 19, 2010 4:57 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 
kernel

Hello all,

I compiled from source Xen 4.0 with the default 2.6.31.13 pv_ops dom0 kernel on 
barebone Debian Lenny installation. Problem is, this dom0 kernel won't boot. 
First complaining about ioapic, so I tried with noioapci, still no luck (the 
screen blackens during boot and computer reboots). :( So here comes serial 
console. This PC is older shady Asrock nForce 430 board with AMD Athlon X2 1,9 
Ghz CPU => no onboard serial port. Therefore I added PCI card with i/o ports. 

dmesg | grep tty
[    0.004000] console [tty0] enabled
[    0.923873] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    0.924008] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    7.887891] 0000:01:0a.0: ttyS1 at I/O 0xec00 (irq = 18) is a 16550A
[    7.887891] 0000:01:0a.0: ttyS2 at I/O 0xe480 (irq = 18) is a 16550A


According to http://wiki.xensource.com/xenwiki/XenSerialConsole I used usb->com 
cable on my laptop and tried the link test with minicom on both sides - 
chatting worked flawlessly (using /dev/ttyS1 on "server" side). 

Problem is, I'm not able configure boot options for Xen to work with this 
serial port. My grub menu.lst (one from many experiments):

title        Xen 4.0, Linux kernel 2.6.31.13 with serial console
root         (hd0,0)
kernel       /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all 
com2=115200, 8n1, 0xec00, 18 console=com2
module       /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro console=hvc0 
earlyprintk=xen nomodeset
module       /boot/initrd.img-2.6.31.13

Tried many  variations, but still no luck getting the xen boot process on my 
serial connected console.

Any hints?


Many thanks.

Matej





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.