thr3ads.net - Xen users - [Xen-users] problem creating Virtual Machine [Feb 2007]

If this information is useful, please help other people find it:
Share via:

ramesh ankam

2007-Feb-07 07:16 UTC

[Xen-users] problem creating Virtual Machine

Hi,

  Today i tried to do the xen installation on RHEL(2.6.16.29) on my x86
system. I have installed successfully but when i am trying to create a
virtual machine, I failed. I have attached my VM configuration file with
this mail. Please help me out in creating the virtual machine. I guess i am
going wrong with my disk options in the configuration file.

create command i am using is :

# xm create -c myvmconf vmid=1


The error message i am getting is :

[root@localhost home]#  xm create -c xmexample55 vmid=1
Using config file "/etc/xen/xmexample55".
Error: Device 2055 (vbd) could not be connected. Backend device not found.

when I gave df -k on my machine this is what i am able to see:

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda8             20161172  10904360   8232672  57% /
/dev/sda7               101086     37403     58464  40% /boot
none                    130524         0    130524   0% /dev/shm
/dev/sda6             10231392    218160  10013232   3% /mnt/proj

My VM configuration file is :

 # -*- mode: python; -*-

#===========================================================================
# Python configuration setup for ''xm create''.

# This script sets the parameters used when a domain is created using
''xm
create''.

# You use a separate script for each domain you want to create, or

# you can set the parameters for the domain on the xm command line.

#===========================================================================


#----------------------------------------------------------------------------

# Kernel image file.

kernel ="/boot/vmlinuz-2.6.16.29-xen"


 # Optional ramdisk.

ramdisk = "/boot/initrd-2.6.16.29-xen.img"


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

#builder=''linux''


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

#

# WARNING: Creating a domain with insufficient memory may cause out of

# memory errors. The domain needs enough memory to boot kernel

# and modules. Allocating less than 32MBs is not recommended.

memory = 64


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

name = "ExampleDomain"

# 128-bit UUID for the domain. The default behavior is to generate a new
UUID

# on each call to ''xm create''.

#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"


 # List of which CPUS this domain is allowed to use, default Xen picks

#cpus = "" # leave to Xen to pick

#cpus = "0" # all vcpus run on CPU0

#cpus = "0-3,5,^1" # run on cpus 0,2,3,5


 # Number of Virtual CPUS to use, default is 1

#vcpus = 1



#----------------------------------------------------------------------------

# Define network interfaces.


 # By default, no network interfaces are configured. You may have one
created

# with sensible defaults using an empty vif clause:

#

# vif = [ '''' ]

#

# or optionally override backend, bridge, ip, mac, script, type, or vifname:

#

# vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]

#

# or more than one interface may be configured:

#

# vif = [ '''', ''bridge=xenbr1'' ]


 vif = [ '''' ]



#----------------------------------------------------------------------------

# 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 = [ ''phy:hd0,sda7,w'' ]



#----------------------------------------------------------------------------

# Define to which TPM instance the user domain should communicate.

# The vtpm entry is of the form
''instance=INSTANCE,backend=DOM''

# where INSTANCE indicates the instance number of the TPM the VM

# should be talking to and DOM provides the domain where the backend

# is located.

# Note that no two virtual machines should try to connect to the same

# TPM instance. The handling of all TPM instances does require

# some management effort in so far that VM configration files (and thus

# a VM) should be associated with a TPM instance throughout the lifetime

# of the VM / VM configuration file. The instance number must be

# greater or equal to 1.

#vtpm = [ ''instance=1,backend=0'' ]



#----------------------------------------------------------------------------

# 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.

dhcp="dhcp"

# Set netmask.

#netmask
# Set default gateway.

#gateway
# Set the hostname.

#hostname= "vm%d" % vmid


 # Set root device.

root = "/dev/sda8 ro"


 # Root device for nfs.

#root = "/dev/nfs"

# The nfs server.

#nfs_server = ''169.254.1.0''

# Root directory on the nfs server.

#nfs_root = ''/full/path/to/root/directory''


 # Sets runlevel 4.

extra = "4"



#----------------------------------------------------------------------------

# Configure the behaviour when a domain exits. There are three
''reasons''

# for a domain to stop: poweroff, reboot, and crash. For each of these you

# may specify:

#

# "destroy", meaning that the domain is cleaned up as normal;

# "restart", meaning that a new domain is started in place of the old

# one;

# "preserve", meaning that no clean-up is done until the domain is

# manually destroyed (using xm destroy, for example); or

# "rename-restart", meaning that the old domain is not cleaned up, but
is

# renamed and a new domain started in its place.

#

# The default is

#

# on_poweroff = ''destroy''

# on_reboot = ''restart''

# on_crash = ''restart''

#

# For backwards compatibility we also support the deprecated option restart

#

# restart = ''onreboot'' means on_poweroff =
''destroy''

# on_reboot = ''restart''

# on_crash = ''destroy''

#

# restart = ''always'' means on_poweroff =
''restart''

# on_reboot = ''restart''

# on_crash = ''restart''

#

# restart = ''never'' means on_poweroff =
''destroy''

# on_reboot = ''destroy''

# on_crash = ''destroy''


 #on_poweroff = ''destroy''

#on_reboot = ''restart''

#on_crash = ''restart''



#===========================================================================
Thanks,

Ankam.


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

Jerry Amundson

2007-Feb-07 18:17 UTC

head link

Re: [Xen-users] problem creating Virtual Machine

On 2/7/07, ramesh ankam <ramesh.ankam@gmail.com>
wrote:>
> Error: Device 2055 (vbd) could not be connected. Backend device not found.
OK. That error indicates the "backend" device is not found.... :-)
>  when I gave df -k on my machine this is what i am able to see:
>
>  Filesystem           1K-blocks      Used Available Use% Mounted on
>  /dev/sda8             20161172  10904360   8232672  57% /
>  /dev/sda7               101086     37403     58464  40% /boot
>  none                    130524         0    130524   0% /dev/shm
>  /dev/sda6             10231392    218160  10013232   3% /mnt/proj
And that won''t find your "backend" device either, because....
> disk = [ ''phy:hd0,sda7,w'' ]
Your "backend" device is the mysterious "hd0". The rest is
an exercise
I''ll leave to you... :-)

jerry

-- 
"Pay no attention to that man behind the curtain!"

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

Xen users - Feb 2007 - problem creating Virtual Machine

[Xen-users] problem creating Virtual Machine

Re: [Xen-users] problem creating Virtual Machine