VMWare Blue Screen?

spencer · 05-30-2006, 03:13 PM

Hello All!!

quick question... maybe someone else has had this problem.

Created an image from scratch in VMWare 5.5. Everything works great up until the point at which i take an image of it and then try to deploy that image to another virtual session. When the session starts booting up the Windows XP logo comes up and then blue screens rebooting itself and stays in that loop until i interfere...

Probably something simple here... anyone?

spencer · 05-31-2006, 03:44 PM

hello?

djdk74 · 05-31-2006, 03:50 PM

I had a similar issue with Windows 2000. Is this image using sysprep? If it is you may need to add a mass storage device to your sysprep.inf. You could also try changing your hard disk in your VM session from SCSI to IDE.

dominique · 05-31-2006, 03:52 PM

Spencer,

VMWare is known for some duplicate MacAddress, all VMWare Sessions are seen under the DS console with the same Mac Address and creating issue when using it... When you deploy is it another Mac Address or the same as the source?
How do you deploy the image? Job, RDeploy command?

Thanks,
Dom

spencer · 05-31-2006, 04:00 PM

It looks like it is using a Virtual IDE Hard Drive... it says under disk drives VMware Virtual IDE Hard Drive... i'm not sure if there is somewhere else to look...

Also, Yes I am using sysprep, and yes i have a mass storage section in there but the .inf was built from another machine. I'm not sure if that would make a difference or not. I am only using this one machine so I do not have any duplicate mac's.

Here is something I just found out... The virtual machine will fail to boot right after I run sysprep. So I am starting to think it has nothing to do with rdeploy at all...

So... here is the situation again:

1. Create Image and all works fine. Reboot still works fine.
2. Run sysprep and use -forceshutdown command
3. Restart Virtual Machine and when it gets to the Windows XP logo the system blue screens and reboots...

??

djdk74 · 05-31-2006, 04:15 PM

What stop message is the bluescreen displaying?

spencer · 05-31-2006, 04:23 PM

*** STOP: 0X0000007B (0xF9DDF528, 0xC0000034, 0x000000000, 0x00000000)

djdk74 · 05-31-2006, 04:28 PM

This may help. Not sure...
http://support.microsoft.com/?kbid=303786

kschroeder · 05-31-2006, 09:24 PM

Well there is an easier way to accomplish this. After the VM shuts down, just make a copy of the entire directory where the .VMDK files are. Open the .VMX file and confirm that you've moved the disk. Whammo, instant image.

spencer · 06-01-2006, 09:19 AM

What do you mean by instant image? How would I use the .vmx file with deployment server?

Quote:

Originally Posted by kschroeder

Well there is an easier way to accomplish this. After the VM shuts down, just make a copy of the entire directory where the .VMDK files are. Open the .VMX file and confirm that you've moved the disk. Whammo, instant image.

spencer · 06-01-2006, 12:46 PM

I ran the sysprep /bmsd command on the virtual machine and it rebuilt the massstorage section in the .inf file.

It still blue screens when it tries to boot... same stop error.

spencer · 06-07-2006, 08:28 AM

bump...

Brandon · 07-28-2006, 02:35 PM

The easiest fix is to use VMWare Virtual Machine Importer 2. This will fix the 3rd party images on VMware like rdeploy and ghost.

http://www.vmware.com/products/vmimporter/

ShawnD · 09-29-2006, 09:35 PM

I have recently ran across the same problem. In the past I have created several VM's, a few win98's and a few XP's. I liked being able to use the same images we drop on production machines on the VM. It used to work perfectly, boot the VM to PXE, connect to the DS select the correct image and in about 30-40 minutes you where looking at a login prompt. However, Monday I tried to create a new XP based VM. After the image came down It goes to the XP splash screen for a second then a BSOD with a STOP error.
I opened the image and made sure it had sysprep and that the build mast storage section was yes. I then tried this image on a physical machine and it worked fine. Later, I tried another known good image and had the same problem.
What is really weird is that I have used these exact same images to create VM's on this same machine in the past. The only thing that has changed is the memory in the Host has went from 2GB-->512MB. The host uses SATA drives, where the Image was created on IDE's. When setting up the new VM I made sure it is using IDE for the VM.
I am really at a loss as to why this is not working know and has worked perfectly in the past. Like I said to the best of my knowledge the only thing that has changed in the past was the decrease in memory and maybe a few windows updates.

the only thing I can think to try is setting the VM drive type to SCSI since it is physically on a SATA. I dont remember doing this in the past but I am at a loss.

kschroeder · 09-30-2006, 04:14 AM

ShawnD:
I don't suppose your production image has a different HAL installed does it? I've had an ACPI-multiprocessor HAL image crash like that on a VM if the VM didn't have virtual dual-core enabled. Did you mean that the Guest OS went from 2GB to 512MB, or the host (running VMWare Workstation)? I've also had some weirdness with the latest VMWare 5.5.2; I don't suppose you upgraded did you?

AaronM · 01-03-2007, 02:41 PM

The stop 7B error is a mass storage driver problem.

While in PE you need to load the approprate hives and inject some keys, as well as copy the correct drivers to the prod machine.

I'm trying to dig the exact settings up, as I've come across this this morning also, and have corrected it before.

ksweet · 01-03-2007, 02:57 PM

I build images in VM and they work just fine...

in a nut shell here are the steps I use

1 Install XP
2 Create a generic sysprep.inf use the BMSD command to add in all the mass storage controlers
3 run sysprep and have VM re-boot and run the mini setup - all mass storage controler drivers are now installed
4 continue building your image
5 Create final sysprep.inf you should not have to use the BMSD command on this version
6 sysprep VM, shut down and make image

AaronM · 01-10-2007, 10:08 PM

Here is how I solved the 7B bluescreen, using the hardware independant image I use for all my physical workstations:

http://www.altirigos.com/vbulletin/s...9120#post29120

richard612 · 01-17-2007, 04:20 PM

Try this.. Edit the VM guest's .VMX file.

Set this line: scsi0.present = "TRUE"

to

scsi0.present = "FALSE"

No, I don't understand it. It just works.

dlloyd · 07-31-2007, 10:46 AM

Spencer,

Did you find a fix for this?

I have had the same issue and resolved it by booting into the recovery console and then typing:

disable pciide

The image was created on a VM and deploys perfectly to any physical machine but when deployed back to a VM I always need to do this to get it to boot...

magnets · 09-02-2008, 11:30 PM

Richard, i wish to have your babies.

the scsi0.present = "FALSE"

edit worked a treat!

richard612 · 09-03-2008, 12:19 AM

Quote:

Originally Posted by magnets

Richard, i wish to have your babies.

Send .jpg!

newalloy · 08-24-2009, 03:00 PM

Many thanks for pointing this out! I built a VM in VMXBuilder and launched it in VMware player. I did PXE boot to load image into VM, but it would just bluescreen.

Manually editing the VMX file to set scsi to false worked.

jumtoit · 11-27-2009, 10:33 AM

Worked perfect

JimChud · 03-02-2010, 06:29 AM

unfortuantely for me doing the scsi0.present = "FALSE" screwed my test vm up and it wouldnt boot... fortunately the fix by aaronm sorted my issue on rebuilt.