Jump to content


Photo

2012R2 BSOD when booting from another server CvhdMp.Sys

Started by Marco Zimmermann , 13 March 2017 - 11:31 AM
6 replies to this topic

Marco Zimmermann Members

Marco Zimmermann
  • 403 posts

Posted 13 March 2017 - 11:31 AM

Hi,

 

just installed a Server 2012 R2 Update 1 [SRV01] from scratch.

Installed PVS 7.6 CU3 (7.6.4) target device software (nothing else)

Backend: PVS 7.6 CU2

All is running on vSphere 6.0

 

Converted to vDisk.

 

vDisk boots in standard and private mode on SRV01 without an issue

However assigning vdisk to another server SRV02 (that is hw identical) I get a BSOD (see attached picture) in standard and private mode.

 

There are no ghost NICs in my image.

 

Any idea?

Marco

 

 

Attached Thumbnails

  • bnistack.PNG


Carl Fallis Citrix Employees

Carl Fallis
  • 984 posts

Posted 17 March 2017 - 03:33 PM

 Any chance you can get a crash dump?   So this crashing fairly early, I would suggest getting a network trace and  turning on target debugging (though it may not be that useful since this is early but we hopefully will see just how early it is with the network trace)

 

Carl



George Spiers Members

George Spiers
  • 215 posts

Posted 18 March 2017 - 11:11 AM

I hope you are using a VMXNET3 NIC on your Target Devices?

 

Have you read http://www.jgspiers.com/0x0000007e-bnistack-failed-vmware/

Since you mention that no ghost NICs are on the image, skip to the second part and check the ethernet pci slot numbers.



Marco Zimmermann Members

Marco Zimmermann
  • 403 posts

Posted 20 March 2017 - 12:45 PM

Hi all,

 

George thank you for this article - I haven't checked the slot numbers.. my bad :(

They were different - so editing them solved the issue.

 

However is it possible to change them without doing a reconvert?

 

Marco



George Spiers Members

George Spiers
  • 215 posts

Posted 20 March 2017 - 02:28 PM

You can change them like I had mentioned in the post, either by directly editing the .vmx file or using the vSphere console and going in to the Configuration Parameters

 

Also change the slot number on your VM template, so new machines you deploy will not be affected



Marco Zimmermann Members

Marco Zimmermann
  • 403 posts

Posted 20 March 2017 - 03:33 PM

Yeah, thatΒ΄s clear. But I got an old vDisk with eth0 168 and the new created with 192.

I want to use both in my environment, so I think the only way is to recreate the 2nd one with 168 or?



George Spiers Members

George Spiers
  • 215 posts

Posted 20 March 2017 - 08:31 PM

You could have one VM Template for the old vDisk, and a second for the new. Each VM template will have the correct slot number, either 192 or 168.

 

Or you could try booting the gold image machine up after changing it's slot number to 168, then run the Imaging Wizard again