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

[Xen-users] x86 vs x86_64 domU : error while loading shared libraries

  • To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Nuno L. Ferreira" <nunolf@xxxxxxxxx>
  • Date: Fri, 26 Mar 2010 14:24:09 +0100
  • Delivery-date: Fri, 26 Mar 2010 06:25:24 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=T1y5DiieVnMMLaWkfE5zqBPYJFloFJ6JQP1E1Sd9mHG/1tkHSjvkUIjHc8dOp9YKLQ ZFJk52I7MvW1CbVdlygrh7LzbK1S6IdvPWgNqmoC/bmXS/Ckd5X4B8If9IoJ40sDDSwt nmS6/BVzkvBjN4/p8upzP41bc8lHqb78zyNDU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Dear *,

I have already setup several LVM based x86 paravirtual domU's on x86_64 dom0's always following the same procedure, for completeness:

1 - build a pristine image with virt-install (VirtualManager); initial configuration and software update is done here, it will be used then to build the production VM's 2 - dump the image into LVM based partitions (kpartx into play here; protocol taken from "Running Xen" book)
3 - after some edition, the VM's boot just fine ...

I was trying to build some paravirtual LVM x86_64 Xen domU's to be run on an x86_64 AMD dom0 server (CentOS 54 x86_64, both the dom0 and domU). Creating the file based image is not a problem, and the VM runs kust fine. The problem is after dumping it to the LV and booting the VM.
I'm getting the following:

[root@xxxlvm <mailto:root@xxxlvm>]# xm create -c xenvm.xen
Using config file "./xenvm.xen".
Started domain xenvm
rtc: IRQ 8 is not free.
rtc: IRQ 8 is not free.
i8042.c: No controller found.
Red Hat nash version starting
Welcome to CentOS release 5.4 (Final)
Press 'I' to enter interactive startup.
Setting clock (utc): Thu Mar 25 22:47:38 CET 2010 [ OK ]
Starting udev: MAKEDEV: mkdir: File exists [ OK ]
Loading default keymap (us): [ OK ]
Setting hostname localhost.localdomain: [ OK ]
No devices found
Setting up Logical Volume Management: [ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
/dev/xvda1: clean, 86854/1310720 files, 605834/2621440 blocks [ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
restorecon: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
Enabling /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Starting background readahead: [ OK ]
Checking for hardware changes [ OK ]
Applying ip6tables firewall rules: ip6tables-restore: error while loading shared libraries: libdl.so.2: cannot open shared object file: Permission denied [FAILED]
... snip ...
/sbin/agetty: error while loading shared libraries: libc.so.6: cannot open shared object file: Permission denied
INIT: Id "co" respawning too fast: disabled for 5 minutes

Can someone give me a hint here?
Why I do not have problems running x86 domU's partition based VM's, while I'm having the above problems for x86_64 domU's?


P.S. I did put this question on the CentOS mailing list (https://www.centos.org/modules/newbb/viewtopic.php?topic_id=25510&forum=45) but still no answers, and since I do not know if this is more from the Xen side, I took the liberty to post it here also.

Xen-users mailing list



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