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

[Xen-users] Trouble booting DomU on Centos 5.2 (x86_64)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Trouble booting DomU on Centos 5.2 (x86_64)
From: "Vijay Subramanian" <vnssports@xxxxxxxxx>
Date: Sun, 23 Nov 2008 19:45:39 -0800
Delivery-date: Sun, 23 Nov 2008 19:46:28 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=nOEXMdpou1DiiUX+WwZ5UfZjkvEILS0TbHhXZ0Jv63c=; b=ovCdXQ2u1RiuOke6NN7JGEEBGtrglGDwpOfLdm9V5veb4xwVuk0Y+KgeG+0yEG7VIA UiA7B7iisTRNDAXWHZlL72h0LD3y4s4ZodSIx1HziaczMveWXNXqZNXEHab5paffVf3Y Ek9VCmd88watfYifT7TCCj/swyEO76TmV3uyA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=LNCTrc/ee1smzl01+7Cdm1axK/I0j3YTwBZEVNztMgXAnZtRSOh4nJslrwWY/Z3cPG YdYLoWl51IIPRSA9COYesdUtc9g+B7uzB4Lay3APIiOSallcTQIn89KQw5Bc7G3S9ymb /xv2xzF2Zt2oC/KhdA0Bt713h6pdOTqKFyqDw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
I am trying to create a DomU that is a clone of the host. I am using
CentOS 5.2 with virtualization enabled . The steps I am following are
as documented in
http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_(Cloning_Host_System)
Everything is x86_64.

The only things I have changed are as follows:
1: I am unmounting /tmp/loop which is the  root file system XenGuest.img
Note that the /boot is not copied into the Guest FS. But I also tried
copying it in but no luck.

The problem:
-- DomU does not boot.

I am getting the following error:
-----------
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@xxxxxxxxxx
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!

----------------
I have tried :
 --Creating a new initrd with xenblk and xennet included and preloaded
and omitting scsi, raid and lvm modules.
Tried variations of this in Dom0

#mkinitrd --omit-scsi-modules --with=xennet --with=xenblk
--preload=xenblk initrd-$(uname -r).img $(uname -r)
(also tried without raid and lvm modules)

I am using the same kernel and initrd from Dom0. i.e. the kernel it
came with 2.6.18-92.el5xen. When I make a new initrd, it is in Dom0.
-- Do I need to copy the /boot into the root file system of DomU or do
makinitrd on DomU ?
-- Do I need a new kernel?

I extracted initrd and xenblk seems to be present.

----------------------------------
My config file for the VM is:
kernel = '/boot/vmlinuz-2.6.18-92.el5xen'
ramdisk = '/boot/initrd-2.6.18-92.el5xen-no-scsi-1.img'
memory = 512
name = 'Xen1'
vif = [ '' ]
dhcp = 'dhcp'
disk = ['tap:aio:/xen/XenGuest1.img,xvda1,w',
'tap:aio:/xen/XenGuest1.swap,xvda2,w']
root = '/dev/xvda1 ro'

extra='xencons=tty'

on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

All my googling seems to indicate that I need a new initrd with xenblk
and no scsi but this does not seem to work.  I also replaced "tap:aio"
with "file" but no joy.
If there is anything I can try, please let me know. Any help/pointers
will be much appreciated. The archives also indicate this is usually
an initrd issue.

Thanks,
vns

--------------------------------
The last few lines of xm log are below:
Full boot message is below that:


