Matej Zary
2010-Apr-19 14:56 UTC
[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@lists.xensource.com http://lists.xensource.com/xen-users
Matej Zary
2010-Apr-20 09:27 UTC
RE: [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@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Matej Zary Sent: Monday, April 19, 2010 4:57 PM To: xen-users@lists.xensource.com 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Viau
2010-Apr-20 15:20 UTC
RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel
[This email is either empty or too large to be displayed at this time]
Pasi Kärkkäinen
2010-Apr-20 17:36 UTC
Re: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel
On Mon, Apr 19, 2010 at 04:56:48PM +0200, Matej Zary wrote:> 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=com2Try this instead: kernel /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all com1=115200,8n1,0xec00,18 console=com1 You can''t have spaces between the parameters. dom0 kernel line looks OK. If that doesn''t work then try specifying 0 as the IRQ (instead of 18). Also.. hmm.. I wonder if the irq should be in hex or in decimal.. -- Pasi> 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Viau
2010-Apr-21 14:17 UTC
RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel
> Tue, 20 Apr 2010 20:36:56 +0300 <pasik@iki.fi> wrote: > > On Mon, Apr 19, 2010 at 04:56:48PM +0200, Matej Zary wrote: > > 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 > > > Try this instead: > kernel /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all com1=115200,8n1,0xec00,18 console=com1 > > You can''t have spaces between the parameters. > dom0 kernel line looks OK. > > If that doesn''t work then try specifying 0 as the IRQ (instead of 18). > Also.. hmm.. I wonder if the irq should be in hex or in decimal.. >My value was written as above without 0x prefix and appears to function. Also since you are using a non-standard serial IO address please make sure: CONFIG_SERIAL_NONSTANDARD=y http://cateee.net/lkddb/web-lkddb/SERIAL_NONSTANDARD.html> > > 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@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_________________________________________________________________ Hotmail & Messenger are available on your phone. Try now. http://go.microsoft.com/?linkid=9724461 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matej Zary
2010-Apr-22 12:30 UTC
Re: Re: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel
On Tue, 2010-04-20 at 20:36 +0300, Pasi Kärkkäinen wrote:> On Mon, Apr 19, 2010 at 04:56:48PM +0200, Matej Zary wrote: > > 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 > > > Try this instead: > kernel /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all com1=115200,8n1,0xec00,18 console=com1 > > You can't have spaces between the parameters. > dom0 kernel line looks OK. > > If that doesn't work then try specifying 0 as the IRQ (instead of 18). > Also.. hmm.. I wonder if the irq should be in hex or in decimal..Yes, only the spaces were the problem. :) So to summarize (might be another example on http://wiki.xensource.com/xenwiki/XenSerialConsole - at this time there's no cfg example for additional cheap I/O ports PCI card yet): dmesg | grep tty [ 0.004000] console [tty0] enabled [ 1.444943] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.445716] 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 8.433667] 0000:01:0a.0: ttyS1 at I/O 0xec00 (irq = 18) is a 16550A [ 8.433667] 0000:01:0a.0: ttyS2 at I/O 0xe480 (irq = 18) is a 16550A lspci -vvv 01:0a.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01) (prog-if 02) Subsystem: LSI Logic / Symbios Logic 1P2S Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e480 [size=8] Region 2: I/O ports at e400 [size=8] Region 3: I/O ports at e080 [size=8] Region 4: I/O ports at e000 [size=8] Region 5: I/O ports at dc00 [size=16] Kernel driver in use: parport_serial Kernel modules: parport_serial /boot/grub/menu.lst 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 com1=38400,8n1,0xec00,18 console=com1 module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro console=hvc0 earlyprintk=xen nomodeset module /boot/initrd.img-2.6.31.13 Confusing parameters are com1=38400 and console=com1 (because the used port is actually Com2 - ttyS1). It doesn't matter whether is there com1 or com2=38400 and console=com2, it works the same.. So again, many thanks all who tried to help. Regards Matej> > -- Pasi > > > 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@lists.xensource.com http://lists.xensource.com/xen-users
Gerry Reno
2010-Apr-24 21:39 UTC
Re: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel
Matej Zary wrote:> 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@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Matej Zary > Sent: Monday, April 19, 2010 4:57 PM > To: xen-users@lists.xensource.com > 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 > >Marej, I am facing same problem as you. Cannot get pv_ops dom0 kernel to boot on my hardware (AMD) and trying to get console output from MB w/o serial port. I thought in 2.6.31 kernels there was support for USB console? I had seen this somewhere but cannot find it now. Not sure how USB console would be configured to other machine. The only way I can think to do this is with a USB-RS232 dongle. -Gerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Viau
2010-Apr-25 03:49 UTC
RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel
> Sat, 24 Apr 2010 17:39:55 -0400 <greno@verizon.net> wrote: > Matej Zary wrote: > > 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@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Matej Zary > > Sent: Monday, April 19, 2010 4:57 PM > > To: xen-users@lists.xensource.com > > 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 > > > > > Marej, > I am facing same problem as you. Cannot get pv_ops dom0 kernel to > boot on my hardware (AMD) and trying to get console output from MB w/o > serial port. I thought in 2.6.31 kernels there was support for USB > console? I had seen this somewhere but cannot find it now. Not sure > how USB console would be configured to other machine. The only way I > can think to do this is with a USB-RS232 dongle. >I hate to be the be the one to give you the bad news but a USB dongle does not load up in the kernel early enough to capture the Xen hypervisor boot messages. As far as my understanding goes a USB serial dongle can not even be used to log the dom0 kernel messages as the usb drivers need to be loaded in memory before the serial port can be made and this is much latter in the kernel''s boot-up. -M _________________________________________________________________ Videos that have everyone talking! Now also in HD! http://go.microsoft.com/?linkid=9724465 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matej Zary
2010-Apr-25 19:31 UTC
RE: RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel
On Sat, 2010-04-24 at 23:49 -0400, Mike Viau wrote:> > > > > > > > Marej, > > I am facing same problem as you. Cannot get pv_ops dom0 kernel to > > boot on my hardware (AMD) and trying to get console output from MB > w/o > > serial port. I thought in 2.6.31 kernels there was support for USB > > console? I had seen this somewhere but cannot find it now. Not sure > > how USB console would be configured to other machine. The only way > I > > can think to do this is with a USB-RS232 dongle. > > > > I hate to be the be the one to give you the bad news but a USB dongle > does not load up in the kernel early enough to capture the Xen > hypervisor boot messages. As far as my understanding goes a USB serial > dongle can not even be used to log the dom0 kernel messages as the usb > drivers need to be loaded in memory before the serial port can be made > and this is much latter in the kernel's boot-up. > > > -M >As far as I know, the USB-RS232 can be used only on the "other" side (like in my case, i put the USB-RS232 dongle into my laptop - this was the "monitoring" machine). If you don't have any onboard serial port on the Xen machine (true com port, or the server variatons which can be accessed via ethernet etc. - http://wiki.xensource.com/xenwiki/XenSerialConsole ) I'm afraid, you have to acquire some pci card with Com ports (they are quite cheap new and can be sometimes found on computer "junkyards" and bazaars for free or for few cents more than free :) ). Btw. can you spot some of the text messagess on the screen during the boot? And you might try the advice, which solved my case - turning on the ACPI HPET Table in the BIOS settings. Good luck. :) Matej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dustin Henning
2010-Apr-26 12:48 UTC
RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel
From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike Viau Sent: Saturday, April 24, 2010 23:50 To: xen-users@lists.xensource.com Subject: RE: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel> Sat, 24 Apr 2010 17:39:55 -0400 <greno@verizon.net> wrote: > Matej Zary wrote: > > Well, it seems, problem is the IO ports Kouwell PCI card - 01:0a.0Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01).> > > > COM ports work in standard Lenny kernel like charm, but when I removethese 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 usablefor monitoring xen boot process)?> > > > > > Regards > > > > Matej > > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Matej Zary> > Sent: Monday, April 19, 2010 4:57 PM > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31dom0 kernel> > > > Hello all, > > > > I compiled from source Xen 4.0 with the default 2.6.31.13 pv_ops dom0kernel 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 usedusb->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 withthis 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=allcom2=115200, 8n1, 0xec00, 18 console=com2> > module /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro console=hvc0earlyprintk=xen nomodeset> > module /boot/initrd.img-2.6.31.13 > > > > Tried many variations, but still no luck getting the xen boot process onmy serial connected console.> > > > Any hints? > > > > > > Many thanks. > > > > Matej > > > > > Marej, > I am facing same problem as you. Cannot get pv_ops dom0 kernel to > boot on my hardware (AMD) and trying to get console output from MB w/o > serial port. I thought in 2.6.31 kernels there was support for USB > console? I had seen this somewhere but cannot find it now. Not sure > how USB console would be configured to other machine. The only way I > can think to do this is with a USB-RS232 dongle. >I hate to be the be the one to give you the bad news but a USB dongle does not load up in the kernel early enough to capture the Xen hypervisor boot messages. As far as my understanding goes a USB serial dongle can not even be used to log the dom0 kernel messages as the usb drivers need to be loaded in memory before the serial port can be made and this is much latter in the kernel''s boot-up. -M This stands to reason regarding a USB->R232 driver, however, does anyone know if most BIOSes "Legacy USB" support settings apply to RS232 as well, or only to PS/2 and removable media? I ask because if the "Legacy USB" settings apply to USB->RS232 as well, then appropriately configuring them in the BIOS would prevent the hypervisor from knowing the serial port wasn''t a standard physical one (much like booting to DOS or OS/2 on a thumb drive or external USB hard drive doesn''t require those operating systems to have a USB driver at all). Dustin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users