Hello,

Didn’t know where else to turn. I’m having an issue capturing an image from a VM in proxmox (been doing this for years). Just noticed when I upgraded to the current stable fog version. I’m unsure if this is a proxmox issue or a fog kernel issue.

Context:
-I cannot capture an image on any devel kernel above v6.1.89 (tried all v6.6.x kernels available).
-I get a, assuming would be an early kernel panic, with the following text:

efi stub: measured intrid data into pcr 9

That’s it. The VM hangs indefinitely. Let it go for an hour or so. Weird thing is I was using the exact same kernel on v1.5.10 (minus the extra digits).

Now I can actually get fog to boot in a VM on the latest kernels if I disable “KVM hardware virtualization” on the VM but it is insanely slow. No joke like a crawl.

If anyone has any suggestions I’d greatly appreciate it.

Thanks!

Sorry to resurrect an old thread. I ran into this issue today and have found a resolution (at least in my case).

I had an image that was quite old that I wanted to update. The client I wanted to image was from a completely different system (a VM). I cloned over top the existing image with the VM. I got the same exact 504 error and it would eventually fail to update the database.

I created a new image in fog and assigned the new host that new image. Went through flawlessly.

It’s weird because I’ve done this in the past on multiple occasions and never had an issue. It was more than likely I created the older image (that I was just trying to clone over) on v1.5.9. I did update to v1.5.10 a couple months ago.

So if you have this same problem, try creating a new image if overwriting an old image fails with the 504 error.