Hi,
I've tried to create a VM from a working Win7x64 SP1 installation but it fails to boot with Stop 7B in Player 4.0.2
The log file contains:
Therefore I assume the error is triggered by a missing or wrong driver for CDROM ide1:0
I've tried a Windows 'startup repair' but without success.
The log contains the following I deemed relevant for CDROM related issue diagnosis:
2012-04-23T22:56:07.384+02:00| vmx| I120: DICT ide1:0.present = TRUE
2012-04-23T22:56:07.384+02:00| vmx| I120: DICT ide1:0.autodetect = FALSE
2012-04-23T22:56:07.384+02:00| vmx| I120: DICT ide1:0.deviceType = cdrom-raw
2012-04-23T22:56:07.384+02:00| vmx| I120: DICT ide1:0.startConnected = TRUE
2012-04-23T22:56:07.384+02:00| vmx| I120: DICT ide1:0.fileName = 😧
2012-04-23T22:56:15.200+02:00| vcpu-0| I120: CDROM: Connecting ide1:0 to 'D:'. img=0 raw=1 remote=0
2012-04-23T22:56:15.208+02:00| vcpu-0| I120: CDROM-SG: Opening device '\\?\ide#cdromhp_dvd_a__ds8a8sh_______________________kh61____#4&36d42ba5&0&0.1.0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}'
2012-04-23T22:56:15.209+02:00| vcpu-0| I120: SGWIN: '\\?\ide#cdromhp_dvd_a__ds8a8sh_______________________kh61____#4&36d42ba5&0&0.1.0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}' Length 24 MaxTransferLength 131072 MaxPhysPages 33
2012-04-23T22:56:15.209+02:00| vcpu-0| I120+ SGWIN: AlignMask 0x2 !AsyncEvent !TaggedQ ScanUp PIO
2012-04-23T22:56:15.209+02:00| vcpu-0| I120: SGWIN: Device's alignment mask of 0x2 cannot be satisfied. Rounding it up to 1 less than nearest power of 2.
2012-04-23T22:56:15.214+02:00| vcpu-0| I120: CDROM: Checking initial physical media state...
2012-04-23T22:56:15.220+02:00| vcpu-0| I120: CDROM: initial physical CDROM state is 1 (sense)
...
2012-04-23T22:57:17.330+02:00| vmx| I120: CDROM ide1:0: CMD 0x5a (MODE SENSE(10)) FAILED (key 0x5 asc 0x24 ascq 0)
"ide1:0.deviceType = cdrom-raw" is the same type used for a different but working VM I created from scratch on the same hardware.
searches regarding CDROM as root cause revealed http://www.bogus.net/stop_7b_error.html but referred to XP OS version only therefore I was not sure if they would still apply.
Any comments regarding root cause & suggestions on how to get the non-working VM fixed appreciated.
Thanks
Mike
I guess your imported vmdk is connected as IDE0:0 ?
That will not work - attach the vmx-file please
how exactly did you import this VM - with Converter 5 ? - did you order LSI-SAS controller during P2V ?
sorry I should have added the relevant part of VM config
Process to create was:
1) SysInternals Disk2VHD
2) StarWind V2V
3) manual changes of .vmx based on a working VM on same hardware
boot process shows the Win 7 animated logo for several seconds and seems to reach nearly the point when 'start screen' for login would be next
Hope this clarifies the problem.
Thanks
Mike
I would use
scsi0.virtualDev = "lsisas1068"
instead - anyway - looks like all you need to do is adjust the LSI-driver so that it starts at boot.
Please read my notes http://sanbarrow.com/p2v2008r2.html
it tells you what to do - you could also try to use Converter 5 - configure machine option - but the result should be similar
I used scsi0.virtualDev = "lsisas1068" as suggested but this change made it worse as after power up instantly error 'Unable to allocate a PCI SCSI adapter' gets displayed.
I had read notes http://sanbarrow.com/p2v2008r2.html before starting the post but felt it did NOT apply.
This seems to be confirmed by the test.
Perhaps you could comment on my assumed root cause 'assume the error is triggered by a missing or wrong driver for CDROM ide1:0'?
Thanks
Mike
your vmx may have an old entry assigning the scsi-controller to PCI-slot 16.
It should use slot 160 !
If unsure - please attach the completee vmx-file that you have now.
I am 99% sure that the 7b BSOD is not caused by the IDE settings you use
I've done the following:
1) manually changed 'scsi0.pciSlotNumber = 160' (see log part below showing all actually used config values)
2) starte VM and got same error as before " I120: [msg.lsilogic.badPCI] Unable to allocate a PCI SCSI adapter."
3) after power off .vmx contains 'scsi0.pciSlotNumber = "21"' again!
From my view this could potentially indicate a conflicting setting triggering this error. I'll
I've attached the full log and vmx.
I'll use the converter 5 now to see what vmx it will produce.
try the attached vmx-file
your settings were changed for a PCI-slot while the LSI-SAS controller uses a PCIe slot - so it could not work
still same error 'Too many PCI devices are already configured'
Player adds the following entries to .vmx
log:
2012-04-24T13:30:23.132+02:00| vmx| I120: Chipset version: 0x13
2012-04-24T13:30:23.135+02:00| vmx| I120: Device scsi0 requested without secondary PCI slots available.
2012-04-24T13:30:23.143+02:00| vmx| I120: SCSI DEVICE (ide1:0): Computed value of ide1:0.useBounceBuffers: default
2012-04-24T13:30:23.143+02:00| vmx| I120: DISKUTIL: ide1:0 : capacity=0
2012-04-24T13:30:23.143+02:00| vmx| I120: DISKUTIL: ide1:0 : geometry=0/0/0
2012-04-24T13:30:23.143+02:00| vmx| I120: SCSI: scsi0: intr coalescing: on period=50msec cifTh=4 iopsTh=2000 hlt=0
2012-04-24T13:30:23.147+02:00| vmx| W110: LSILogic: Failed to register PCI slot.
2012-04-24T13:30:23.147+02:00| vmx| I120: Msg_Post: Error
2012-04-24T13:30:23.147+02:00| vmx| I120: [msg.lsilogic.badPCI] Unable to allocate a PCI SCSI adapter.
2012-04-24T13:30:23.147+02:00| vmx| I120+ Too many PCI devices are already configured.
2012-04-24T13:30:23.147+02:00| vmx| I120: [msg.vmxlsilogic.poweronFailed]
2012-04-24T13:30:23.147+02:00| vmx| I120+ Failed to configure scsi0.
2012-04-24T13:30:23.147+02:00| vmx| I120: ----------------------------------------
2012-04-24T13:30:29.578+02:00| vmx| I120: Module DevicePowerOn power on failed.
2012-04-24T13:30:29.578+02:00| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0
2012-04-24T13:30:29.598+02:00| vmx| I120: MKS local poweroff
2012-04-24T13:30:29.601+02:00| usbCCIDEnumCards| I120: USB-CCID: Card enum thread exiting.
2012-04-24T13:30:29.606+02:00| vmx| I120: scsi0:0: numIOs = 1 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
2012-04-24T13:30:29.607+02:00| vmx| I120: Closing disk scsi0:0
2012-04-24T13:30:34.732+02:00| vmx| I120: AIOWIN32C: asyncOps=2 syncOps=1204 bufSize=0Kb fixedOps=0 sgOps=1193 sgOn=1
then you did NOT use the vmx-file I attached
I've repeated the test and made screenshots of the vmx before I ran player.
0) closed player and renamed all existing .vmx and .log file in the directory
1) downloaded 'edited.vmx' again
2) open in editor and modified annotation = "VM_MHolzer_EB8440 edited" and displayName = "VM_MHolzer_EB8440 edited" and saved as VM_MHolzer_EB8440.edited.vmx (see attached VM_MHolzer_EB8440.edited.vmx.png)
3) right clicked and used 'open with vmware player' to run exactly this file
4) same error 'Too many PCI devices are already configured' (see vmware.log)
5) opened VM_MHolzer_EB8440.edited.vmx and saw again below new entries apprently added by player
What else can I do to proof that I'm not cheating you and execute the process as described?
ok - I see you are innocent - this is a new behaviour of WS8 / VMplasyer I had not noticed before
use the new attached one
slight improvement, we are back to where it started
.vmx gets updated with scsi0.pciSlotNumber = "160" as desired but still it ends with identical bsod after windows logo displayed for several seconds.
looks like my case is the 1% not solved by standard approach.
As 'Windows startup repair' can't fix the problem I'm still stuck.
How about reconsidering the CDROM drivers as the root cause?
use the approach with the Windows 7 recovery CD I describe in the link I already gave you
if you dont have one - get one
http://neosmart.net/blog/2009/windows-7-system-repair-discs/
The IDE-driver for the CDrom is 99% innocent - feel free to remove the CD-drive for a test
upgrade to Player version 4.0.3 solved my issue finally without going thru the process descibed on http://sanbarrow.com/p2v2008r2.html
Thanks
Mike