KMV installation can not locate images folder upon image deploy or capture.

[lperoma]

Hi all,

I recently migrated FOG (1.5.9.220) to KVM environment with images folder shared from a folder in the bare metal host.

I worked fine for some time. The host were is worked fine went belly up some weeks ago.

Not a big deal, I had a backup of both the guest KVM and the images.

Migrated all to new HW, fired up, working straight away. I can see the images folder from the guest (again shared via virtio from host), I can even create a new image (to be captured) of delete an old image.

However upon deploy, I get a “No image files found that would match partition to be restored” . The files are there. I’m puzzled.

Upon capture, all seems to go fine but when it’s time to start capture, I’m presented with a menu with options ifconfig, gdisk, fdisk, fixparts, reboot. And no capture.

What am I missing ? Thanks a lot in advance

[lperoma]

Thanks @Sebastian-Roth

Disabling the debug mode gave me a tip on the problem, as capture stopped with a failed to set permissions error.

In the end, I ended up narrowed down the problem to the type of filesystem presented to FOG from the KVM.

I had:

<filesystem type='mount' accessmode='passthrough'>
  <driver type='virtiofs'/>
  <source dir='/images/'/>
  <target dir='ximages'/>
</filesystem>

This is not quite OK for FOG, needs to be a raw disk presented to the guest. I changed it to a raw disk with :

<disk type='block' device='disk'>
  <driver name='qemu' type='raw' cache='none'/>
  <source dev='/dev/disk/by-uuid/7c4cf625-18de-4bd8-852b-952b9bc7fdc5' index='1'/>
  <backingStore/>
  <target dev='vdb' bus='virtio'/>
  <alias name='virtio-disk1'/>
</disk>

And all worked just fine then. Looks like a /filesystem declaration is not a proper ext4 filesystem when mounting on the guest.

All is working fine now. Thank you all for your help.

[lperoma]

Update:

I was suspecting the images folder mount into the virtual machine. I have unmounted the filesystem, and now I have the local /images file (no images there).

I still can’t capture images, no apparent error given, just the options to : ifconfig, gdisk, fdisk, fixparts, reboot. But no capture.

No ideas ? Troubleshooting tips ?

[Sebastian Roth]

@lperoma May I ask you to take pictures of what you See on screen and post those here?

[lperoma]

@Sebastian-Roth Here you go:

https://naks.es/downloads/fog.mov

Hope this can clarify a bit.

[lperoma]

@Sebastian-Roth One more:

https://naks.es/downloads/fog-deploy.mov

Best, LP

[lperoma]

Hi @Sebastian-Roth did you have the chance to see those 2 videos for capture and deploy ?

We are a bit stuck. Yesterday I tried reinstalling fog to no avail.

[Sebastian Roth]

@lperoma said in KMV installation can not locate images folder upon image deploy or capture.:

did you have the chance to see those 2 videos for capture and deploy ?

Not yet but will take a look and reply today.

[lukebarone]

This post is deleted!

[Sebastian Roth]

@lperoma said in KMV installation can not locate images folder upon image deploy or capture.:

https://naks.es/downloads/fog.mov

In this video I see a capture task scheduled in debug mode. Just hit ENTER twice to get to the shell and start capturing by running the command fog. If you don’t want debug capture you should not enable the debug checkbox in the web UI when scheduling the capture task.

https://naks.es/downloads/fog-deploy.mov

This video shows a hanging deployment that seems to be waiting on post init scripts. Please check the following folders on your server to see what kind of scripts you have in place:

ls -al /images/dev/postinitscripts
cat /images/dev/postinitscripts/fog.postinit
ls -al /images/postinitscripts
cat /images/postinitscripts/fog.postinit

Yesterday I tried reinstalling fog to no avail.

Do you still get the exact same error message mentioned in your initial post? I am wondering why we don’t see this in the video.

[lperoma]

Thanks @Sebastian-Roth

Disabling the debug mode gave me a tip on the problem, as capture stopped with a failed to set permissions error.

In the end, I ended up narrowed down the problem to the type of filesystem presented to FOG from the KVM.

I had:

<filesystem type='mount' accessmode='passthrough'>
  <driver type='virtiofs'/>
  <source dir='/images/'/>
  <target dir='ximages'/>
</filesystem>

This is not quite OK for FOG, needs to be a raw disk presented to the guest. I changed it to a raw disk with :

<disk type='block' device='disk'>
  <driver name='qemu' type='raw' cache='none'/>
  <source dev='/dev/disk/by-uuid/7c4cf625-18de-4bd8-852b-952b9bc7fdc5' index='1'/>
  <backingStore/>
  <target dev='vdb' bus='virtio'/>
  <alias name='virtio-disk1'/>
</disk>

And all worked just fine then. Looks like a /filesystem declaration is not a proper ext4 filesystem when mounting on the guest.

All is working fine now. Thank you all for your help.

[Sebastian Roth]

@lperoma Thanks for the update. Good to hear you found this and were able to fix it. Well done! This is beyond FOG itself and it would have taken a lot of posting forth and back to figure this out for us. Although I don’t know much about virtiofs I can imagine it causing problems when being exported as NFS (as FOG does).