Virtualbox Homelab

[soulreaper11207]

So I built me a virtualbox lab to freshen up on Sysadmin skill. 

Currant setup:

Running three VM

    Windows 2019 that has WDS, DCHP, and AD installed and configured (to a point)

    pfSence acting as the router between my physical LAN and my virtual..

    To be Windows 10 client machine being deployed from WDS.

I end up getting the configuration to pxe the client VM, but it hangs on the Blue Windows logo, and then give me a BSOD with a HAL INITALIZATION error.

Oh and the boot and install wim's are pulls from a generic Windows 10 x64 iso.

I'm I missing something? I watched plenty of youtube how to's and the configurations are basically the same as they were back on 2008 server. 

[Electronics Wizardy]

Try using a different hypervisor, so hyper-v or kvm depending on platform

 

When do you get this bsod in the boot process?

[Malice Techen]

18 hours ago, soulreaper11207 said:

So I built me a virtualbox lab to freshen up on Sysadmin skill. 

Currant setup:

Running three VM

    Windows 2019 that has WDS, DCHP, and AD installed and configured (to a point)

    pfSence acting as the router between my physical LAN and my virtual..

    To be Windows 10 client machine being deployed from WDS.

I end up getting the configuration to pxe the client VM, but it hangs on the Blue Windows logo, and then give me a BSOD with a HAL INITALIZATION error.

Oh and the boot and install wim's are pulls from a generic Windows 10 x64 iso.

I'm I missing something? I watched plenty of youtube how to's and the configurations are basically the same as they were back on 2008 server. 

If you have a spare Box load XCP-NG or other hypervisor like @Electronics Wizardy suggested as it may play nicer on a different hardware box; unless you are trying to keep it down to one running computer which I can see. As running less hardware then needed has its upsides as well.

 

[soulreaper11207]

On 9/11/2019 at 6:03 PM, Electronics Wizardy said:

Try using a different hypervisor, so hyper-v or kvm depending on platform

 

When do you get this bsod in the boot process?

I got the bsod when using WDS to deploy to another VM. It loads the boot.wim over the network, loads up the black screen with at blue windows symbol, and then after 5 mins I get that BSOD. Do I need to build a drivers store? I tried using HyperV, but I had video driver issues after installing it. You have to remove all video drivers before installing it. So thats a no go. I am planning on buying another machine to host the lab, but I gotta pay bills first lol. 

 

[Electronics Wizardy]

7 hours ago, soulreaper11207 said:

I got the bsod when using WDS to deploy to another VM. It loads the boot.wim over the network, loads up the black screen with at blue windows symbol, and then after 5 mins I get that BSOD. Do I need to build a drivers store? I tried using HyperV, but I had video driver issues after installing it. You have to remove all video drivers before installing it. So thats a no go. I am planning on buying another machine to host the lab, but I gotta pay bills first lol. 

 

What video driver issues do you get in hyper-v? That should work fine when I tested it.

[Sir Asvald]

On 9/13/2019 at 3:07 PM, soulreaper11207 said:

I got the bsod when using WDS to deploy to another VM. It loads the boot.wim over the network, loads up the black screen with at blue windows symbol, and then after 5 mins I get that BSOD. Do I need to build a drivers store? I tried using HyperV, but I had video driver issues after installing it. You have to remove all video drivers before installing it. So thats a no go. I am planning on buying another machine to host the lab, but I gotta pay bills first lol. 

 

I use WDS for LiteTouch iso boot and use MDT for the the installation. 

[soulreaper11207]

On 9/13/2019 at 5:29 PM, Electronics Wizardy said:

What video driver issues do you get in hyper-v? That should work fine when I tested it.

Running a gtx 1060 6gb. I even tried uninstalling them and installing the Hyper-V with the generic ms video driver. Probably just end up buying a cheap machine, transfer the servers over, and call it a day. Seems like virtualbox has plenty of issues with trying to image deploy over it's internal network. Thanks for the help though guys

[Electronics Wizardy]

23 minutes ago, soulreaper11207 said:

Running a gtx 1060 6gb. I even tried uninstalling them and installing the Hyper-V with the generic ms video driver. Probably just end up buying a cheap machine, transfer the servers over, and call it a day. Seems like virtualbox has plenty of issues with trying to image deploy over it's internal network. Thanks for the help though guys

Are you trying to do passthough of the gpu in hyper-v or do the vgpu?

 

Normally don't view the image from the vm in the virtual machine software, use rdp or ssh to manage vms.

[paddy-stone]

On 9/11/2019 at 10:15 PM, soulreaper11207 said:

So I built me a virtualbox lab to freshen up on Sysadmin skill. 

Currant setup:

Running three VM

    Windows 2019 that has WDS, DCHP, and AD installed and configured (to a point)

    pfSence acting as the router between my physical LAN and my virtual..

    To be Windows 10 client machine being deployed from WDS.

I end up getting the configuration to pxe the client VM, but it hangs on the Blue Windows logo, and then give me a BSOD with a HAL INITALIZATION error.

Oh and the boot and install wim's are pulls from a generic Windows 10 x64 iso.

I'm I missing something? I watched plenty of youtube how to's and the configurations are basically the same as they were back on 2008 server. 

Could it be that the typo in your settings file location is the problem?  it says "vitural machines" when it should be virtual. I don't know about this stuff just to be clear, but I noticed the typo