Thanks I had not seen that one before! Jon
On Sat, Dec 20, 2008 at 9:52 PM, Ken Schaefer <[email protected]> wrote: > Hi. > > > > You can do this in two ways – Pass through disks, and direct guest access > (via iSCSI). > > > > > http://blogs.technet.com/josebda/archive/2008/02/14/storage-options-for-windows-server-2008-s-hyper-v.aspx > > > > Cheers > > Ken > > > > *From:* Jon Harris [mailto:[email protected]] > *Sent:* Sunday, 21 December 2008 4:47 AM > > *To:* NT System Admin Issues > *Subject:* Re: Hyper-V and Windows Server 2008 > > > > I don't know about John but I would have loved the ability to mount a > physical drive from a virtual machine. Then I could keep the files in a > file server on a physical drive separate from and independent of my virtual > machines. > > > > Jon > > On Fri, Dec 19, 2008 at 5:20 PM, Ken Schaefer <[email protected]> > wrote: > > Are you trying to mount the SCSI RAID array as a direct access disk in the > guest? Or do you just want to create a VHD and mount it within the guest? > > > > Cheers > > Ken > > > > *From:* John Hornbuckle [mailto:[email protected]] > *Sent:* Saturday, 20 December 2008 6:45 AM > > > *To:* NT System Admin Issues > *Subject:* RE: Hyper-V and Windows Server 2008 > > > > One exception (and someone please let me know if there's a way around this, > because I'm new to VMs in general and Hyper-V in particular)… I have an > external RAID storage device attached via SCSI cable. I don't know how to > make this device accessible through a Hyper-V guest OS, so I'm having my > users access it through the host OS (which means I have to make the host a > file server). Is there another alternative in this sort of situation? > > > > > > > > *From:* Joseph L. Casale [mailto:[email protected]] > *Sent:* Friday, December 19, 2008 12:06 PM > *To:* NT System Admin Issues > *Subject:* RE: Hyper-V and Windows Server 2008 > > > > You _*can*_ do whatever you wish the host, but it's my opinion that it > should it be segregated to a manglement network and ran completely vanilla. > > > > Whatever you do to the host introduces any potential failure or instability > for all the guests. If your host is busy chugging away, it effects all the > guests as well. > > > > jlc > > > > *From:* Reimer, Mark [mailto:[email protected]] > *Sent:* Friday, December 19, 2008 9:54 AM > *To:* NT System Admin Issues > *Subject:* Hyper-V and Windows Server 2008 > > > > Hi folks, > > > > Quick question that my googling hasn't answered for me. > > > > I understand the theory of Hyper-V, and that the first VM is the "parent". > > > > My question is: Can/Should the parent be used as a regular VM (file server, > web server or whatever I want to do with it), or should it just be the OS? > > > > I'm assuming it can/should be a VM (file server, web server whatever), but > being the first VM, will also help control the hardware/VM setup etc. As > such, the first VM should run Windows Server 2008. Other VM's can run W2K8, > but can run other OS's (in my case, I would only use W2K3) as well. Correct? > > > > Am I way off base, or is this basically it? > > > > Thanks for any advice, and have a great Christmas. > > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
