MP Bios bug 8254 timer not connect to IO APIC

[Blrvenky]

I have setup Fog server on Virtualbox ( ver 6.1), windows server VM 2016 for DHCP and Windows 10 VM.

When Windows 10 VM boots to network pxe boot, dhcp assign the IP, then it come up the screen host not registered.
then choose to Perform full host registration and inventory,

I see this error comes up

[Blrvenky]

Moved the VM’s to different Laptop, problems got resolved.
I think the Processor was not compatible to run VM’s i think.

Also one problem i find is enabling EFI mode in virtual box always throws error
Works fine without EFI mode.

Also in dhcp service enable the policy as Fog suggestions.
Now Overall Fog server setup completed. Successfully deployed images to all models of Laptops.

Thank you

[george1421]

@sebastian-roth said in MP Bios bug 8254 timer not connect to IO APIC:

I think the kernel arg should be noapic, right?

Yes, it sure is. I guess I can’t read what was before my eyes. Sorry.

[Sebastian Roth]

@george1421 I think the kernel arg should be noapic, right?

[george1421]

@blrvenky I haven’t seen this issue before with VB. But I also haven’t use VB since I switched to Proxmox in my home lab. It must be a nuance with VB in your environment.

So the first step is to make sure you are running the latest FOS Linux kernel (the software that threw these error messages) You can get the latest kernel in the FOG Web UI -> FOG Configuration -> Kernel update.

Make sure you are running the 5.10.x version of FOG Linux. Download both the 32 bit and 64 bit versions. Then try to register it again.

If that doesn’t work then go into the FOG UI -> FOG Configuration -> FOG Settings hit the expand all button and then search for “KERNEL ARGS” in that field enter what it says noapc and save it. Understand this is just a temp fix to help you boot into FOG. Normally this setting should not exist, but to get you going we can put it there globally. Once you get the VM registered then you can go into the host definition and put noapc in the kernel args there and then remove it from the global setting.