i want to create a domU using iscsi disk.
Since virt-manager and virt-install do not support, pls advise the config file
which will be used by xm create to create a xen guest.
Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2009/12/9 Aclhk Aclhk <aclhkaclhk@ymail.com>> > i want to create a domU using iscsi disk. > > Since virt-manager and virt-install do not support, pls advise the config file which will be used by xm create to create a xen guest.Short answer, it''d be MUCH easier to simply import the iscsi share on dom0, and then use something like phy:/dev/disk/by-path/* on your domU config file (or virt-manager/virt-install) The alternative is somewhat complicated, and might involve logging in/out all targets from the iscsi server at the same time, which (usually) is not what you want. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I used the block-script from
http://kinkrsoftware.nl/contrib/xen/block-iscsi
i created a config:
name = "c5.4-iscsi"
maxmem = 512
memory = 512
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "d"
pae = 1
acpi = 0
apic = 0
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [
"iscsi:192.168.123.253:3260-iscsi-iqn.2001-04.com.example:storage.disk1.amiens.sys1.xyz,hda,w"
, "file:/root/Desktop/c5.4.iso,hdc:cdrom,r" ]
vif = [ "bridge=xenbr0" ]
parallel = "none"
serial = "pty"
soundhw = "es1370"
error:
[root@localhost xen]# xm create c5.4-iscsi
Using config file "./c5.4-iscsi".
Error: Device 768 (vbd) could not be connected. /etc/xen/scripts/block failed;
error detected.
xen-hotplug.log
xenstore-read: couldn''t read path backend/vbd/36/768/node
pls kindly advise
--- 2009年12月9日 星期三，Aclhk Aclhk <aclhkaclhk@ymail.com> 寫道﹕
寄件人: Aclhk Aclhk <aclhkaclhk@ymail.com>
主題: [Xen-users] xen config for iscsi domU
收件人: xen-users@lists.xensource.com
日期: 2009年12月9日,星期三,上午9:41
i want to create a domU using iscsi disk.
Since virt-manager and virt-install do not support, pls advise the config file
which will be used by xm create to create a xen guest.
Yahoo!香港提供網上安全攻略，教你如何防範黑客!了解更多
-----內含下列附件-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
>>> On 2009/12/09 at 02:52, Aclhk Aclhk <aclhkaclhk@ymail.com> wrote: > I used the block-script from > http://kinkrsoftware.nl/contrib/xen/block-iscsi >And the script simply uses the iSCSI Software initiator on the dom0 to load the disk, then figures out the device automatically and uses that for the disk...pretty much what Fajar suggested. I''d like to see iSCSI support in a little bit different fashion than this. As of Xen 3.4, HVM supports gPXE, which can boot from either iSCSI or AOE. It''d be nice to be able to pass an iSCSI disk through in the Xen config and have gPXE pick it up during boot. Perhaps a pipe dream, but it would be nice. For PV domUs this should be even easier, as the iSCSI target could be connected to the dom0 to load the kernel, then the arguments for iSCSI target passed on into the created domU. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Dec 10, 2009 at 3:36 AM, Nick Couchman <Nick.Couchman@seakr.com> wrote:> I''d like to see iSCSI support in a little bit different fashion than this. As of Xen 3.4, HVM supports gPXE, which can boot from either iSCSI or AOE. It''d be nice to be able to pass an iSCSI disk through in the Xen config and have gPXE pick it up during boot. Perhaps a pipe dream, but it would be nice. For PV domUs this should be even easier, as the iSCSI target could be connected to the dom0 to load the kernel, then the arguments for iSCSI target passed on into the created domU.Last time I check, using iscsi target directly in domU is still slower compared to importing it on dom0 :P That being said, a workaround I use for Linux domU is to have a small /boot on dom0 (it could be an iscsi share mounted on dom0 if you like), and let domU access the big iscsi share directly during installation. Not ideal, but enough for testing purposes. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users