Xen users - Apr 2010 - RE: [SEMI-SOLVED] XenSerialConsole help + GRUB2 (Machine locks up on boot)

> Mon, 12 Apr 2010 19:02:12 +0300 <pasik@iki.fi> wrote:
> 
> On Mon, Apr 12, 2010 at 11:55:49AM -0400, Mike Viau wrote:
>     > > >
> >    > > > Can you please paste the full boot messages before
it locks up?
> >    > > >
> >    > > >
> >    > >
> >    > > Unfortunately no, because I am not getting any output
(kernel
> >    messages) to
> >    > > the terminal on the other machine listening. I attached a
photo of
> >    what I
> >    > > see on the screen when console=com1,vga.
> >    > >
> >    >
> >    > So do you see the Xen hypervisor boot messages at least?
> >    >
> >    >
> > 
> >    Nothing in fact.
> > 
> 
> Please paste your grub.conf again.
> 
>
Attached is grub.cfg.

Please notice:

menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64 with a serial console"
{
insmod ext2
set root=(hd2,1)
search --fs-uuid --set 13f83e98-6e2e-48a5-992e-b266d17bbfd3
multiboot /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all sync_console
console_to_ring com1=115200,8n1,0x1000,0 console=com1
module /vmlinuz-2.6.32-4-xen-amd64
root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro console=hvc0 earlyprintk=xen
module /initrd.img-2.6.32-4-xen-amd64
}
 

I have tried using both 0x1000 and 0x1008 with IRQ 21 and 22 and 0
> >    > > > > Motherboard:
> >    > > > >
> >    > >
> >   
[4]http://www.intel.com/products/desktop/motherboards/DP55WG/DP55WG-overview.htm
> >    > > > > [5]http://ark.intel.com/Product.aspx?id=40078
> >    > > > >
> >    > > > > Add-in serial card:
> >    > > > > "Cables Unlimited IOC-2200 2-Port DB9
Serial PCI I/O Card"
> >    > > > >
> >    > >
> >   
[6](http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1431863&CatId=1422)
> >    > > > >
> >    > > >
> >    > > > Does the serial console work with plain baremetal
Linux? (without
> >    Xen).
> >    > > >
> >    > > >
> >    > >
> >    > > No it does not. I started a thread over on the Debian
mailing-list for
> >    > > this though to see if anyone there had any ideas. I have
got no
> >    replies as
> >    > > of yet.
> >    > >
> >    > > Mainly I was asking if one needed to build the
mcs9865-serial.ko
> >    (kernel
> >    > > module) against the kernel source for the running kernel
in order to
> >    log
> >    > > kernel message during boot time or does grub implement a
generic
> >    driver to
> >    > > capture the kernel message?
> >    > >
> >    >
> >    > Uhm.. are you saying this serial-card requires some
non-standard driver?
> >    > Then it probably can''t be used as a serial console.
> >    >
> > 
> >    I was hoping this was not the case. The Linux kernel includes
drivers for
> >    serial port devices does it not? Can anyone confirm if the Moschip
MCS9865
> >    is or is not supported by the Linux kernel?
> > 
> >    Can I try using a generic driver with this card that is already
built into
> >    the Linux kernel?
> 
> Yeah, sure, try it.
What driver (name or module name) do you suggest I start with. Another system
has drivers like:

8250_accent.ko         8250_exar_st16c554.ko  8250_hub6.ko           jsm/       
serial_cs.ko
8250_boca.ko           8250_fourport.ko       8250_mca.ko            max3100.ko 

What about serial_cs.ko?

http://www.google.com/#hl=en&source=hp&q=serial_cs.ko&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=&fp=6909149b0ecd8aa
> I don''t know more about the serial card you have.
> 
> >    > The PCI serial-card needs to show up as a
''real'' serial port, so that
> >    > Xen can output there boot time (before any drivers are loaded
in dom0
> >    kernel).
> >    >
> > 
> >    How does one determine if it is real serial port or not. No
/dev/ttyS[?]
> >    devices are created in the filesystem and there is nothing in the
dmesg
> >    out for these serial ports either. The PCI add-in card was
advertised to
> >    be Linux compatible.
> > 
> 
> Real serial ports are available without any drivers, at boot time before
Linux is loaded.
> Xen needs to log to the serial port before _any_ drivers are loaded, even
before dom0 Linux is loaded.
> 
So the serial line use by grub ''taps'' into real serial ports
only right? So is a driver even needed at all if all the details such as I/O
address, IRQ, speed, etc are provided in the grub configuration?

