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

[Xen-users] multiple disk images, how to?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Molle Bestefich <molle.bestefich@xxxxxxxxx>
  • Date: Mon, 9 Jan 2006 18:11:30 +0100
  • Delivery-date: Mon, 09 Jan 2006 17:18:24 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PyMng/makgf6ZKL3mH4vu1aQ8fZ7TH5fDpfX1pETlpQQJHGTZc5Gv/svl3Q0VXcGMcR2r8A+/agnIQwY2DJk4Ww6/q6BhEh3i0mQjyfz5hIYAUo6DeCmYBTV8LV4UYh5naqOVzyEi4zaufNiWG47+hcMxXqwXMTVIvjPAzB1Ky4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm trying to mount two filesystems in a Xen virtual machine.
I think this should work since 'xm' has an option to attach virtual disks.
Can't get it to work though.

Here's my domU config file:
################
kernel = "/boot/kernel-domU"
memory = 128
name = "dom1"
nics = 1
disk = ['phy:/dev/evms/domubase,xvda1,r']
disk = ['file:/images/linux1.img,xvda2,w']
root = "/dev/xvda1 ro"
################

Using the above, the domU kernel dies like this:
===========
VFS: Cannot open root device "xvda1" or unknown-block(0,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
===========

If I switch the order of the two 'disk' lines, the domU actually
boots, but xvda2 is inacessible and nowhere to be found.

Am I doing something wrong?

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


 


Rackspace

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