VMware vSphere

 View Only
  • 1.  VM shows BSOD after P2V

    Posted Jan 17, 2013 03:57 PM

    Hi everybody,

    i have done P2V with a Windows Server 2003 R2 using Converter 5.0.1 Standalone. Now the VM is booting up with a BSOD. The Errorcode 0x0000007E refers to a missing SCSI driver. The Harddisk isnt present in VMs BIOS. The VM only boots up in Safe Mode. In Safe Mode Windows tries to install the missing driver, but then i get an error telling me that the selected driver is not supported in Windows XP. I have done the following to solve this problem, with no affect:

    -       Inject the SCSI drivers to the Conversion source

    -       Copied the SCSI drivers from a working Windows Server 2003 R2 VM to the converted VM

    -       Mounted VMware Tools and tried to copy the SCSI drivers

    I am running out of ideas and I hope that someone has experienced the same problem and could give me a hint how to solve this.



  • 2.  RE: VM shows BSOD after P2V

    Posted Jan 20, 2013 07:34 AM

    I am basically stuck in the same situation.

    Any help guys?



  • 3.  RE: VM shows BSOD after P2V

    Posted Jan 20, 2013 10:15 AM

    What type of virtual disk controller did you select in the conversion wizard? For Windows 2003 the "LSI Logic Parallel" controller is the default.

    Depending on the target virtual disk type it might be possible to modify the controller type to avoid another conversion. In case there's a small .vmdk file (a text file with a few hundred bytes in size), compress/zip this .vmdk file along with the VM's .vmx file and attach the .zip file to your reply post to see what can be done.

    André



  • 4.  RE: VM shows BSOD after P2V

    Posted Jan 20, 2013 11:05 AM

    Hi Andre'

    Thanks for responding.

    I am using vCenter Conv Standalone v5.0.1.

    I am converting a server 2003r2 64bit os, currently running on Hyper-v.

    I'm a bit lost in regards to the questions posed.

    I did not get any options to specify which controller i want to use on the target.

    It was automatically set to "auto select" with Volume based cloning and "thick provisional disks" (there are three disks)

    I thought i did something wrong, so i deleted my vm and started from scratch to make sure of the settings and i cant change anything except for the size of the disks.

    Where do i find the .vmdk file you want me to have a look at ? (sorry, all this vmware is still very new to me)

    Thanks in advance.

    Etienne



  • 5.  RE: VM shows BSOD after P2V

    Posted Jan 20, 2013 12:11 PM

    I the converter wizard you have the option to modify the configuration. The controller type is shown when you select "Devices" in the left pane.

    Anyway, take a look at the VM's folder (using e.g. the Datastore Browser in ESXi). There you will find a .vmx file for the converted VM. Use the download icon and attach the file to your next reply post.

    André



  • 6.  RE: VM shows BSOD after P2V

    Posted Jan 21, 2013 06:14 AM

    Hi Andre'

    You are a star :-)

    I re-converted the vm again (this time paying close attantion to the "devices" tab, and i found the setting you were talking about.

    I set the controller as per your first post ( LSI Logic)

    The vm is now starting without any problems and all three of my disks are on scsi :smileycool:

    Thanks for taking the time to help, i really appreciate it.

    Regards

    Etienne



  • 7.  RE: VM shows BSOD after P2V

    Posted Jan 21, 2013 08:49 AM

    I have selected LSI Logic Parallel in the Converter Wizard. I also have tried Paravirtual and injected the drivers to the Conversion source, with no affect. VM still shows BSOD.



  • 8.  RE: VM shows BSOD after P2V

    Posted Jan 21, 2013 11:02 AM

    Hi pusha.

    Maybe you can do what Andre' suggested and attach the .vmdk to your next post.

    Unfortunately I would not be able to help you, but I am sure someone else will.

    Good luck.



  • 9.  RE: VM shows BSOD after P2V

    Posted Jan 25, 2013 12:07 PM

    I have checked the vmx and the vmdk file. They seem to be correct but i will post the content here, maybe i overlooked something.

    the vmdk:

    # Disk DescriptorFile

    version=1

    encoding="UTF-8"

    CID=5c718366

    parentCID=ffffffff

    isNativeSnapshot="no"

    createType="vmfs"

    # Extent description

    RW 62928896 VMFS "VM1-flat.vmdk"

    # The Disk Data Base

    #DDB

    ddb.geometry.biosHeads = "255"

    ddb.geometry.biosSectors = "63"

    ddb.geometry.biosCylinders = "3917"

    ddb.adapterType = "lsilogic"

    ddb.geometry.sectors = "63"

    ddb.geometry.heads = "255"

    ddb.geometry.cylinders = "3917"

    ddb.uuid = "60 00 C2 95 16 4e 7e d1-2a 87 dd 24 05 43 95 e0"

    ddb.longContentID = "1206edb349964af0266c9e005c718366"

    ddb.virtualHWVersion = "8"

    the vmx:

    .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 = "VM1.nvram"
    virtualHW.productCompatibility = "hosted"
    powerType.powerOff = "soft"
    powerType.powerOn = "hard"
    powerType.suspend = "hard"
    powerType.reset = "soft"
    displayName = "VM1"
    extendedConfigFile = "VM1.vmxf"
    scsi0.present = "TRUE"
    scsi0.sharedBus = "none"
    scsi0.virtualDev = "lsilogic"
    memsize = "512"
    scsi0:0.present = "TRUE"
    scsi0:0.fileName = "VM1.vmdk"
    scsi0:0.deviceType = "scsi-hardDisk"
    ide0:0.present = "TRUE"
    ide0:0.clientDevice = "TRUE"
    ide0:0.deviceType = "cdrom-raw"
    ide0:0.startConnected = "FALSE"
    guestOS = "winnetstandard"
    uuid.bios = "42 30 c6 07 96 2c 0b 70-ae 00 be a3 80 62 e2 ac"
    vc.uuid = "50 30 96 e1 37 be 97 ad-d8 72 37 e3 bd 5a 48 18"
    floppy0.present = "FALSE"
    scsi0.pciSlotNumber = "16"
    vmci0.id = "-2141003092"
    vmci0.pciSlotNumber = "32"
    uuid.location = "56 4d 08 5f 30 e0 66 8a-05 dd 30 e5 3e 0a 1d 9a"
    cleanShutdown = "TRUE"
    replay.supported = "FALSE"
    sched.swap.derivedName = "/vmfs/volumes/4addc79d-86c982d8-75c9-002481e3a414/VM1/VM1-ed703485.vswp"
    replay.filename = ""
    scsi0:0.redo = ""
    pciBridge0.pciSlotNumber = "17"
    pciBridge4.pciSlotNumber = "21"
    pciBridge5.pciSlotNumber = "22"
    pciBridge6.pciSlotNumber = "23"
    pciBridge7.pciSlotNumber = "24"
    hostCPUID.0 = "0000000b756e65476c65746e49656e69"
    hostCPUID.1 = "000106a500100800009ce3bdbfebfbff"
    hostCPUID.80000001 = "00000000000000000000000128100800"
    guestCPUID.0 = "0000000b756e65476c65746e49656e69"
    guestCPUID.1 = "000106a500010800809822010fabbbff"
    guestCPUID.80000001 = "00000000000000000000000128100800"
    userCPUID.0 = "0000000b756e65476c65746e49656e69"
    userCPUID.1 = "000106a500100800009822010fabbbff"
    userCPUID.80000001 = "00000000000000000000000128100800"
    evcCompatibilityMode = "FALSE"
    vmotion.checkpointFBSize = "4194304"
    softPowerOff = "FALSE"



  • 10.  RE: VM shows BSOD after P2V

    Posted Jan 25, 2013 07:27 PM

    The files seem to be ok. What you could try is to run the Converter again, but using the "Configure Machine" option this time for the converted VM.

    André