Many there is a hardware limitation I am unaware or blind to see?
> It''s the same with USB-serial-adapters.. you can''t use
those for serial console
> because they don''t work before the driver is loaded.
> 
> But yeah.. good luck!
> 
> -- Pasi
> 
 		 	   		  
 		 	   		  As the subject says "semi-solved."

Used the patch found here:

http://marc.info/?l=linux-serial&m=124975806304760

8250_pci: add support for MCS9865

So lesson learned Pasi, a kernel driver must be compiled with the running kernel
in order to capture boot messages from it. The driver does not load from the
bootloader or from grub itself.

-M
 		 	   		  
_________________________________________________________________
Live connected. Get Hotmail & Messenger on your phone.
http://go.microsoft.com/?linkid=9724462

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

On Thu, Apr 15, 2010 at 11:42:59AM -0400, Mike Viau
wrote:
>     > Mon, 12 Apr 2010 19:02:12 +0300 <pasik@iki.fi> wrote:
>    >
>    > On Mon, Apr 12, 2010 at 11:55:49AM -0400, Mike Viau wrote:
>    > > > >
>    > > > > > Can you please paste the full boot messages
before it locks up?
>    > > > > >
>    > > > > >
>    > > > >
>    > > > > Unfortunately no, because I am not getting any
output (kernel
>    > > messages) to
>    > > > > the terminal on the other machine listening. I
attached a photo of
>    > > what I
>    > > > > see on the screen when console=com1,vga.
>    > > > >
>    > > >
>    > > > So do you see the Xen hypervisor boot messages at least?
>    > > >
>    > > >
>    > >
>    > > Nothing in fact.
>    > >
>    >
>    > Please paste your grub.conf again.
>    >
>    >
> 
>    Attached is grub.cfg.
> 
>    Please notice:
> 
>    menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64 with a serial
console" {
>    insmod ext2
>    set root=(hd2,1)
>    search --fs-uuid --set 13f83e98-6e2e-48a5-992e-b266d17bbfd3
>    multiboot /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all
sync_console
>    console_to_ring com1=115200,8n1,0x1000,0 console=com1
>    module /vmlinuz-2.6.32-4-xen-amd64
>    root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro console=hvc0
>    earlyprintk=xen
>    module /initrd.img-2.6.32-4-xen-amd64
>    }
> 
> 
>    I have tried using both 0x1000 and 0x1008 with IRQ 21 and 22 and 0
> 
So do you now get Xen hypervisor boot messages? 

