[nflug] vmware player bsod

[Jason Lasker]

If you are using vmware it does not really matter what the actual host
hardware is.  It uses it's own BIOS and presents virtual hardware to the
guest OS.  

What you can control is how many processors and how much RAM you dedicate to
the virtual machine(s).  

Virtual machines are portable from one host to the next.  I believe they are
even portable between Windows and Linux hosts. 

The vmware tools enhance performance using "better" drivers for disk, net,
and video and allow some scripting.

Lasker at eng.buffalo.edu

-----Original Message-----
From: nflug-bounces at nflug.org [mailto:nflug-bounces at nflug.org] On Behalf Of
Stephen Burke
Sent: Wednesday, February 14, 2007 9:01 PM
To: nflug at nflug.org
Subject: Re: [nflug] vmware player bsod

Thanks for the response, Mark.
The two methods seem quite similar, except for the gentoo/ubuntu differences
and the ubuntu guy recommending installing the vmware tools from inside the
player. But I am still not quite sure what drivers you're talking about.
Something to be set in windows or ubuntu?

Actually, I am on the verge of putting a new motherboard in this machine,
probably of the amd64 variety, so that's probably going to screw everything
up, right?

Thanks,
S.

Mark Musone wrote:
> I was reading your web site reference..and the thing is that you want 
> to make that vmware profile, but disable/change all those special 
> drivers when you are booted in that profile.
> 
> 
> Also try this 
> http://rougebob.com/Running-a-Windows-Partition-in-VMware.htm
> 
> I know that I had to specifically change the IDE driver to a windows 
> standard one, then it worked fine.
> 
> Matk
> 
> 
> -----Original Message-----
> From: nflug-bounces at nflug.org [mailto:nflug-bounces at nflug.org] On 
> Behalf Of Stephen Burke
> Sent: Tuesday, February 13, 2007 11:24 PM
> To: nflug at nflug.org
> Subject: [nflug] vmware player bsod
> 
> So, after finding this
> 
> http://www.advicesource.org/ubuntu/Run_Existing_Windows_Instalation_On
> _Ubunt
> u_With_Vmware_player.html
> 
> on digg recently, I decided to finally try diving into the vm realm 
> (mainly to avoind the creeping heebie jeebies and feeling of despair 
> that booting M$ gives me anymore). I followed the instructions there, 
> and I can ALMOST get things going, but as soon as xp gets to the 
> splashscreen it crashes with a bsod that says:
> 
> "A problem has been detected and windows has been shut down to prevent 
> damage to your computer.
> 
> If this is the first time you've seen this stop error screen, restart 
> your computer. If this screen appears again, follow these steps:
> 
> Check for viruses on your computer. Remove any newly installed hard 
> drives or hard drive controllers. Check your hard drive to make sure 
> it is properly configured and terminated. Run CHKDSK /F to check for 
> hard drive corruption, and then restart your computer.
> 
> Technical information:
> 
> *** STOP: 0x0000007B (0xFC8D2640, 0x0000034, 0x00000000, 0x00000000)"
> 
> Then the vmware player window starts flashing red (e17 thing for not 
> responding from what I gather), so killing the window is the only way to
>   quit.
> 
> After that "ps -ae | grep vm" still shows this:
> 
>   4391 ?        00:00:00 vmnet-bridge
>   4405 ?        00:00:00 vmnet-natd
>   5086 ?        00:00:00 vmnet-netifup
>   5100 ?        00:00:00 vmnet-netifup
>   5114 ?        00:00:00 vmnet-dhcpd
>   5115 ?        00:00:00 vmnet-dhcpd
> 
> And I still see the vmware window in the middle click window list no 
> matter how many times I kill it. I can't seem to kill it completely 
> without logging out. It keeps popping back up when I return to the 
> desktop it was started on.
> 
> This machine has a 1.3G duron processor and 512M ram. Maybe not enough 
> to run vmware?
> 
> The xp system still boots and runs fine, and I can't see how it could 
> be infected with a virus since it's almost never used, though as a toy 
> inside vmware it might be amusing.
> 
> I'm can't actually recall how or if it's even possible to get to a CL 
> in xp to actually run CHDSK /F.
> 
> Strangeness indeed.
> Clearly I'm doing something terribly wrong, but I can't see what. 
> since the instructions don't seem that complex Has anyone seen this 
> sort of thing before?
> Any ideas?
> 
> Thanks,
> S.
> 
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
> 
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
> 

_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug


_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug