Prev: usr5686e optimal settings for server 2003
Next: "Do not display last username" with Remote Desktop on Server 2008
From: bob on 10 Jun 2010 22:03 Hi , Window Server 2008 R2 Standard Edition. 4 Core Intel processor 8 Gig RAM. HyperV set up with a Win2003 Server Virtual machine running inside. Intermittant BSOD's when virtual machine is active. I have removed the unused SCSI device from the virtual machine as this has been mentioned as a possible cause of problems. Any thoughts on what else could be causing this? Has anybody out there deployed Hyper V in a production environment with out BSOD's thanks Bob
From: jaajog on 12 Jun 2010 05:43 Which one is BSODing, host or the virtual machine? Have you installed hyperv integration services in the VM? I can assure you that there are a lot of working production Hyper-V deployments. "bob" wrote: > Hi , > Window Server 2008 R2 Standard Edition. 4 Core Intel processor 8 Gig > RAM. > > HyperV set up with a Win2003 Server Virtual machine running inside. > Intermittant BSOD's when virtual machine is active. > > I have removed the unused SCSI device from the virtual machine as this > has been mentioned as a possible cause of problems. > Any thoughts on what else could be causing this? > > Has anybody out there deployed Hyper V in a production environment > with out BSOD's > thanks > Bob > . >
From: bob on 12 Jun 2010 18:24 Hi, Thanks for your reply. I accidentally started two threads on this in the newsgroup so my apologies to all for double posting. I am an absolute learner with HyperV. All I did was enable the service then build the virtual machine. It is the host that is BSODing. The integration services are required? thanks Bob On Sat, 12 Jun 2010 02:43:48 -0700, jaajog <jaajog(a)discussions.microsoft.com> wrote: >Which one is BSODing, host or the virtual machine? Have you installed hyperv >integration services in the VM? >I can assure you that there are a lot of working production Hyper-V >deployments. > >"bob" wrote: > >> Hi , >> Window Server 2008 R2 Standard Edition. 4 Core Intel processor 8 Gig >> RAM. >> >> HyperV set up with a Win2003 Server Virtual machine running inside. >> Intermittant BSOD's when virtual machine is active. >> >> I have removed the unused SCSI device from the virtual machine as this >> has been mentioned as a possible cause of problems. >> Any thoughts on what else could be causing this? >> >> Has anybody out there deployed Hyper V in a production environment >> with out BSOD's >> thanks >> Bob >> . >>
From: jaajog on 14 Jun 2010 16:12
Hi, I found your other thread also, maybe the hotfix mentioned there will help you. Btw you can disable automatic restart on BSOD by pressing F8 on Windows startup and choosing that option, then you can see what the error message is. Integration services probably will not help with host restarts, but are necessary for VMs for faster communication with host hardware. "bob" wrote: > Hi, > Thanks for your reply. > I accidentally started two threads on this in the newsgroup so my > apologies to all for double posting. > I am an absolute learner with HyperV. > All I did was enable the service then build the virtual machine. > It is the host that is BSODing. > The integration services are required? > thanks > Bob > > > On Sat, 12 Jun 2010 02:43:48 -0700, jaajog > <jaajog(a)discussions.microsoft.com> wrote: > > >Which one is BSODing, host or the virtual machine? Have you installed hyperv > >integration services in the VM? > >I can assure you that there are a lot of working production Hyper-V > >deployments. > > > >"bob" wrote: > > > >> Hi , > >> Window Server 2008 R2 Standard Edition. 4 Core Intel processor 8 Gig > >> RAM. > >> > >> HyperV set up with a Win2003 Server Virtual machine running inside. > >> Intermittant BSOD's when virtual machine is active. > >> > >> I have removed the unused SCSI device from the virtual machine as this > >> has been mentioned as a possible cause of problems. > >> Any thoughts on what else could be causing this? > >> > >> Has anybody out there deployed Hyper V in a production environment > >> with out BSOD's > >> thanks > >> Bob > >> . > >> > . > |