vijay shankar yadav
2007-Feb-19 09:23 UTC
[Xen-users] unable to create the Unpriviledge domain
hi, i have a problem while creating the guest domain. i have three partitions /dev/VolGroup00/LogVol00 as ''/'' root partition /dev/VolGroup00/LogVol01 as /home /dev/VolGroup00/LogVol02 as swap partition i have exported the root filesystem as the root file system in the virtual machine. ( Can i do so ??? ) My config file for the domainU is as follows: <<<<<==================[ Start File ]=============================>>>>>> # -*- 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.33-xenU" # Optional ramdisk. ramdisk = "/boot/initrd-2.6.16.33-xenU.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 = 256 # 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:VolGroup00/LogVol00,sda1,r'' ] #---------------------------------------------------------------------------- # 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/sda2 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'' #=========================================================================== <<<<<===========================[ End File ]======================>>>>>> Whenever i try to create the Unprivileged domain it says : [root@localhost ~]# xm create -c vm1 Using config file "./vm1". Error: string index out of range [root@localhost ~]# can anybody please explain me what is wrong with the configuration file. Regards vijay shankar yadav. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang
2007-Feb-20 14:03 UTC
Re: [Xen-users] unable to create the Unpriviledge domain
On 2/19/07, vijay shankar yadav <vijay.yadav@nechclst.in> wrote:> > can anybody please explain me what is wrong with the configuration file.I think you have a simple error in you domU config, but I am not looking at it with all these comments and wrong linebreaks. Please repost it without all the unneeded comments, and we can look at it. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
yeh Henning is Right. No time to look and search for the right info in your config. So if you repost your config with deleting unnecesary parts, then i guess we can have a look to your problem... RAM could be a error but i am not going through ur config....so not sure... All the Best -- View this message in context: http://www.nabble.com/unable-to-create-the-Unpriviledge-domain-tf3252067.html#a9063452 Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users