Running Fog and other machines in virtualized environment, but cannot make capture work
-
In order to try to test out Fog, I set up a set of virtual machines in order to keep them in a quarantined environment, and not risk affecting production machines. I am using Hyper-V for this and have created a basic Windows 10 Gold Copy on a VM that I am now trying to capture with Fog.
Unfortunately, after resolving various issues around this and getting to the point where the VM will boot over PXE, I am getting an error.
At the top of the output there is a FATAL PCI: error complaining that no config space function is found. It then goes on, through the various checks and errors out on the partition table. It says “Reading partition tables”#######################################
An error has been detected
############################################
I am thinking the partition table error might be related to the PCI error above, but as I am new to Fog I need some help here.
I appreciate any help you can give.
Thank you,
Dave -
On this host item, remove the C:\ from the host device line and restart the machine.
From the GUI -> Host List -> Win10-Gold -> Host Device, delete c:\ and save. You may need to cancel and recreate the task.
-
@davemccracken Please take pictures of the errors on screen and post those here.
-
Okay, I’ve got the pictures
1st error
and 2nd
-
@Sebastian-Roth I neglected to put that in the previous post, sorry
-
@davemccracken So does it just stop at the attempting to check in?
What is the IP address of the FOG server? Has it changed since FOG was installed?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421 No, it hasn’t changed. It is 192.168.0.5. DHCP on a Windows 2012r2 server (to mimic the way it is set up for our prod environment) is 0.1, forwarding server to provide internet access is 0.2 (also windows) DHCP starts handing out at 0.101. The Gold Image VM is 0.112.
-
@george1421 said in Running Fog and other machines in virtualized environment, but cannot make capture work:
So does it just stop at the attempting to check in?
Ok so everything is on the same subnet and from what I see in the screen shots its working as it should. Does it ever throw an error screen?
-
@george1421 Unfortunately not. It seems I made an error and posted the same screenshot twice. This one shows the second error, which then causes it to reboot.
-
On this host item, remove the C:\ from the host device line and restart the machine.
From the GUI -> Host List -> Win10-Gold -> Host Device, delete c:\ and save. You may need to cancel and recreate the task.
-
@davemccracken Ok THAT is the error screen we were looking for. Please follow Tom’s guidance on removing the
drive reference. You have to remember that FOS is linux based, so it has no concept of a drive. Only drives and partitions as they are known to linux will be accepted. -
-
@davemccracken I am really wondering - who did set
C:\as Host Device?? -
@Sebastian-Roth I must confess I did it. It was my first attempt at anything with Fog and describing a windows host, I used windows nomenclature. I was not considering that PXE boot would boot Linux. I know how Linux represents devices, but… Call it a faux pas.
-
@davemccracken no harm no foul man. I am learning linux facts every day and I have been a FOG user for about 6-7 years. Many a time I find myself googling how the heck to do something still. Far from a master here.
-
@davemccracken Not pointing at anyone here! Just good you know how it happened and it’s not something out of the blue or “FOG messed up”!