>    > > > > > > Motherboard:
>    > > > > > >
>    > > > >
>    > >
>   
[4]http://www.intel.com/products/desktop/motherboards/DP55WG/DP55WG-overview.htm
>    > > > > > >
[5]http://ark.intel.com/Product.aspx?id=40078
>    > > > > > >
>    > > > > > > Add-in serial card:
>    > > > > > > "Cables Unlimited IOC-2200 2-Port DB9
Serial PCI I/O Card"
>    > > > > > >
>    > > > >
>    > >
>   
[6](http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1431863&CatId=1422)
>    > > > > > >
>    > > > > >
>    > > > > > Does the serial console work with plain
baremetal Linux?
>    (without
>    > > Xen).
>    > > > > >
>    > > > > >
>    > > > >
>    > > > > No it does not. I started a thread over on the
Debian mailing-list
>    for
>    > > > > this though to see if anyone there had any ideas. I
have got no
>    > > replies as
>    > > > > of yet.
>    > > > >
>    > > > > Mainly I was asking if one needed to build the
mcs9865-serial.ko
>    > > (kernel
>    > > > > module) against the kernel source for the running
kernel in order
>    to
>    > > log
>    > > > > kernel message during boot time or does grub
implement a generic
>    > > driver to
>    > > > > capture the kernel message?
>    > > > >
>    > > >
>    > > > Uhm.. are you saying this serial-card requires some
non-standard
>    driver?
>    > > > Then it probably can''t be used as a serial
console.
>    > > >
>    > >
>    > > I was hoping this was not the case. The Linux kernel includes
drivers
>    for
>    > > serial port devices does it not? Can anyone confirm if the
Moschip
>    MCS9865
>    > > is or is not supported by the Linux kernel?
>    > >
>    > > Can I try using a generic driver with this card that is
already built
>    into
>    > > the Linux kernel?
>    >
>    > Yeah, sure, try it.
> 
>    What driver (name or module name) do you suggest I start with. Another
>    system has drivers like:
> 
>    8250_accent.ko         8250_exar_st16c554.ko  8250_hub6.ko
>    jsm/                   serial_cs.ko
>    8250_boca.ko           8250_fourport.ko       8250_mca.ko
>    max3100.ko
> 
>    What about serial_cs.ko?
> 
>   
[1]http://www.google.com/#hl=en&source=hp&q=serial_cs.ko&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=&fp=6909149b0ecd8aa
> 
>    > I don''t know more about the serial card you have.
>    >
>    > > > The PCI serial-card needs to show up as a
''real'' serial port, so
>    that
>    > > > Xen can output there boot time (before any drivers are
loaded in
>    dom0
>    > > kernel).
>    > > >
>    > >
>    > > How does one determine if it is real serial port or not. No
>    /dev/ttyS[?]
>    > > devices are created in the filesystem and there is nothing in
the
>    dmesg
>    > > out for these serial ports either. The PCI add-in card was
advertised
>    to
>    > > be Linux compatible.
>    > >
>    >
>    > Real serial ports are available without any drivers, at boot time
before
>    Linux is loaded.
>    > Xen needs to log to the serial port before _any_ drivers are
loaded,
>    even before dom0 Linux is loaded.
>    >
> 
>    So the serial line use by grub ''taps'' into real serial
ports only right?
>    So is a driver even needed at all if all the details such as I/O
address,
>    IRQ, speed, etc are provided in the grub configuration?
> 
>    Many there is a hardware limitation I am unaware or blind to see?
> 
>    > It''s the same with USB-serial-adapters.. you
can''t use those for serial
>    console
>    > because they don''t work before the driver is loaded.
>    >
>    > But yeah.. good luck!
>    >
>    > -- Pasi
>    >
> 
>    As the subject says "semi-solved."
> 
>    Used the patch found here:
> 
>    http://marc.info/?l=linux-serial&m=124975806304760
> 
>    8250_pci: add support for MCS9865
> 
>    So lesson learned Pasi, a kernel driver must be compiled with the
running
>    kernel in order to capture boot messages from it. The driver does not
load
>    from the bootloader or from grub itself.
> 
Ok. All the Serial Consoles I''ve used so far haven''t required
special/additional drivers.

-- Pasi


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

