ok, I managed to deploy the image…
Before attempting to update the kernal I noticed I could no longer deploy the old image I had restored yesterday. I deleted the Hyper V VM, recreated it then deployed my latest image and it worked.
All those errors from before are still visible over the blue and red progress screen. Howver, the newly restored vm won’t start.
Do I need to add the HyperV VM drivers to the original PC before trying to restore to a hyper V VM?
I have another image I took a while back that will deploy to the VM so somethings changed between than and yesterday when i took this latest image.
If I update the kernel I’ll have to capture the image again?
Hi,
I’m having problems deploying a windows image to a hyperv vm
Hyper-V Version : 6.1.7601.17514
Fog Version : 1.2.0
Source PC - Windows 7 32 bit
I’m sure I’ve done this successfully before but I’m getting the following in the log now…
tsc: Fast TSC calibration failed
piix4_smbbus 0000:00:07.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
BUG: using smp_processor_id() in preemptible [00000000] code: fdisk/2287
Looking for Hard Disks…BUG: using smp_processor_id() in preemptible [00000000] code: fogpartinfo/2428******
After that it says Task Completed and reboots, this all takes just a few seconds. I can deploy images I’ve captured previously to this VM so I suspect I’ve done something wrong when capturing this latest image.
When I try “service vsftpd status” I get Unknown job:vsftpd
I get the same when I try it on my other fog box which is working.
I had been using “service tftpd-hpa restart” to restart ftp previously.
I can ftp into the fog server from a windows PC, so it looks like it’s running.
Hi,
I just moved my fog server over to a VM. I’d already done it for our branch office and had no problems.
The server is running on the VM ok but I’m having problems moving the images over to the new server.
I copied the images over to \images and then created new images on the fog admin page making sure the paths point to the right place. On the other VM I setup the image sixe fields and upload date both populate. On this new Vm that’s not happening…image size is zero and uplaod date just says “no data”
I’ve checked the permissions, restarted mysql…no change. What have i forgotten? Thanks, Kev
I’ve sorted it. I was using a sata drive on various different models of PC around the office to confirm the image works with multiple models. I tried using a different drive and it worked fine, the drive I was using was only 80gb whereas the image came from a 250gb drive.
The windows installation on the image only takes up about 20gb, is this behaviour correct? Does the target drive need to be the same size or larger then the original?
ok, rebuilt fog on a brand new VM, I’m getting the same issue. I can’t think what else it could be…the DHCP options are the same as they’ve always been. Perhaps there’s something odd about these two particular PCs I’ve been testing with, I’ve been using them with fog for a while though. I’m going to dig out another couple of the same model…
ah, too late I removed FOG as per…[url]http://www.fogproject.org/wiki/index.php?title=Uninstall_FOG[/url]
Reinstalled, dragged my images back in…same problem. I’ll build a new vm as you suggest. Thanks very much for your prompt replies
No luck, ran the installer again, still the same issue. Can i remove it fog completey? I have my images backed up…
Yep it works ok, it get to the bottom line - saving MBR then starts partclone whereas the others just reboot.
Same thing happens if I try to deploy using the quick image option. I can deploy and capture from my dell e6400 but not to optiplex 3020 or HP dc7100.
It can’t be anything to do with the actual images as I can’t even capture a fresh image from these PCs.
The permissions are :
owner - root - create and delete
group - root - create and delete
others - create and delete
Hello.
Suddenly my pxe boot/imaging process seems to be failing.
I create a task in fog, reboot the PC, it starts the pxe boot and gets stuck for a while at init.xz or init_32.xz…eventually it starts pushing out the image but then reboots before the copying screen appears.(the blue screen with the red progress bars)
This is happening with all images but not with all models of PC, some seem to run ok.
Thanks very much for any advice, Kev