[nflug] vmware player bsod

Thu Feb 15 10:58:46 EST 2007

Try this URL, this has helped me in the past..

Details

I get an INACCESSIBLE_BOOT_DEVICE error when booting my Windows 2000,
Windows XP or Windows Server 2003 guest operating system from a raw disk.

Solution

This issue may appear due to one of several problems, as described in the
following sections.

ACPI Issue

The following, older versions of GSX Server and Workstation may display this
error due to an ACPI issue. Please see one of these articles for a solution:

GSX Server 2.5:
www.vmware.com/support/gsx25/doc/disks_dual-boot_acpi_gsx.html
GSX Server 2.0.x:
www.vmware.com/support/gsx2/doc/disks_dual-boot_acpi_gsx.html
Workstation 3.x: www.vmware.com/support/ws3/doc/ws32_disks8.html#1009931
If the ACPI solution does not work for these versions of your VMware
software, the INACCESSIBLE_BOOT_DEVICE message may be due to a driver error.
Please see the solution that appears in the following section.

IDE Controller Driver Issue

For all versions of GSX Server, Workstation and VMware Server, this problem
can also be caused by the use of a third party IDE controller driver on your
native Windows 2000, Windows XP or Windows Server 2003 partition.

To solve this problem, you need to replace the third party IDE driver with a
standard IDE driver. Complete the following steps:

Boot natively into your Windows partition (do not boot the guest operating
system from a virtual machine).
Create a copy of the original hardware profile.
Shut down and boot natively again using the copy of the hardware profile.
Open the Device Manager, select the IDE Controller object and edit its
properties.
Click the Driver tab, then click the Update Driver button.
Click Next.
Select Display a list of the known drivers, then click Next.
Select Standard Dual channel PCI IDE controller instead of the driver that
matches your physical IDE controller.
Click Next, then click Next again.
Click Finish, then Close.
Shut down the operating system when prompted. Boot into your Linux host,
start the virtual machine and power it on.
Select the edited hardware profile when prompted.
This allows you to load the standard IDE driver and continue booting past
this problem.

-----Original Message-----
From: nflug-bounces at nflug.org [mailto:nflug-bounces at nflug.org] On Behalf Of
Stephen Burke
Sent: Thursday, February 15, 2007 1:35 AM
To: nflug at nflug.org
Subject: Re: [nflug] vmware player bsod

Indeed, the bsod does talk about new hard drives, which would mean IDE, 
but I've never actually had to toy with IDE drivers before so I'm a bit 
lost. I'm in the vmware profile, on the driver tab of the Primary IDE 
Channel Properties window and I see buttons for Driver Details, Update 
Driver, Roll Back Driver, and Uninstall. I see two drivers in the driver 
details window (C:\WINDOWS\System32\DRIVERS\atapi.sys and 
C:\WINDOWS\System32\storprop.dll), but I can't do much with them from 
here. Update doesn't sound right for this, and I have nothing to roll 
back to. Where might I find the generic drivers? A different window? Do 
I just uninstall and log out before it goes looking for the hard drive 
again? That would seem to negate the bootable vmware profile, however.

Thanks,
S.

Mark Musone wrote:
> You need to remove/change the windows drivers..
> 
> You need to boot straight into windows, create a "vmware" profile, then
boot
> up using that profile and change the IDE drivers and a few others to use
the
> standard/generic windows drivers.
> 
> Once you have a booting windows machine with generic drivers in the
"vmware"
> profile, then try booting it in vmware using the "vmware" profile.
> 
> 
> The problem is that your existing windows install is expecting certain
real
> hardware that vmware does not have. So windows is trying to boot up and is
> trying to load drivers for devices that don't exist. Windows get miffed
and
> craps out..
> 
> I actually do this a lot (take a physical machine and virtualize it) it's
a
> pain in the butt, but after a while it's not too bad and it gets easier..
> 
> The only thing the new motherboard may screw up is the cpu, everything
else
> is essentially virtualized..
> 
> Feel free to let me know if you have any questions.
> 
> Mark
> 
> 
> -----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
> 

_______________________________________________
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