|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] iSCSI target - run in Dom0 or DomU?
Keep in mind that unless you are exporting hardware ethernet cards to
DomU, you will have a significant network performance issue inside a
DomU (tech details here
http://www.cs.aau.dk/~kleist/Courses/nds-e05/presentations/2609-preformance_overheads_xen.pdf#search=%22xen%20network%20performance%22)
but if you run in Dom0 and busy up the CPU, all VMs will suffer. I would
run in DomU with an exported PCI NIC instead of using virtual devices.
Thomas Harold wrote:
We're working on setting up a test box for an eventual iSCSI SAN.
(I've dug through the archives for the last 6 months, but don't see a
good thread that discusses our situation.) Both technologies (Xen,
iSCSI) are new to us, so there's going to be a bit of a learning curve.
The test unit is an AMD Athlon64 X2 4200+ AM2 socket, 2GB RAM, and
multiple SATA drives. Since it has the AM2 socket, I believe that it
supports AMD-V (AMD's virtual technology) so we should be able to run
unmodified guest OSs on it. Any guest OSs besides the iSCSI/SAN
specific tasks will eventually be migrated off to an external box
(either new SocketF Opteron systems or AM2 Athlon64 systems).
My plan for the disks is to lay software RAID over the disks (RAID1
for the first pair, RAID10 for the second set of 6 disks). Then lay
LVM on top of mdadm's software RAID before handing it off to
iscsitarget to be divided up for use by the iSCSI initiators.
Specific questions:
1) The mdadm and LVM will need to happen in Dom0?
2) Should iscsitarget also run in Dom0 or should it be moved into a DomU?
3) I assume that ethernet card bonding should happen in Dom0 with the
bonded interface presented as a virtual interface to the DomUs?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|