> Thu, 15 Apr 2010 21:01:29 +0300 <pasik@iki.fi> wrote:
> On Thu, Apr 15, 2010 at 11:42:59AM -0400, Mike Viau wrote:
> >     > Mon, 12 Apr 2010 19:02:12 +0300 <pasik@iki.fi> wrote:
> >    >
> >    > On Mon, Apr 12, 2010 at 11:55:49AM -0400, Mike Viau wrote:
> >    > > > >
> >    > > > > > Can you please paste the full boot
messages before it locks up?
> >    > > > > >
> >    > > > > >
> >    > > > >
> >    > > > > Unfortunately no, because I am not getting any
output (kernel
> >    > > messages) to
> >    > > > > the terminal on the other machine listening. I
attached a photo of
> >    > > what I
> >    > > > > see on the screen when console=com1,vga.
> >    > > > >
> >    > > >
> >    > > > So do you see the Xen hypervisor boot messages at
least?
> >    > > >
> >    > > >
> >    > >
> >    > > Nothing in fact.
> >    > >
> >    >
> >    > Please paste your grub.conf again.
> >    >
> >    >
> > 
> >    Attached is grub.cfg.
> > 
> >    Please notice:
> > 
> >    menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64 with a serial
console" {
> >    insmod ext2
> >    set root=(hd2,1)
> >    search --fs-uuid --set 13f83e98-6e2e-48a5-992e-b266d17bbfd3
> >    multiboot /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all
sync_console
> >    console_to_ring com1=115200,8n1,0x1000,0 console=com1
> >    module /vmlinuz-2.6.32-4-xen-amd64
> >    root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro console=hvc0
> >    earlyprintk=xen
> >    module /initrd.img-2.6.32-4-xen-amd64
> >    }
> > 
> > 
> >    I have tried using both 0x1000 and 0x1008 with IRQ 21 and 22 and 0
> > 
> 
> So do you now get Xen hypervisor boot messages? 
Yes! And I have access to the hyper-visor by hitting ctrl+a three
times.
> 
> 
> >    > > > > > > Motherboard:
> >    > > > > > >
> >    > > > >
> >    > >
> >   
[4]http://www.intel.com/products/desktop/motherboards/DP55WG/DP55WG-overview.htm
> >    > > > > > >
[5]http://ark.intel.com/Product.aspx?id=40078
> >    > > > > > >
> >    > > > > > > Add-in serial card:
> >    > > > > > > "Cables Unlimited IOC-2200
2-Port DB9 Serial PCI I/O Card"
> >    > > > > > >
> >    > > > >
> >    > >
> >   
[6](http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1431863&CatId=1422)
> >    > > > > > >
> >    > > > > >
> >    > > > > > Does the serial console work with plain
baremetal Linux?
> >    (without
> >    > > Xen).
> >    > > > > >
> >    > > > > >
> >    > > > >
> >    > > > > No it does not. I started a thread over on the
Debian mailing-list
> >    for
> >    > > > > this though to see if anyone there had any
ideas. I have got no
> >    > > replies as
> >    > > > > of yet.
> >    > > > >
> >    > > > > Mainly I was asking if one needed to build the
mcs9865-serial.ko
> >    > > (kernel
> >    > > > > module) against the kernel source for the
running kernel in order
> >    to
> >    > > log
> >    > > > > kernel message during boot time or does grub
implement a generic
> >    > > driver to
> >    > > > > capture the kernel message?
> >    > > > >
> >    > > >
> >    > > > Uhm.. are you saying this serial-card requires some
non-standard
> >    driver?
> >    > > > Then it probably can''t be used as a serial
console.
> >    > > >
> >    > >
> >    > > I was hoping this was not the case. The Linux kernel
includes drivers
> >    for
> >    > > serial port devices does it not? Can anyone confirm if
the Moschip
> >    MCS9865
> >    > > is or is not supported by the Linux kernel?
> >    > >
> >    > > Can I try using a generic driver with this card that is
already built
> >    into
> >    > > the Linux kernel?
> >    >
> >    > Yeah, sure, try it.
> > 
> >    What driver (name or module name) do you suggest I start with.
Another
> >    system has drivers like:
> > 
> >    8250_accent.ko         8250_exar_st16c554.ko  8250_hub6.ko
> >    jsm/                   serial_cs.ko
> >    8250_boca.ko           8250_fourport.ko       8250_mca.ko
> >    max3100.ko
> > 
> >    What about serial_cs.ko?
> > 
> >   
[1]http://www.google.com/#hl=en&source=hp&q=serial_cs.ko&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=&fp=6909149b0ecd8aa
> > 
> >    > I don''t know more about the serial card you have.
> >    >
> >    > > > The PCI serial-card needs to show up as a
''real'' serial port, so
> >    that
> >    > > > Xen can output there boot time (before any drivers
are loaded in
> >    dom0
> >    > > kernel).
> >    > > >
> >    > >
> >    > > How does one determine if it is real serial port or not.
No
> >    /dev/ttyS[?]
> >    > > devices are created in the filesystem and there is
nothing in the
> >    dmesg
> >    > > out for these serial ports either. The PCI add-in card
was advertised
> >    to
> >    > > be Linux compatible.
> >    > >
> >    >
> >    > Real serial ports are available without any drivers, at boot
time before
> >    Linux is loaded.
> >    > Xen needs to log to the serial port before _any_ drivers are
loaded,
> >    even before dom0 Linux is loaded.
> >    >
> > 
> >    So the serial line use by grub ''taps'' into real
serial ports only right?
> >    So is a driver even needed at all if all the details such as I/O
address,
> >    IRQ, speed, etc are provided in the grub configuration?
> > 
> >    Many there is a hardware limitation I am unaware or blind to see?
> > 
> >    > It''s the same with USB-serial-adapters.. you
can''t use those for serial
> >    console
> >    > because they don''t work before the driver is loaded.
> >    >
> >    > But yeah.. good luck!
> >    >
> >    > -- Pasi
> >    >
> > 
> >    As the subject says "semi-solved."
> > 
> >    Used the patch found here:
> > 
> >    http://marc.info/?l=linux-serial&m=124975806304760
> > 
> >    8250_pci: add support for MCS9865
> > 
> >    So lesson learned Pasi, a kernel driver must be compiled with the
running
> >    kernel in order to capture boot messages from it. The driver does
not load
> >    from the bootloader or from grub itself.
> > 
> 
> Ok. All the Serial Consoles I''ve used so far haven''t
required special/additional drivers.
The required kernel/drivers/serial options must have been compiled in the kernel
.config then. It makes life much simpler when that is the case...

