On the road....forgive typos.... You'll have to do an advanced install in order to get to the disk options.
Normally, you tell vmware how big a disk you want and it then makes a bunch of vmdk files which constitute that disk. In that situatin all of your data is confined to the vm and the only way to access the drives 'on the metal' is by mounting a directory into the vm as an nfs share. Conversely, when you tell a vm to use your physical disk, it does just that. Your data is stored on your actual drives. Don't do this on a drive you want, however. It's the functional equivalent of taking your drives out and putting them into another machine. J --- Sent from the road... -----Original Message----- From: "Mitchell Brown" <[EMAIL PROTECTED]> Date: Thursday, Mar 1, 2007 12:17 pm Subject: Re: [clug-talk] FreeNAS VM WAS Old Computers To: "CLUG General" <[email protected]>Reply-To: CLUG General <[email protected]> > > If you have no need for ACLs, then why FreeNAS? That's pretty much it's > only usefulness > > >Forgive me, I was over-complicating things and didn't realize ACL stood for >access control list. Yes, I will be needing this. > > >As for hooking up the drives, you can either mount the Host OS > disks/partition as shares into the VM using NFS (or CIFS if you're > putting VMWare on Windows) or you can tell VMWare to actually use the > physical disks themselves. I've only seen that done once because it > means that the disks cannot be used by the host OS. I think you'll only > ever see that in a multi-drive machine where the boot drive houses the > "Host" OS and the remaining drives are taken by the VM to make a RAID. > > >So if I run a Typical wizard in VMware and load up FreeNAS as a vmdk image, >how can I convince it to use the Host OS's drives? >AFAIK, you're confined to the clients virtual "drives" aren't you? > >------=_Part_70539_18463728.1172775127585 >Content-Type: text/html; charset=ISO-8859-1 >Content-Transfer-Encoding: 7bit >Content-Disposition: inline > ><div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt >0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">If you have no need for >ACLs, then why FreeNAS? That's pretty much it's<br>only usefulness ></blockquote><div><br>Forgive me, I was over-complicating things and didn't >realize ACL stood for access control list. Yes, I will be needing >this.<br></div> </div><br><blockquote style="border-left: 1px solid >rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" >class="gmail_quote"> As for hooking up the drives, you can either mount the >Host OS<br>disks/partition as shares into the VM using NFS (or CIFS if >you're<br>putting VMWare on Windows) or you can tell VMWare to actually use >the<br>physical disks themselves. I've only seen that done once because it ><br>means that the disks cannot be used by the host OS. I think you'll >only<br>ever see that in a multi-drive machine where the boot drive houses >the<br>"Host" OS and the remaining drives are taken by the VM to >make a RAID. ></blockquote><div><br>So if I run a Typical wizard in VMware and load up >FreeNAS as a vmdk image, how can I convince it to use the Host OS's drives? ><br>AFAIK, you're confined to the clients virtual "drives" aren't >you? ><br> </div><br> > >------=_Part_70539_18463728.1172775127585-- > >Re: [clug-talk] FreeNAS VM WAS Old Computers"Mitchell Brown" <[EMAIL >PROTECTED]>To: "CLUG General" <[email protected]> Reply-To: CLUG General ><[email protected]> _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
