Looks like I forgot to send this to the alias...
MRJ
----
A quick heads up for the iscsi, zvol, and vdisk
format putback I did into the 3.3 development
gate.
ISCSI
=====
With this putback, you can now install onto and
boot a guest using iSCSI disk(s).
The iscsi formats supported are:
phy:iscsi:/alias/<iscsi-alias>
phy:iscsi:/static/<server IP>/<lun>/<target id>
phy:iscsi:/discover/<lun>/<alias or target id>
i.e. for the following iscsi disk:
bash-3.2# iscsiadm list target -S
Target: iqn.1986-03.com.sun:02:d5ab1c26-0a7a-c6b4-98f8-d6d267eb2561
Alias: tank/iscsi/nevada/disk0
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: SUN
Product: SOLARIS
OS Device Name: /dev/rdsk/c2t600144F0499C09B800001A4D4B643700d0s2
If your dom0 is set up for discover, you can either use
the alias (if it is unique) or the target id. e.g.
phy:iscsi:/alias/tank/iscsi/nevada/disk0
or
phy:iscsi:/discover/0/iqn.1986-03.com.sun:02:d5ab1c26-0a7a-c6b4-98f8-d6d267eb2561
Or if you use a static mapping. The hotplug scripts will
add/remove static-config for you. e.g.
phy:iscsi:/static/192.168.0.70/0/iqn.1986-03.com.sun:02:d5ab1c26-0a7a-c6b4-98f8-d6d267eb2561
Here's an example virt-install onto an iscsi disk.
virt-install -p -n nevada -l /export/snv108.iso --nographics \
--noautoconsole -r 1024 \
--disk path=/alias/tank/iscsi/nevada/disk0,driver=phy,subdriver=iscsi
VDISK
=====
You can now specify the vdisk format at install time. For example,
to use a vdi file instead of the vmdk default:
virt-install -p -n nevada -l /export/snv108.iso --nographics \
--noautoconsole -r 1024 \
--disk
path=/export/nevada/disk0,size=10,driver=tap,subdriver=vdisk,format=vdi
ZVOL
====
virt-install can now create a zvol for you, i.e. to have it create
a 10g zvol @ guests/nevada/disk0
virt-install -p -n nevada -l /export/snv108.iso --nographics \
--noautoconsole -r 1024 \
--disk path=/guests/nevada/disk0,size=10,driver=phy,subdriver=zvol
_______________________________________________
xen-discuss mailing list
[email protected]