-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

On Thu, Apr 15, 2010 at 03:24:03PM -0400, Mike Viau
wrote:
>    > > >
>    > >
>    > > Attached is grub.cfg.
>    > >
>    > > Please notice:
>    > >
>    > > menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64 with a
serial console"
>    {
>    > > insmod ext2
>    > > set root=(hd2,1)
>    > > search --fs-uuid --set 13f83e98-6e2e-48a5-992e-b266d17bbfd3
>    > > multiboot /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all
>    sync_console
>    > > console_to_ring com1=115200,8n1,0x1000,0 console=com1
>    > > module /vmlinuz-2.6.32-4-xen-amd64
>    > > root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro console=hvc0
>    > > earlyprintk=xen
>    > > module /initrd.img-2.6.32-4-xen-amd64
>    > > }
>    > >
>    > >
>    > > I have tried using both 0x1000 and 0x1008 with IRQ 21 and 22
and 0
>    > >
>    >
>    > So do you now get Xen hypervisor boot messages?
> 
>    Yes! And I have access to the hyper-visor by hitting ctrl+a three times.
>

Good. So what was the problem with Xen boot messages earlier? What did you
change
in grub settings to get it working? 
 

-- Pasi



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

> Thu, 15 Apr 2010 22:37:14 +0300 <pasik@iki.fi> wrote:
> 
> On Thu, Apr 15, 2010 at 03:24:03PM -0400, Mike Viau wrote:
> >    > > >
> >    > >
> >    > > Attached is grub.cfg.
> >    > >
> >    > > Please notice:
> >    > >
> >    > > menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64 with
a serial console"
> >    {
> >    > > insmod ext2
> >    > > set root=(hd2,1)
> >    > > search --fs-uuid --set
13f83e98-6e2e-48a5-992e-b266d17bbfd3
> >    > > multiboot /xen.gz dom0_mem=2048M loglvl=all
guest_loglvl=all
> >    sync_console
> >    > > console_to_ring com1=115200,8n1,0x1000,0 console=com1
> >    > > module /vmlinuz-2.6.32-4-xen-amd64
> >    > > root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro
console=hvc0
> >    > > earlyprintk=xen
> >    > > module /initrd.img-2.6.32-4-xen-amd64
> >    > > }
> >    > >
> >    > >
> >    > > I have tried using both 0x1000 and 0x1008 with IRQ 21 and
22 and 0
> >    > >
> >    >
> >    > So do you now get Xen hypervisor boot messages?
> > 
> >    Yes! And I have access to the hyper-visor by hitting ctrl+a three
times.
> >
> 
> 
> Good. So what was the problem with Xen boot messages earlier? What did you
change
> in grub settings to get it working? 
>  
> 
I was just not able to get any messages through the serial console at first. I
was hoping to just setup my grub config as seen about with the I/O address and
IRQ for my PCI serial port card and start getting the Xen boot messages across
the serial link.

