Thanks Mark.
The whole disk naming method did not work. The specific
method did work.
I mknod'd /dev/console and /dev/null to fix the "Warning:
unable to open initial console" message/hang and have
VM1 running now.
Mark Williamson wrote:
2. sdb = Contains a fresh install of Fedora Core 3 to
be used for domains, as prompted by the following:
"The first step in creating a new domain is
to prepare a root filesystem for it to boot off.
Typically, this might be stored in a normal
partition, an LVM or other volume manager partition,
a disk file or on an NFS server. A simple way to
do this is simply to boot from your standard OS
install CD and install the distribution into
another partition on your hard drive."
sdb1 = /
sdb2 = swap
sdb3 = /tmp
sdb5 = /var
sdb6 = /data
Try:
disks = ['phy:sdb,sdb,w']
If that doesn't work (I can't remember if exporting whole disks works) then
export the partitions individually:
disks = [ 'phy:sdb1,sdb1,w', 'phy:sdb2,sdb2,w', 'phy:sdb3,sdb3,w' ... and so
on.
Set the first entry in this list to calculate the> offset of the
domain's root partition, based on the
domain ID. Set the second to the location of /usr if you
are sharing it between domains (e.g. disk =
['phy:your_hard_drive%d,sda1,w' % (base_partition_number
+ vmid), 'phy:your_usr_partition,sda6,r' ]"
I understand the Python array creation in that and nothing
else :)
This is a more advanced feature of the comfig files, intended to allow you to
pass an additional variable "vmid" into "xm create" and automatically
generate the disk, network, etc settings for several domains using a single
config file. It's rarely used and for your configuration you should probably
ignore it.
Cheers,
Mark
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home