wimboot & multicore on esx issues
|
2014-12-03, 16:55
(This post was last modified: 2014-12-03 17:03 by thild.)
Post: #7
|
|||
|
|||
RE: wimboot & multicore on esx issues
(2014-11-12 12:27)mijanek Wrote: What kind of storage are you assigning to the guest? It should be the LSI SAS storage. This is working fine in our environment. However we are booting form PXE using microsoft bootstrap. Hi Mijanek, thanks for the tip. In fact I am already using 'LSI SAS Storage' as the storage controller so the problem lies probably somewhere else. (2014-12-03 16:19)robinsmidsrod Wrote: You might need to attach a debugger (windbg) to WinPE to figure out exactly what is going on during installation. Then you might be able to figure out what is causing the access violation. Knowing where it happens is the first part in solving it. I would recommend you join the developers on IRC and try to debug it in realtime. Hi Robin, thanks for the recommendation. I will try windbg as soon as I get some spare time. I guess I will need to modify the BCD store to ensure that the booted WinPE can be debugged through a serial link (not sure how this should work from an ESX guest). |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
wimboot & multicore on esx issues - thild - 2014-09-30, 17:12
RE: wimboot & multicore on esx issues - thild - 2014-10-22, 16:20
RE: wimboot & multicore on esx issues - mcb30 - 2014-11-07, 11:45
RE: wimboot & multicore on esx issues - thild - 2014-11-12, 11:42
RE: wimboot & multicore on esx issues - mijanek - 2014-11-12, 12:27
RE: wimboot & multicore on esx issues - thild - 2014-12-03 16:55
RE: wimboot & multicore on esx issues - robinsmidsrod - 2014-12-03, 16:19
RE: wimboot & multicore on esx issues - danberk - 2015-01-31, 01:24
RE: wimboot & multicore on esx issues - danberk - 2015-01-31, 02:31
|
User(s) browsing this thread: 1 Guest(s)