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

[Xen-users] RE: Xen-users Digest, Vol 33, Issue 88

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Steve" <taginashi@xxxxxxxxxxx>
  • Date: Tue, 20 Nov 2007 14:02:47 -0800
  • Delivery-date: Tue, 20 Nov 2007 14:03:46 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcgrqH1+sFouoHAZRaeFC5YFC+09ugAF9oCw


A xen server with 9 virtual machines on it lost power this weekend and two
of the 9 virtual servers failed to boot when I got to them.  The more
important one gets as far as the error below.  The other non-functional
virtual machine isn't even getting to the point of any console output but
that one's easy to rebuild so it's only significant in that the error is
different.  All other virtual machines are running with no errors.

Any help would be appreciated.


LILO boot:
Loading Linux2....................
Linux version 2.2.19-compact (herbert@gondolin) (gcc version #1 Wed
Mar 20 19:58:56 EST 2002 
BIOS-provided physical RAM map:
 BIOS-e820: 0009f000 @ 00000000 (usable)
 BIOS-e820: 0fefd000 @ 00100000 (usable)
Detected 3193393 kHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 6330.77 BogoMIPS
Memory: 256884k/262132k available (1648k kernel code, 416k reserved, 3028k
data, 156k init)
Dentry hash table entries: 32768 (order 6, 256k)
Buffer cache hash table entries: 262144 (order 8, 1024k)
Page cache hash table entries: 65536 (order 6, 256k) 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
12K L1 instruction cache
65536K L1 instruction cache
CPU:                   Intel(R) Xeon(TM) CPU 3.20GHz
CPU: Intel                   Intel(R) Xeon(TM) CPU 3.20GHz stepping 04
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@xxxxxxxxxxxxx)
PCI: PCI BIOS revision 2.10 entry at 0xf9ec0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: 00:00 [8086/1237]: Passive release enable (00) 
PIIX3: Enabling Passive Release
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP 
TCP: Hash tables configured (ehash 262144 bhash 65536)
Starting kswapd v 1.5
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device 
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16450
pty: 256 Unix98 ptys configured
RAM disk driver initialized:  16 RAM disks of 4096K size
loop: registered device at major 7 
PIIX3: IDE controller on PCI bus 00 dev 09
PIIX3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio 
hd0: C/H/S=1023/0/63 from BIOS ignored
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: QEMU HARDDISK, 9215MB w/256kB Cache, CHS=18722/16/63 
hdc: ATAPI 4X CD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.11
FDC 0 is a S82078B
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
sim710: No NCR53C710 adapter found.
scsi: <fdomain> Detection failed (no card) 
NCR53c406a: no available ports found
sym53c416.c: Version 1.0.0
Failed initialization of WD-7000 SCSI card!
DC390: 0 adapters found
scsi : 0 hosts.
scsi : detected total.
3c59x.c 18Feb01 Donald Becker and others
pcnet32.c: PCI bios is present, checking for devices...
via-rhine.c:v1.08b-LK1.0.0 12/14/2000  Written by Donald Becker 
Partition check:
 hda:hda: set_multmode: status=0x41 { DriveReady Error }
hda: set_multmode: error=0x04 { DriveStatusError } 
 [PTBL] [1174/255/63] hda1
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 156k freed

Xen-users mailing list



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