August 30, 201312 yr I was actually trying to combine my vSphere 5.1 and my UnRaid server this week into one box, with a huge Lian Li d8000 case. All looked great, I started finally moving my cards and drives over last night. I had VT-D passthrough on and finally figured out the trick to getting the UnRaid virtualized. About 5 minutes in I am greeted with a vSphere 5.1 PSOD, the dreaded PSOD. From decrypting their message it says something about time drift? I have had zero luck with VT-D in the past, it has always been flaky as crap. My CPU's are Xeon 2620, I think they are 6 core and I have two of them. I do not think where I put my memory in my board would cause this error could it? It has run for days with no PSOD until I fired up UnRaid with the passthrough. Lian Li 8000 Xeon 2620 x 2 ASRock EP2C602-4L/D16 Super Micro AOC-SASLP-MV8 x 2 (VT-D Passthrough) Purple Screen of death reads like PCPU 4: no heartbeat (2/2 IPIs received PCPU 0:ISSISISVIS.............................. *PCPU15:8208/idle16
August 30, 201312 yr The AOC-SASLP-MV8 requires the card hack (at least in ESXi) to get passthrough working with it.
August 30, 201312 yr Author Oh wow, I think it is fixed. I was about to give up and go a different route, you saved a ton of headache and time. I am going to start a thread soon since this is such a massive build, I want to document my experience. Thank you sooo much.
August 30, 201312 yr Haha had the same problem when I rebuilt my server and the mv hack was not valid (port # changed)
August 30, 201312 yr Author Haha had the same problem when I rebuilt my server and the mv hack was not valid (port # changed) But yours was fixed by just changing the port number in the VMX file, or did the problem persist? Was it the PSOD?
August 30, 201312 yr Haha had the same problem when I rebuilt my server and the mv hack was not valid (port # changed) But yours was fixed by just changing the port number in the VMX file, or did the problem persist? Was it the PSOD? Every time you add the SASLP-MV8 through to a VM you will have to do the VMX part of the HACK. When you delete the PCI card(SASLP-MV8) ESXi will delete the VMX edit from the file. You can however add the .msiEnabled = "FALSE" part of the hack through the GUI from vCenter web interface. You don't have to edit the VMX file directly. Don't have the instructions here at work that I wrote up so can't post them right now.
August 30, 201312 yr Haha had the same problem when I rebuilt my server and the mv hack was not valid (port # changed) But yours was fixed by just changing the port number in the VMX file, or did the problem persist? Was it the PSOD? Yes it was PSOD and it was fixed for good
August 30, 201312 yr Author Thank God.....I am at work remoted in staring at the screen thinking it will bomb out again, this is the longest it has run with VT-D turned on.
Archived
This topic is now archived and is closed to further replies.