Cannot fog Windows7 to VirtualBox on either Windows or Linux with image that works to bare metal

[DrT]

Trying all day to fog a Windows7 image to a virtualbox VM. It registers, and when downloading the image (which works on several bare metal machines) the guest machine during net boot gives a couple of diagnostic messages following /init.xz…ok
tsc: Fast calibration failed
piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr

Then it blanks the screen, shows the FOG ascii art display, and checks stuff:

• Checking Operating System … … Windows 7
• Checking CPU Cores … … 3
  …
• Database updated!
• Task is completed, computer will now restart.

Then the task disappears from the fog console about the time this virtual machine goes into a loop where reboots :
iPXE (PCI 00:0D.0) starting execution… ok
iPXE initializing devices… ok
…
DHCP (net0 …) …
(clear screen)
iPXE initialising devices…ok
…
Configuring (net0 … ) . . . . …
(clears the screen again)
iPXE (PCI 00:0D.0) starting execution…ok
iPXE initializing devices… ok
…

Anyone familiar with this problem? Is it related to the “tsc: Fast calibration failed” and "piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr" ?

We’re following: https://www.youtube.com/watch?v=Si3kMajqXbE
Complete Fog Imaging server Tutorial using Virtualbox 4.2.4 and cloning windows 7

I tried downloading to various versions of VirtualBox running on WIndows or Linux Mint. On Windows, the 4.2.4 version was not available but I tried the previous and next available versions, in addition to version 5, with no different results, and on linux mint I’m running version 4.3.18_Ubuntu 496516.

Any ideas?

[Wayne Workman]

I see the “tsc: Fast calibration failed” Every time Linux boots inside of Hyper-V. This isn’t your issue.

What version of FOG are you using? This video is using FOG 0.32 which is very obsolete.

What is your end-goal with FOG? We might be able to provide you instructions that are much more simplified than what this hour long YouTube video might have.

[DrT]

My system administrator fogged a common windows7 setup to all of the machines in our lab, and I want a copy of the same configuration running on a VM in my office. I run Linux Mint 17.2 in my office. The fog that our system administrator is using to do this is 1.2.0, running on the xubuntu 14.04. He was unable to fog to a VirtualBox machine running on a bare metal machine that had been fogged successfully. I’m running VirtualBox5.0 now and have had reports in the past few days that the tutorial works fine between virtual machines as in the tutorial with VirtualBox5.0 and the same fog that we use. We also tried with the closest versions of VirtualBox available to the video (the prior and next releases available at virtualbox.org) since the exact version number was not listed for download. I also tried fogging directly to a virtualbox 4.3.18_Ubuntu_496516 on my Linux Mint 17.2 (that is the current version for Mint 17.2).

[Ray F]

Hello, any updates to this? I’m trying to deploy a Win7 OS from a physical machine to a VM hosted via Virtual box. My fog server is also kubuntu inside Hyper-V at Windows 2012 server.

Issue is, The virtual box manages to get to the fog server-- but shows this error posted above and reboots in less than 15 secs. The task manager then deletes the task- thinking its complete. Ive looked around someone and no solution Im using the latest fog version.

Thanks for any help.

[Ray F]

@Wayne-Workman Hello, any updates to this? I’m trying to deploy a Win764 OS from a physical machine to a VM hosted via Virtual box. My fog server is also on kubuntu inside Hyper-V at Windows 2012 server.

Issue is, The virtual box VM manages to get to the fog server-- but shows this error posted above and reboots in less than 15 secs. The task manager then deletes the task- thinking its complete. Ive looked around someone and no solution Im using the latest fog version.

Thanks for any help.

[Tom Elliott]

What is the issue you’re seeing? You’re describing things but there’s no representation of the actual problem. Based on the information that is given, it sounds to me like the bare metal hard drive size is larger than the vbox hd is. What happens in this type of scenario is the mbr writes to the disk but partitions are completely unable to be used because there outside the scope the actual hdd can use. This presents problems where the imaging system doesn’t even know anything about the partition it’s trying to write to. So it continues to the next and so forth until there is no more data to try writing. This can happen very fast.

[Tom Elliott]

Think of it this way.

It’s like trying to fit a quarter through a dime sized hole.

There are ways you can force the quarter through, but most times it’s simply just not going to happen.