WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] XEN boot messages not visible on console

To: Krist van Besien <krist.vanbesien@xxxxxxxxx>
Subject: Re: [Xen-users] XEN boot messages not visible on console
From: Richie <listmail@xxxxxxxxxxxx>
Date: Sat, 22 May 2010 10:20:13 -0400
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 22 May 2010 07:21:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimDvO6G1lfjyAAj211WHzf0gRsn9iTcfz91jk4g@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimDvO6G1lfjyAAj211WHzf0gRsn9iTcfz91jk4g@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (X11/20090817)
I think it is that com1 defaults to the standard irq/address but you can redefine it

menuentry "Xen 4.0 / Ubuntu 10.4 kernel 2.6.32.10-xen7 pvops IOMMU SERIAL" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 321dedfa-be48-4b4d-bff0-0e5ecce240fd
multiboot /boot/xen-4.0.gz dummy=dummy iommu=1 dom0_mem=1024M com1=19200,8n1,0xe480,17 console=com1 module /boot/vmlinuz-2.6.32.10-xen7 dummy=dummy root=/dev/sdc2 ro xen-pciback.permissive xen-pciback.hide=(07:01.0)(01:00.0)(00:1a.0)(00:1d.0) console=hvc0
module /boot/initrd.img-2.6.32.10-xen7
}

Krist van Besien wrote:
Hello,

I'm not seeing any XEN boot messages at all. Xen boots OK, and
afterwards I do get the DOM0 boot messages. I can also see the
messages using xm dmesg.
root@thunersee:~/work/xen/src/xen-4.0.0# xm dmesg
(XEN) Bad console= option 'com3'
 __  __            _  _    ___   ___
 \ \/ /___ _ __   | || |  / _ \ / _ \
  \  // _ \ '_ \  | || |_| | | | | | |
  /  \  __/ | | | |__   _| |_| | |_| |
 /_/\_\___|_| |_|    |_|(_)___(_)___/

(XEN) Xen version 4.0.0 (krist@xxxxxxxxx) (gcc version 4.4.3 (Ubuntu
4.4.3-4ubuntu5) ) Sat May 22 13:07:02 CEST 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: dom0_mem=1024M console=com3 com3=115200,8n1

As you see xen complains about hte console. However, according to the
info I found here:
http://wiki.xensource.com/xenwiki/XenHypervisorBootOptions
Or should I interpret "Xen supports up to two 16550-compatible serial
ports" as meaning "XEN only supports com1 and com2"?

Com3 is the port that I can see using the SOL funtion of the IPMI
build in to the server.

Krist



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

<Prev in Thread] Current Thread [Next in Thread>