Re: [Xen-users] upgrade going bad

[James Bulpin <james@xxxxxxxxxxxxx>]

Eric S. Johansson wrote:
> just got your message about which few lines they are and is there any 
> way to capture them so I don't have to write them down in my palsied 
> scrawl and then type them in again?
If you have a second machine and a null modem cable then you can use the 
serial console output (see user manual). If not, then just look to see 
if anything looks "dodgy". Compare to what you can get with xm dmesg on 
2.6.10.
An example of a successful boot on 2.0.5/2.6.10 (I don't have a 2.0.6 
box I can easily use right now) is:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found: 
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Kernel image:  00c00000->00fdefdc
(XEN)  Initrd image:  00000000->00000000
(XEN)  Dom0 alloc.:   01000000->11000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c05106a8
(XEN)  Init. ramdisk: c0511000->c0511000
(XEN)  Phys-Mach map: c0511000->c0551000
(XEN)  Page tables:   c0551000->c0554000
(XEN)  Start info:    c0554000->c0555000
(XEN)  Boot stack:    c0555000->c0556000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Scrubbing Free RAM: ...............................done.

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