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] Finally got CentOS installed as domU onSLES10SP2dom0, bu

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Finally got CentOS installed as domU onSLES10SP2dom0, but....
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Sat, 02 Aug 2008 19:07:58 -0400
Cc: Nick Couchman <Nick.Couchman@xxxxxxxxx>
Delivery-date: Sat, 02 Aug 2008 16:08:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <489490CF.87A6.0099.1@xxxxxxxxx>
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>
Mailscanner-null-check: 1218323361.44771@20PeQ11TV3iDnnsQZL72bA
References: <4889AA40.87A6.0099.1@xxxxxxxxx> <1217717390.12727.79.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <489490CF.87A6.0099.1@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, 2008-08-02 at 16:52 -0600, Nick Couchman wrote:
> As far as I know it should work on SLES10SP1, yes.  When you
> transferred it to the SLES10SP1 machine, did the path to the disk file
> change and did you make sure to change it the config file?
> 

Yes, and it actually tries to boot, I just get the exact same error as
before:
 # xm create server04;xm console server04
Using config file "./server04".
Started domain server04
Bootdata ok (command line is TERM=xterm )
Linux version 2.6.18-92.el5xen (mockbuild@xxxxxxxxxxxxxxxxxxxx) (gcc
version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Jun 10 19:20:18
EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 00000000c0800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 788480
Kernel command line: TERM=xterm 
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2666.760 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Software IO TLB disabled
Memory: 3072512k/3153920k available (2414k kernel code, 72548k reserved,
1349k data, 176k init)
Calibrating delay using timer specific routine.. 6273.92 BogoMIPS
(lpj=12547845)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 10317A0 could
not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 10317A0 could
not acquire Mutex [2] [20060707]
Initializing CPU#1
migration_cost=5823
Initializing CPU#2
migration_cost=5823
Initializing CPU#3
migration_cost=5823
Brought up 4 CPUs
PCI: Fatal: No PCI config space access function found
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1217715664.034:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 52394A11B61A91
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Console: switching to colour frame buffer device 100x37
input: Xen Virtual Keyboard/Mouse as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Write protecting the kernel read-only data: 461k
USB Universal Host Controller Interface driver v3.0
Registering block device major 202
 xvda: xvda1 xvda2 xvda3
Kernel panic - not syncing: Attempted to kill init!

I've tried changing the root device to all three of the above (on my SP2
server it was xvda3, so I assume it would be the same).

Thanks,
James

James



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