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] No init found.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] No init found.
From: Paul Tap <paul.tap@xxxxxxxxxxx>
Date: Tue, 20 Dec 2005 17:29:45 +0100
Delivery-date: Tue, 20 Dec 2005 16:24:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E1EojYf-00020C-LZ@host-192-168-0-1-bcn-london>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Armorica - Open Source Software / Consultancy
References: <E1EojYf-00020C-LZ@host-192-168-0-1-bcn-london>
Reply-to: paul.tap@xxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I struggled with this for while too. Got it going now though. Ok, I'm
not on 100% identical hardware (it is HS20 but with AoE SAN), nor on Xen
3 (still running 2), but I think it's more of an initrd issue than
anything else. I found the Fedora and CentOS Xen manulas to be very
helpful. Besides that, I wrote a howto for myself
(http://www.armorica.net/index.php?id=57) that may be helpful. It deals
with initrd (and what to leave out).

Maybe it helps.

Regards,

Paul Tap

-- 
Armorica - Open Source Software / Consultancy

Berkelstraat 91
3522 EL Utrecht

T +31 30 289 4890
M +31 653 269 629
F +31 30 289 6150
E paul.tap@xxxxxxxxxxx
W www.armorica.nl

> Message: 2
> Date: Tue, 20 Dec 2005 22:12:52 +0800
> From: Colin Coe <CCoe@xxxxxxxxxxxxxxx>
> Subject: RE: [Xen-users] No init found.
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Message-ID:
>       <1FB25FFEAA977540B5BC43D9F5F607F7081D2307@xxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;     charset="iso-8859-1"
> 
> 
> I've had some progress with this.  I've found that an initrd is indeed
> required but I've been unable to build one that works on the Blade servers
> in domU.  Can someone whos got this working on an IBM Blade advise how this
> is done?  I keep getting 'unknown symbol errors' when loading the modules in
> the initrd.
> 
> Thanks
> 
> CC
> 
> -----Original Message-----
> From: Colin Coe [mailto:CCoe@xxxxxxxxxxxxxxx]
> Sent: Tuesday, 20 December 2005 2:01 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] No init found.
> 
> 
> 
> Hi all
> 
> I have dom0 happy now but am having real issues with domU.
> 
> Hardware
> - IBM HS20 Blade (884325M)
> - 2G RAM
> - 36G sda (hardware RAID1)
> 
> Software
> - RHEL ES4 update 2
> - Xen 3.0.0 pre-built binaries for x86_64 (untar's to
> 'xen-unsatble-install')
> 
> Config
> kernel = "/boot/vmlinuz-2.6.xenU"
> memory = 256
> name = "vm1"
> disk = [ 'phy:rootvg/xen_vm1,sda1,w' ]
> hostname = "vm1"
> root = "/dev/sda1 ro"
> 
> domU fstab
> /dev/sda1          /                    ext3         defaults
> 1 1
> none                     /dev/pts             devpts       gid=5,mode=620
> 0 0
> none                     /proc                proc         defaults
> 0 0
> none                     /dev/shm             tmpfs        defaults
> 0 0
> 
> dom0's / (/dev/rootvg/root) has been copied to /dev/rootvg/xen_vm1 and the
> relevent mods made.
> 
> Do I need to roll my own initrd?  How do I do this for Xen?  I've read about
> Debian and debootstrap, does this apply to me?  Any ideas?
> 
> Thanks
> 
> 
> Colin Coe
> Store Systems Team Leader
> Bunnings Pty Ltd
> 
> Phone: +61 8 9365 1555 (ext 737)
> Mobile: 0407 089 115
> 
> ************************************************************************
> Bunnings Legal Disclaimer:
> 
> 1)     This email is confidential and may contain legally privileged
> information.  If you are not the intended recipient, you must not
> disclose or use the information contained in it.  If you have received
> this email in error, please notify us immediately by return email and
> delete the document.
> 
> 2)     All emails sent to and sent from Bunnings Group Limited.
> are scanned for content.  Any material deemed to contain inappropriate
> subject matter will be reported to the email administrator of all
> parties concerned.
> ************************************************************************
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> ************************************************************************
> Bunnings Legal Disclaimer:
> 
> 1)     This email is confidential and may contain legally privileged
> information.  If you are not the intended recipient, you must not
> disclose or use the information contained in it.  If you have received
> this email in error, please notify us immediately by return email and
> delete the document.
> 
> 2)     All emails sent to and sent from Bunnings Group Limited.
> are scanned for content.  Any material deemed to contain inappropriate
> subject matter will be reported to the email administrator of all
> parties concerned.
> ************************************************************************




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

<Prev in Thread] Current Thread [Next in Thread>