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/> ~