The grub configuration above worked perfectly after I patched my kernel to
support my netmos 9865 serial card [*]. So really no changes were really needed
by I later decided to remove the "sync_console" and
"console_to_ring" options. I also removed "earlyprintk=xen"
from the dom0 kernel line and replaced "console=hvc0" with
"console=hvc0 console=tty0"so that I can get the messages on my screen
and serial console.

[*] I downloaded the current 2.6.33 stable pvops kernel sources and wrote in the
patches. The top of my git log output:

commit 0cc94d21a154f2360daf886e7ec0a25fa6f67452
Author: root <root@xen-host.site>
Date:   Wed Apr 14 19:37:45 2010 -0400

    8250_pci: add support for MCS9865 / SYBA 6x Serial Port Card

commit d4454747e32cb45d27fe1fae024436660fd6774f
Merge: 90d4e45... 19f00f0...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date:   Fri Apr 2 11:29:33 2010 -0700

    Merge remote branch ''stable-2.6.33/master'' into
xen/stable-2.6.33.x

    * stable-2.6.33/master: (156 commits)
      Linux 2.6.33.2
      pata_via: fix VT6410/6415/6330 detection issue
      GFS2: Skip check for mandatory locks when unlocking
      classmate-laptop: use a single MODULE_DEVICE_TABLE to get correct aliases
      x86: Fix sched_clock_cpu for systems with unsynchronized TSC
      b43: Workaround circular locking in hw-tkip key update callback
      Bluetooth: Fix kernel crash on L2CAP stress tests
      Bluetooth: Fix potential bad memory access with sysfs files
      ahci: use BIOS date in broken_suspend list
      quota: Fix warning when a delayed write happens before quota is enabled
      quota: manage reserved space when quota is not active [v2]
      tcp: Fix tcp_make_synack()
      tcp: Fix OOB POLLIN avoidance.
      tcp: Fix tcp_mark_head_lost() with packets == 0
      skbuff: remove unused dma_head & dma_maps fields
      net: Potential null skb->dev dereference
      r8169: offical fix for CVE-2009-4537 (overlength frame DMAs)
      netlink: fix unaligned access in nla_get_be64()
      netfilter: ctnetlink: fix reliable event delivery if message building fail
      netlink: fix NETLINK_RECV_NO_ENOBUFS in netlink_set_err()
      ...


My final question, is it worth submitting that latest patch to xen-devel? Is
there a better channel to use? What steps would I take?


-M
 		 	   		  
_________________________________________________________________
Hotmail & Messenger. Get them on your phone now.
http://go.microsoft.com/?linkid=9724463

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

On Fri, Apr 16, 2010 at 10:36:10AM -0400, Mike Viau
wrote:
>    > Thu, 15 Apr 2010 22:37:14 +0300 <pasik@iki.fi> wrote:
>    >
>    > On Thu, Apr 15, 2010 at 03:24:03PM -0400, Mike Viau wrote:
>    > > > > >
>    > > > >
>    > > > > Attached is grub.cfg.
>    > > > >
>    > > > > Please notice:
>    > > > >
>    > > > > menuentry "Xen 4.0.0 / PVOPS 2.6.32-4-xen-amd64
with a serial
>    console"
>    > > {
>    > > > > insmod ext2
>    > > > > set root=(hd2,1)
>    > > > > search --fs-uuid --set
13f83e98-6e2e-48a5-992e-b266d17bbfd3
>    > > > > multiboot /xen.gz dom0_mem=2048M loglvl=all
guest_loglvl=all
>    > > sync_console
>    > > > > console_to_ring com1=115200,8n1,0x1000,0
console=com1
>    > > > > module /vmlinuz-2.6.32-4-xen-amd64
>    > > > > root=UUID=a8129b5a-f8cc-460e-bda4-93cc547b9f7e ro
console=hvc0
>    > > > > earlyprintk=xen
>    > > > > module /initrd.img-2.6.32-4-xen-amd64
>    > > > > }
>    > > > >
>    > > > >
>    > > > > I have tried using both 0x1000 and 0x1008 with IRQ
21 and 22 and 0
>    > > > >
>    > > >
>    > > > So do you now get Xen hypervisor boot messages?
>    > >
>    > > Yes! And I have access to the hyper-visor by hitting ctrl+a
three
>    times.
>    > >
>    >
>    >
>    > Good. So what was the problem with Xen boot messages earlier? What
did
>    you change
>    > in grub settings to get it working?
>    >
>    >
> 
>    I was just not able to get any messages through the serial console at
>    first. I was hoping to just setup my grub config as seen about with the
>    I/O address and IRQ for my PCI serial port card and start getting the
Xen
>    boot messages across the serial link.
> 
>    The grub configuration above worked perfectly after I patched my kernel
to
>    support my netmos 9865 serial card [*].
Dom0 Linux kernel (or the drivers in it) don''t affect Xen _hypervisor_
serial console
logging at all.. 

