@Preston Wow that was a super answer, thanks Preston! I’ll give this a go in the week. 🙂

@Exsival When you say “Causing the fog server to crash” what exactly do you mean?

If it’s just a “saying” I can understand that but from a technical standpoint what this means is completely different and would need logs. If all you mean is the machine in quesiton is hanging, that’s a different issue altogether. I highly doubt the whole FOG Server is crashing.

@Infojoe I forgot an important information : version 1.5.10.1826

@kratkale said in Windows 11 | 65x HP Z2 Tower G1i:

Can I specify in FOG which hard drive to clone to? For example, using the serial number? That could be stored in the host entry

Hi, this is a known issue when using NVMe, as you’ve probably already discovered. I’m not sure whether FOG 1.5 supports using serial numbers to target disks, but someone from the team may be able to confirm that. FOG 1.6, however, does support targeting disks by serial number.

I ran into the same situation. As a workaround, I customized my init.xz to use the PCI path instead, since those appear to be more persistent.

@rodluz I tried a manual installation of the updated init.xz as outlined in your instructions, and there was no change. I also upgraded my FOG server and reinstalled your experimental XCP bzImage from earlier in this thread but did not see any change in VM behavior after doing so.

Out of curiosity, @BPSTravis, what hardware are you running XCP-ng on? I know it’s virtualized, but maybe there’s some CPU feature I have disabled in BIOS on my XCP hosts or something like that?

Also, thanks for your patience. I’m only available to work on this once or twice in the middle of the week as I’m part-time with this organization.

@Tom-Elliott Hi, has there been any development with this?

I’m facing a situation that’s not quite identical but very similar in my 1.6.0-beta.2297.

I already posted to the Forum with the details I thought were relevant, but noticed my FOG status is showing the same messages that are posted here.

@lucasgfaj have you turned off secure boot?

@Tom-Elliott
I did not update yet to 1824, but i did SELECT * FROM HISTORY;

MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 1 row in set (0.000 sec)

the new session i create are not shown, and dont work until i run the maintenance queries

then it shows in history table:

MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | | 2 | [2026-04-01 09:10:37] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 09:10:37 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 2 rows in set (0.000 sec)

@devle I’ve made a couple of edits, though I still cannot replicate the problem you’re seeing.

You shouldn’t see the errors any more (just saying), though I don’t know if these things will fix whatever problem you’re seeing.

@Tom-Elliott All good the last update fixed the issue!

@BLT I don’t necessarily have a timeline for the final release but I did just release an experimental kernel with a newer nic driver. It may work for you if you want to give it a try.