[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:1350) XendDomainInfo.construct: None
[2008-11-23 19:38:09 xend 5946] DEBUG (balloon:127) Balloon: 2007164
KiB free; need 2048; done.
[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:1398) XendDomainInfo.initDomain: 160 1.0
[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:1437) _initDomain:shadow_memory=0x0, maxmem=0x200,
memory=0x200.
[2008-11-23 19:38:09 xend 5946] DEBUG (balloon:127) Balloon: 2031568
KiB free; need 524288; done.
[2008-11-23 19:38:09 xend 5946] INFO (image:137) buildDomain os=linux
dom=160 vcpus=1
[2008-11-23 19:38:09 xend 5946] DEBUG (image:202) domid          = 160
[2008-11-23 19:38:09 xend 5946] DEBUG (image:203) memsize        = 512
[2008-11-23 19:38:09 xend 5946] DEBUG (image:204) image          =
/boot/vmlinuz-2.6.18-92.el5xen
[2008-11-23 19:38:09 xend 5946] DEBUG (image:205) store_evtchn   = 1
[2008-11-23 19:38:09 xend 5946] DEBUG (image:206) console_evtchn = 2
[2008-11-23 19:38:09 xend 5946] DEBUG (image:207) cmdline        =
ip=:1.2.3.4::::eth0:dhcp root=/dev/xvda1 ro xencons=tty
[2008-11-23 19:38:09 xend 5946] DEBUG (image:208) ramdisk        =
/boot/initrd-2.6.18-92.el5xen-no-scsi-1.img
[2008-11-23 19:38:09 xend 5946] DEBUG (image:209) vcpus          = 1
[2008-11-23 19:38:09 xend 5946] DEBUG (image:210) features       =
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:110)
DevController: writing {\047mac\047: \04700:16:3e:4b:32:a9\047,
\047handle\047: \0470\047, \047protocol\047: \047x86_64-abi\047,
\047backend-id\047: \0470\047, \047state\047: \0471\047,
\047backend\047: \047/local/domain/0/backend/vif/160/0\047} to
/local/domain/160/device/vif/0.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:112)
DevController: writing {\047domain\047: \047Xen1\047, \047handle\047:
\0470\047, \047script\047: \047/etc/xen/scripts/vif-bridge\047,
\047state\047: \0471\047, \047frontend\047:
\047/local/domain/160/device/vif/0\047, \047mac\047:
\04700:16:3e:4b:32:a9\047, \047online\047: \0471\047,
\047frontend-id\047: \047160\047} to
/local/domain/0/backend/vif/160/0.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:110)
DevController: writing {\047virtual-device\047: \04756321\047,
\047device-type\047: \047disk\047, \047protocol\047:
\047x86_64-abi\047, \047backend-id\047: \0470\047, \047state\047:
\0471\047, \047backend\047:
\047/local/domain/0/backend/tap/160/56321\047} to
/local/domain/160/device/vbd/56321.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:112)
DevController: writing {\047domain\047: \047Xen1\047,
\047frontend\047: \047/local/domain/160/device/vbd/56321\047,
\047format\047: \047raw\047, \047dev\047: \047xvda1\047,
\047state\047: \0471\047, \047params\047:
\047aio:/xen/XenGuest1.img\047, \047mode\047: \047w\047,
\047online\047: \0471\047, \047frontend-id\047: \047160\047,
\047type\047: \047tap\047} to /local/domain/0/backend/tap/160/56321.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:110)
DevController: writing {\047virtual-device\047: \04756322\047,
\047device-type\047: \047disk\047, \047protocol\047:
\047x86_64-abi\047, \047backend-id\047: \0470\047, \047state\047:
\0471\047, \047backend\047:
\047/local/domain/0/backend/tap/160/56322\047} to
/local/domain/160/device/vbd/56322.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:112)
DevController: writing {\047domain\047: \047Xen1\047,
\047frontend\047: \047/local/domain/160/device/vbd/56322\047,
\047format\047: \047raw\047, \047dev\047: \047xvda2\047,
\047state\047: \0471\047, \047params\047:
\047aio:/xen/XenGuest1.swap\047, \047mode\047: \047w\047,
\047online\047: \0471\047, \047frontend-id\047: \047160\047,
\047type\047: \047tap\047} to /local/domain/0/backend/tap/160/56322.
[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:756) Storing VM details: {\047shadow_memory\047:
\0470\047, \047uuid\047: \0472ea38fa9-dc5e-700f-252a-d8da657dd398\047,
\047on_reboot\047: \047restart\047, \047start_time\047:
\0471227497889.28\047, \047on_poweroff\047: \047destroy\047,
\047name\047: \047Xen1\047, \047vcpus\047: \0471\047,
\047vcpu_avail\047: \0471\047, \047memory\047: \047512\047,
\047on_crash\047: \047restart\047, \047image\047: "(linux (kernel
/boot/vmlinuz-2.6.18-92.el5xen) (ramdisk
/boot/initrd-2.6.18-92.el5xen-no-scsi-1.img) (ip
:1.2.3.4::::eth0:dhcp) (root \047/dev/xvda1 ro\047) (args
\047xencons=tty\047))", \047maxmem\047: \047512\047}
[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:791) Storing domain details:
{\047console/ring-ref\047: \0471126964\047, \047console/port\047:
\0472\047, \047name\047: \047Xen1\047, \047console/limit\047:
\0471048576\047, \047vm\047:
\047/vm/2ea38fa9-dc5e-700f-252a-d8da657dd398\047, \047domid\047:
\047160\047, \047cpu/0/availability\047: \047online\047,
\047memory/target\047: \047524288\047, \047store/ring-ref\047:
\0471126965\047, \047store/port\047: \0471\047}
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices vif.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:149) Waiting for 0.
[2008-11-23 19:38:09 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:989) XendDomainInfo.handleShutdownWatch
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/vif/160/0/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/vif/160/0/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:490)
hotplugStatusCallback 1.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices usb.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices vbd.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices irq.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices vkbd.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices vfb.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices pci.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices ioports.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices tap.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:149) Waiting for 56321.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/tap/160/56321/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/tap/160/56321/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:490)
hotplugStatusCallback 1.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:149) Waiting for 56322.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/tap/160/56322/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/tap/160/56322/hotplug-status.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:490)
hotplugStatusCallback 1.
[2008-11-23 19:38:09 xend 5946] DEBUG (DevController:143) Waiting for
devices vtpm.
[2008-11-23 19:38:16 xend.XendDomainInfo 5946] WARNING
(XendDomainInfo:923) Domain has crashed: name=Xen1 id=160.
[2008-11-23 19:38:16 xend.XendDomainInfo 5946] ERROR
(XendDomainInfo:1828) VM Xen1 restarting too fast (7.792794 seconds
since the last restart).  Refusing to restart to avoid loops.
[2008-11-23 19:38:16 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:1560) XendDomainInfo.destroy: domid=160
[2008-11-23 19:38:16 xend.XendDomainInfo 5946] DEBUG
(XendDomainInfo:1568) XendDomainInfo.destroyDomain(160)
[2008-11-23 19:38:17 xend 5946] DEBUG (DevController:476)
hotplugStatusCallback
/local/domain/0/backend/vbd/85/56320/hotplug-status.


------------------

Full boot message:



Bootdata ok (command line is  ip=:1.2.3.4::::eth0:dhcp root=/dev/xvda1
ro xencons=tty)
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 - 0000000020800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 133120
Kernel command line:  ip=:1.2.3.4::::eth0:dhcp root=/dev/xvda1 ro xencons=tty
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2599.998 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Software IO TLB disabled
Memory: 499712k/532480k available (2414k kernel code, 24008k reserved,
1349k data, 176k init)
Calibrating delay using timer specific routine.. 6503.38 BogoMIPS (lpj=13006764)
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: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Physical Processor ID: 1
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 1C7A0 could
not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 1C7A0 could
not acquire Mutex [2] [20060707]
Brought up 1 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: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1227498531.036: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
WARNING: Failed to register Xen virtual console driver as 'tty1'
Event-channel device installed.
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/56321
XENBUS: Device with no driver: device/vbd/56322
XENBUS: Device with no driver: device/vif/0
Write protecting the kernel read-only data: 461k
Registering block device major 220
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has flipping receive path.
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@xxxxxxxxxx
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Trouble booting DomU on Centos 5.2 (x86_64), Vijay Subramanian <=