|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] best practices in using shared storage for XENVirtualMachines and auto-failover?
On Thu, Oct 14, 2010 at 6:45 AM, Jeff Sturm <jeff.sturm@xxxxxxxxxx> wrote: >> -----Original Message----- >> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users- >> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of admin@xxxxxxxxxxx >> Sent: Thursday, October 14, 2010 8:37 AM >> To: 'xen-users' >> Subject: RE: [Xen-users] best practices in using shared storage for > XENVirtualMachines >> and auto-failover? >> >> It is easier to use NFS than iSCSI for shared storage target. ÂIf you > use iSCSI, you will >> need to use a cluster aware file system to avoid data corruption. ÂIf > your storage >> target can do both, just use NFS. > > You don't need a clustered filesystem. ÂYou don't need a shared > filesystem at all. ÂJust partition your shared block storage (with a > clustered logical volume manager if needed) and use a logical volume for > each domU image. Trying to get this straight in my head. :) Would you run the iSCSI initiator in the host and attach the block device to the guest? Or would you run the iSCSI initiator in the guest? How does the migration from one host machine to another work with iSCSI? -- Freddie Cash fjwcash@xxxxxxxxx _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |