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/
Home Products Support Community News


[Xen-users] Unable to start domain based on ubuntu filesystem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Unable to start domain based on ubuntu filesystem
From: Ricardo <djrico@xxxxxxx>
Date: Sun, 06 Nov 2005 11:03:54 -0500
Delivery-date: Sun, 06 Nov 2005 16:04:28 +0000
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050618)
I recently installed Ubuntu 4.05 Hoary on a separate partition (JFS
filesystem), installed Xen on it, and then dd'ed the filesystem into a
file (ubuntu.img).  I also created the requisite config file, which I
have included in this e-mail.  When I try to run it using xm create -c
ubuntu, I get the following error:

IP-Config: Incomplete network configuration information.
jfs_mount: Mount Failure: File System Dirty.           
Mount JFS Failure: -22                     
Kernel panic - not syncing: VFS: Unable to mount root fs on

************ REMOTE CONSOLE EXITED *****************

Does anyone have a clue as to what's going on here and how I can fix it?
# Configuration file for Ubuntu 4.05 Hoary
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.11-xenU"

# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"

# The domain build function. Default is 'linux'.

# Initial memory allocation (in megabytes) for the new domain.
memory = 96

# A name for your domain. All domains must have different names.
name = "ubuntu"

# Which CPU to start domain on? 
cpu = -1   # leave to Xen to pick

# Define network interfaces.

# Number of network interfaces. Default is 1.

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
vif = [ 'mac=00:09:6B:E0:57:8A, bridge=xen-br0' ]

# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

disk = [ 'file:/etc/xen/images/ubuntu.img,hda1,w' ]

# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the domain's
# IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
# You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).

# Set if you want dhcp to allocate the IP address.
# Set netmask.
# Set default gateway.
# Set the hostname.
#hostname= "vm%d" % vmid

# Set root device.
root = "/dev/hda1"

# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''  
# Root directory on the nfs server.
#nfs_root   = '/full/path/to/root/directory'

# Sets runlevel 4.
extra = "4"

# Set according to whether you want the domain restarted when it exits.
# The default is 'onreboot', which restarts the domain when it shuts down
# with exit code reboot.
# Other values are 'always', and 'never'.

restart = 'never'

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>