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

[Xen-devel] [BUG] xen-create-image memory vs config file

  • To: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Jeroen van der Ham <vdham@xxxxxx>
  • Date: Tue, 25 Feb 2014 16:33:25 +0100
  • Delivery-date: Tue, 25 Feb 2014 15:50:37 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>


I’m trying to use xen-create-image to create an installed Xen machine. If I do 
the following:

# sudo xen-create-image —hostname=foobar --memory=2048 --swap=1024M --size=10G 
--lvm=VolumeGroupXen --dist=wheezy --fs=ext3 
--mirror=http://ftp.nl.debian.org/debian --genpass=1 --vcpus=2
ERROR: 'memory' argument takes a suffixed integer.

This does not work, because the memory argument is incorrect. So I adapt it:

# sudo xen-create-image —hostname=foobar --memory=2048M --swap=1024M --size=10G 
--lvm=VolumeGroupXen --dist=wheezy --fs=ext3 
--mirror=http://ftp.nl.debian.org/debian --genpass=1 --vcpus=2

This installs the machine successfully. If I then continue:

# sudo xl create /etc/xen/foobar.cfg
Parsing config from /etc/xen/foobar.cfg
/etc/xen/foobar.cfg:13: warning: parameter `memory' is not a valid number

This means I have to edit the configuration file and remove the “M” from the 
memory number.

Seems to me like xen-create-image and xl need to have a friendly argument on 
how to handle memory numbers.


Xen-devel mailing list



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