[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] HVM domU on storage driver domain
On Tue, Jan 17, 2017 at 1:04 AM, Austin S. Hemmelgarn <ahferroin7@xxxxxxxxx> wrote: I don't have any specific suggestions regarding figuring out what's going on, but I do have a suggestion for a work-around. Based on what you've said, what you want is to use a domU running FreeNAS to provide storage for other domU's on the same system. The de-facto method of doing this sanely is to use a block-storage protocol instead of a network filesystem to export the storage devices, and import the block-device into dom0 (or a PV domU running as a storage driver domain) then pass them to the VM's (or, if you're not using them as boot devices, just import them in the VM directly). iSCSI is what usually gets used for this, although if FreeNAS supports it I'd suggest using ATAoE (which require near zero client-side setup when the client is Linux (literally just load the module)) or NBD (which requires significantly less client-side setup than iSCSI) as they're both much simpler to set-up on the client side and have much less protocol overhead than iSCSI. While I've never seen anyone try with a NAS running as a domU itself, I know all three options work fine with Xen when set up correctly. Hi Austin, First of all thanks you for your suggestion. What I'm trying to do here is partially for fun. I really doubt if I could see real perf difference in production. But isn't that really cool if it works? Currently I'm using both NFS && iSCSI since they are supported by freeNAS out-of-box. Haven't payed attention to AOE && NBD before but will take a look for future reference. BTW, the NAS domU works great, really. ______________________________ _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx https://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |