Posts made by bnorwood

@Sebastian-Roth The VM is set to Legacy bios with a Legacy Network adapter and virtual switch. It works with a physical laptop connecting, just not the VM.

@Sebastian-Roth I set my DHCP to the ipxe.kpxe and get this error.

Warning Using Legacy NIC wrapper on “MAC Address” Then sticks on IPXE initialising devices again.

Yes just a Hyper-V VM on the same server.

I had to update/reinstall my virtual Fog server running ubuntu 18.04.4 LTS on a Windows 2019 Server version 1809 build 17763.1217 running Hyper-V. I have a virtual pc with a windows 10 version 1909 build 18363.836 ready to upload to the Fog server. It sticks at the IPXE initialising devices spot and won’t go any further. I have tested with verifying all the usernames/passwords for the fog and fogproject accounts are correct. I have tried different Kernels, different dhcp setting with undionly.kpxe and undionly.kkpxe. I have verified my legacy Network Adapter and virtual switch are working. I can upload an image from a real pc without issues but can’t upload/connect from another virtual computer. Any suggestions would be appreciated. Thanks!

PS This was working fine a month ago with the same configuration.

This is what I get.

My setup is a Microsoft 2016 server running Hyper-V Manager 10.0.14393.0. I have two VMs. One is a FOG server 1.5.5 running on Ubuntu 18.04.2 LTS. The other VM is my machine I create/update images (Windows 10) to the FOG server. I am noticing that when capturing an image it is very slow. For a 32GB image it takes between 7-8 hours. The only thing I found on the forums indicated that the Legacy Network Adapter used in the FOG virtual switch only runs at 100MB even when connected to a 1GB NIC. Is there a way to fix this or use an actual NIC instead of the virtual switch manager? Any information is greatly appreciated!

@Sebastian-Roth The password error solved the capture issue. I have successfully captured the image. Thanks for the help! I will start another thread on the Hyper-V slowness issue.

@Sebastian-Roth From what I am reading it is an issue with the virtual switch manager using the Legacy Network Adapter only running at 100MB. That would account for the long capture time. The forum link didn’t address if there is a fix for this. I am using the Legacy Network Adapter as per the setup instructions. I have “real” NICs available but not sure how to use them instead of the Virtual Switch Manager. Thoughts?

I also reset all the username and passwords to match after seeing the error code. I think the storage one may have been bad.

Here are some screen shots at the end of the capture and errors.

Here is a screenshot of my Hyper V

@Sebastian-Roth I am running a Windows 2016 Server with 32 GB RAM and Xeon CPU E5-2640 @ 2.50 GHz. I have Hyper V loaded using manager 10.0.14393.0. I have two VMs set up. One is the FOG Server and the other VM is the machine I use to update/capture mages from. There is nothing else running on this server. I have the virtual switch manager running an external fog switch with a 1GB connection. Both the Fog server and client VM are running at 1 GB. I have them both set to 16GB Memory and 8 virtual processors. I only have the compression set to 4 in the Fog GUI. Not sure why it takes so long.

Here is my setting on the image.

Right now it is still running another try. They are taking about 7 hours.

I am running Ubuntu 18.04.2 LTS and FOG 1.5.5 and trying to do a basic image capture of a Windows 10 VM machine. The process starts like normal and everything looks good but after finishing the capture the Windows 10 VM restarts and the capture process starts all over again. I have let it run over the weekend and it never completes. In the FOG GUI under images, it shows the size but has an invalid date listed.

Under the tasks, it shows normal

Any help would be appreciated. Thanks!