locked
hyper-v Try to PXE boot. RRS feed

  • Question

  • Im currently running Hyper-v core, and want to PXE boot aan image from a Provisioning server, the image boot's (server 2003 standard with citrix 4.0) but after a couple of seconds a blue screens appears with the code: 0x0000007b

    So i searched the internet for a solution, and foud several thiings, like adding IDE device to the VHD, but it does not work for me.
    Any help would be appreciated!

    Kind regards,

    Martijn Kootstra

    Friday, January 14, 2011 11:07 AM

Answers

  • a stop 7B is a critical boot device error.

    How did you create the image that you are streaming from Provisioning server?

    If the image was built from a system that used SCSI disks (either physical or a VM on ESX server) then yes, you need to modify the critical boot devices and switch them to IDE.

    Did you use XenConvert to create the PVS image?

    BTW - considering that you are getting to a stop 7B error - this is not a problem with Provisioning server, nor a problem with Hyper-V - but rather a problem rooted in the image itself.

     

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    • Marked as answer by Vincent Hu Wednesday, January 19, 2011 8:14 AM
    Friday, January 14, 2011 3:38 PM
  • Hi,

     

    I agree with BrianEh, it seems that there are some issue with the image itself.

     

    By the way, in order to narrow down the cause the issue, you can boot the VM with a ISO file on the Hyper-V computer to see whether you get the same issue.

     

    In addition, the following post discussed a similar issue, you can refer to:

     

    Fresh WinXP SP3 install in VM: Bluescreen after reboot

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/0f5ca3e1-2142-45ac-b036-09ba0f6497b0

     

     

    Best Regards,

    Vincent Hu

     

    • Marked as answer by Vincent Hu Wednesday, January 19, 2011 8:15 AM
    Monday, January 17, 2011 9:07 AM

All replies

  • a stop 7B is a critical boot device error.

    How did you create the image that you are streaming from Provisioning server?

    If the image was built from a system that used SCSI disks (either physical or a VM on ESX server) then yes, you need to modify the critical boot devices and switch them to IDE.

    Did you use XenConvert to create the PVS image?

    BTW - considering that you are getting to a stop 7B error - this is not a problem with Provisioning server, nor a problem with Hyper-V - but rather a problem rooted in the image itself.

     

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    • Marked as answer by Vincent Hu Wednesday, January 19, 2011 8:14 AM
    Friday, January 14, 2011 3:38 PM
  • Hi Brian,

     

    Thanks for your reply.

     

    I have no idea how the image was created, It's running since it was called ardence, and updated to provisioning server 5.0.

    The thing is, when i attach the VHD directly to the hyper v as a disk it boot's fine. and the same image is on the provisionig server, and when i want to boot the vm with pxe (streamed from the provis server) i'm getting the 7B error.

    Any idea how i can fix this?

     

    Thanks,

    Martijn

    Friday, January 14, 2011 8:27 PM
  • pop over to the citrix forums you will get your best help there.

    a quick search ( http://tinyurl.com/4vpqhbe ) gave me the following and I have a feeling that your answer might be here..

    http://forums.citrix.com/message.jspa?messageID=1339805

    http://forums.citrix.com/thread.jspa?messageID=1428292

    http://support.citrix.com/article/ctx119129

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Friday, January 14, 2011 10:05 PM
  • Hi,

     

    I agree with BrianEh, it seems that there are some issue with the image itself.

     

    By the way, in order to narrow down the cause the issue, you can boot the VM with a ISO file on the Hyper-V computer to see whether you get the same issue.

     

    In addition, the following post discussed a similar issue, you can refer to:

     

    Fresh WinXP SP3 install in VM: Bluescreen after reboot

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/0f5ca3e1-2142-45ac-b036-09ba0f6497b0

     

     

    Best Regards,

    Vincent Hu

     

    • Marked as answer by Vincent Hu Wednesday, January 19, 2011 8:15 AM
    Monday, January 17, 2011 9:07 AM
  • Personally, you might need to boot the image as a Hyper-V VM and then unintall and re-install teh Provisioning Server tools into the VM.

    It sounds as if the Provisioning Server driver is not initializing properly.


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Monday, January 17, 2011 3:14 PM