Blackberry p2v Conversion Blue Screen after Conversion completed successfully

[Ashrafali79]

Dears,

I tried to convert a blackberry server by vmware converter 5 and the conversion completed successfully but when i go to the esxi5 to power on the black berry virtual machine i found the machine give blue screen and restarted and i didn't able to pause the screen of blue screen to reed the information.

any advise please

[alwaysnodowntim]

Did you do a windows update as well as updating drivers before the conversion? Did you stop the Blackberry services before the conversion. Was this a Hot or Cold migration (powered-on vs. powered-off)?

[Ashrafali79]

Dear Collegue,

i make the conversion from physical to virtual and the destination is the vmware infrastructure vmware vsphre 5.

yes i did windows update,stopped the Blackberry services before the conversion and this a Hot migration (powered-on)

[alwaysnodowntim]

Are you able to get the blue screen error upon powering on the vm?

[Ashrafali79]

yes the Blue screen appear when powring the vm and the this is the vmx file information:

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "MMOSEGYHQ033.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
displayName = "MMOSEGYHQ033"
extendedConfigFile = "MMOSEGYHQ033.vmxf"
numvcpus = "2"
cpuid.coresPerSocket = "2"
memsize = "4096"
ide0:0.present = "TRUE"
ide0:0.fileName = "MMOSEGYHQ033.vmdk"
ide0:1.present = "TRUE"
ide0:1.clientDevice = "TRUE"
ide0:1.deviceType = "cdrom-raw"
ide0:1.startConnected = "FALSE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.networkName = "VLan 30"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:8b:0e:44"
usb.present = "TRUE"
ehci.present = "TRUE"
disk.EnableUUID = "TRUE"
guestOS = "longhorn"
uuid.bios = "42 0b 13 88 33 f7 70 b3-ef ec 24 1b 43 76 a7 72"
vc.uuid = "50 0b f9 61 0d 1f 5a 14-8e 6f 8f 1c f6 8e ff 92"
sched.cpu.affinity = "all"
sched.mem.affinity = "all"
vmci0.id = "1131849586"
uuid.location = "56 4d 46 ba d1 d6 f9 7e-41 33 3f e4 f2 67 9c fc"
cleanShutdown = "TRUE"
replay.supported = "FALSE"
sched.swap.derivedName = "/vmfs/volumes/4f834cd8-91cc0474-460b-101f74317a4a/MMOSEGYHQ033/MMOSEGYHQ033-861481c6.vswp"
replay.filename = ""
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
vmci0.pciSlotNumber = "35"
usb:1.present = "TRUE"
hostCPUID.0 = "0000000b756e65476c65746e49656e69"
hostCPUID.1 = "000206c220200800029ee3ffbfebfbff"
hostCPUID.80000001 = "0000000000000000000000012c100800"
guestCPUID.0 = "0000000b756e65476c65746e49656e69"
guestCPUID.1 = "000206c200020800829822031febfbff"
guestCPUID.80000001 = "00000000000000000000000128100800"
userCPUID.0 = "0000000b756e65476c65746e49656e69"
userCPUID.1 = "000206c220200800029822031febfbff"
userCPUID.80000001 = "00000000000000000000000128100800"
evcCompatibilityMode = "FALSE"
vmotion.checkpointFBSize = "4194304"
usb:1.speed = "2"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
tools.remindInstall = "TRUE"
bios.bootRetry.enabled = "TRUE"
mem.hotadd = "TRUE"
bios.bootRetry.delay = "30000"
floppy0.present = "FALSE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"

[alwaysnodowntim]

the .vmx file is just the configuration file.  I will need the stop error that windows is outputting when you power on the vm.  Normally when a windows os blue screens, that screen doesn't disappear.  Can you try to power on the vm to get the stop error that windows is posting on screen?

[continuum · Accepted solution]

you get a 7b bluescreen because you allowed Converter to misconfigure the VM.

Converter cant patch systems with IDE disks so you should select an appropriate scsi driver during the process.

As guestOS used is longhorn I guess this was a Vista, Windows7 or 2008.
Select lsilogic or lsi-sas

[Ashrafali79]

it solved after remigrate the Black Berry server again but change Disk Controllers to   LogicSaS