You must have had wrong options in grub.conf earlier..
>  So really no changes were really
>    needed by I later decided to remove the "sync_console" and
>    "console_to_ring" options. I also removed
"earlyprintk=xen" from the dom0
>    kernel line and replaced "console=hvc0" with
"console=hvc0 console=tty0"so
>    that I can get the messages on my screen and serial console.
> 
>    [*] I downloaded the current 2.6.33 stable pvops kernel sources and
wrote
>    in the patches. The top of my git log output:
> 
>    commit 0cc94d21a154f2360daf886e7ec0a25fa6f67452
>    Author: root <root@xen-host.site>
>    Date:   Wed Apr 14 19:37:45 2010 -0400
> 
>        8250_pci: add support for MCS9865 / SYBA 6x Serial Port Card
> 
>    commit d4454747e32cb45d27fe1fae024436660fd6774f
>    Merge: 90d4e45... 19f00f0...
>    Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>    Date:   Fri Apr 2 11:29:33 2010 -0700
> 
>        Merge remote branch ''stable-2.6.33/master'' into
xen/stable-2.6.33.x
> 
>        * stable-2.6.33/master: (156 commits)
>          Linux 2.6.33.2
>          pata_via: fix VT6410/6415/6330 detection issue
>          GFS2: Skip check for mandatory locks when unlocking
>          classmate-laptop: use a single MODULE_DEVICE_TABLE to get correct
>    aliases
>          x86: Fix sched_clock_cpu for systems with unsynchronized TSC
>          b43: Workaround circular locking in hw-tkip key update callback
>          Bluetooth: Fix kernel crash on L2CAP stress tests
>          Bluetooth: Fix potential bad memory access with sysfs files
>          ahci: use BIOS date in broken_suspend list
>          quota: Fix warning when a delayed write happens before quota is
>    enabled
>          quota: manage reserved space when quota is not active [v2]
>          tcp: Fix tcp_make_synack()
>          tcp: Fix OOB POLLIN avoidance.
>          tcp: Fix tcp_mark_head_lost() with packets == 0
>          skbuff: remove unused dma_head & dma_maps fields
>          net: Potential null skb->dev dereference
>          r8169: offical fix for CVE-2009-4537 (overlength frame DMAs)
>          netlink: fix unaligned access in nla_get_be64()
>          netfilter: ctnetlink: fix reliable event delivery if message
>    building fail
>          netlink: fix NETLINK_RECV_NO_ENOBUFS in netlink_set_err()
>          ...
> 
>    My final question, is it worth submitting that latest patch to
xen-devel?
>    Is there a better channel to use? What steps would I take?
> 
You should send the patches to lkml I think. If they''re already in the
git tree of Linus,
then they could be easily backported to 2.6.32.x (stable) and then send them for
inclusion
in the next upstream (kernel.org) 2.6.32.x stable release.

Then they''ll get to Jeremy''s tree automatically when Jeremy
pulls from the upstream tree.

-- Pasi


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