always failed to create new system on separate disk

Submitted by dmaster97 on Wed, 06/01/2011 - 23:12

Hi every body,

this is my first trial using cloud min

i'm using two disk configuration for the cloudmin master. the first disk , a 80GB Disk,is configure to used with the linux master system. the second disk, 1TB, is where the created cloudmin host would be.

on the cloudmin's xen host setting, i have set base directory for virtual system to the second disk mount point. but when i create new system, cloudmin always fails with error not enough diskspace. a few hudreds gigs short.

can someone help me?

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Wed, 06/01/2011 - 23:47

How much disk space is free on both disks, and how large is the VM you are trying to create?

Submitted by dmaster97 on Thu, 06/02/2011 - 01:27

first disk is 80GB with 62GB free space second disk is 1TB with 99% free space

system created with configuration 2048 Memory, 2048 swap and 80GB HDD Space

if i create 1GB of images, the system is successfuly created in the mount point of the second disk. but failed to start the system

however, cloudmin could ajust the new 1GB images to desired size and did recognize 1TB free space on the second disk

starting up the system still result with error : Starting up durian.entsohost.com .. .. failed : Error: Unable to open config file: /xfs/xen/durian.cfg Usage: xm create [options] [vars] Create a domain based on . Options: -h, --help Print this help. --help_config Print the available configuration variables (vars) for the configuration script. -q, --quiet Quiet. --path=PATH Search path for configuration scripts. The value of PATH is a colon-separated directory list. -f=FILE, --defconfig=FILE Use the given Python configuration script.The configuration script is loaded after arguments have been processed. Each command-line option sets a configuration variable named after its long option name, and these variables are placed in the environment of the script before it is loaded. Variables for options that may be repeated have list values. Other variables can be set using VAR=VAL on the command line. After the script is loaded, option values that were not set on the command line are replaced by the values set in the script. -F=FILE, --config=FILE Domain configuration to use (SXP). SXP is the underlying configuration format used by Xen. SXP configurations can be hand-written or generated from Python configuration scripts, using the -n (dryrun) option to print the configuration. -n, --dryrun Dry run - prints the resulting configuration in SXP but does not create the domain. -p, --paused Leave the domain paused after it is created. -c, --console_autoconnect Connect to the console after the domain is created.

Submitted by JamieCameron on Thu, 06/02/2011 - 11:57

Does that file /xfs/xen/durian.cfg actually exist on the host system?

Also, make sure you have SElinux disabled on the host - I've seen cases in the past where it interferes with Xen.

Submitted by dmaster97 on Thu, 06/02/2011 - 22:39

the xen config file is exist in the cloud master. the "/xfs" is the mount point of the second disk

when i start the virtual machine using command "/usr/sbin/xm create -c /xfs/xen/durian.cfg", the virtual machine power up is successfull.

but i cannot start the virtual machine from cloudmin.

after the machine started manually, cloudmin did recognize it.

Submitted by JamieCameron on Thu, 06/02/2011 - 23:03

Did you try turning off SElinux ? You can do this by editing /etc/sysconfig/selinux , and changing the SELINUX line to SELINUX=disabled , then rebooting.

Submitted by dmaster97 on Thu, 06/02/2011 - 23:29

ok.

disabling SELinux did solve all cloudmin issue in my installation.

you might want to automaticly disable selinux on cloudmin install.

thank you very much.

regards

Submitted by Issues on Fri, 06/17/2011 - 03:24

Automatically closed -- issue fixed for 2 weeks with no activity.