@olivierlambert Congrats you guys are expanding!

Always have appreciated everyone help here and a great community of users.

@stormi after the update it seem to work well for me. Well the update from edk2 at least is working now. Haven't tried the iso.

Hello all,

Not sure it this is something specific to this update on (8.3beta 12/21/2023 release update) or not but did anyone else run into pfsense 2.7.1 having the VM not doing the autoboot countdown on startup screen after update? Apparently my node has this problem. I have to manually press the enter button to continue from startup screen...

Unless I accidently change the console keyboard from XOA setting somehow? I always use SSH to do all my stuff but if there is anyway to type in directly from console would be nicer

Screen it is stuck on until enter is pressed.

Reason i suspect it is XCP-ng is because there was no change before xcp-ng update (8.3beta 12/21/2023 release update) and when i revert vm to older version of the snapshot it has same problem. Really weird...

FYI all other VM didn't have this problem as they autoboot up normally.

@lkernan Ahh ic let me double check. Thanks hopefully that is the case.

Ok the linked partner was the issue. Thanks for clarifying that issue makes total sense now

Wow this great news and amazing work!!!

@stormi
Good things I notice on the new beta2-test3 iso:

• "efi: EFI_MEMMAP is not enabled" used to take minutes is now down to 30 sec
• host joins other host or pool really quickly (it sometime takes forever or doesn't work for me before until I manually toggle disconnect and reconnect) (hosts in pool always work fine but hosts from different pool was slow previously not sure why when they all start up at the same time is usually the issue especially when network is up slower than the hosts. I assume host search timeout before network is up.)
• UEFI is definitely fixed now

All good feedback. No drawback yet.

Also when is NFS v4 available believe it was end of 1st quarter (March???) from what i heard is that still true?

Thanks otherwise it is good on my short test so far.

@exetico it didnt break for me lol and all 4 of my xcp-ng and multiple pfsense VMs

@Pilow my is SMB too but it saw the issue. I use windows to login and drag all iso into a new created folder in the iso folder and drag it back out delete the newly created folder and all my iso is back to normal. It was a quick thing.

@Pilow Check the iso does it have a snapshot icon in the drive?

Next it show up fine until u want to create a vm in the new vm pg it think they are snapshots and you cant select the ISOs. This is when the problem arise.

Yep the dev here are super reaponsive. Have been a long term user and here and love their support . I mostly just been playing with things and learn so much by tinkering

@Pilow now that you mention that everything is seen as snapshot i remember all my ISO are seen as snapshots too... so most iso cannot be mounted until i drag them in a folder then put them back in same folder so XO could reprocess all the iso correctly. This might be a related issue to all the snapshots for the VMs.

@Pilow Lol glad I was able to help. Its only if you have a few VMs having hundreds will be a nightmare... giod luck to those that has that issue. In the meantime I will use the method I mention for now.

@Pilow Does disk show up after you do the snapshot? If it is able to do the snapshot there is a high chance it can boot up. So try booting up (and check for disk) and shut it down and do the snapshot at that time if the disk show up.

It helps to boot up on the old v5 commit and check from that side too if you have both copy before the commit update.

Yep I can confirm that snapshot doesn't always work. But using the older v5 that used to work before the update does get it showing up on the newer v5 commit if I go through whole snapshot, revert, etc. one of those case work.

It will be a nightmare if I have to do all 286 VMs...

slowing verifying if its going down the countdown... luckily most of them are related so it's not too bad.

Hello All,

Found some roundabout solutions you may want to try:
https://xcp-ng.org/forum/post/101370

So far a few solutions for me has been:

• Revert the SNAPSHOT and it magically find the disk...
• Create a new SNAPSHOT and it magically find the disk... (esp. if you don't have a snapshot on some VMs like me)
• SNAPSHOT sometime works but still missing disk so boot it up and disk show up
• Some claim migrating the VM works... (migration fail for me as it can't find the disk lol...)

There should be better solutions as sometime I want to keep old snapshots. Still testing other methods... as my old XO still finds everything... even though its loaded with the same CONFIG FILES and same XCP-ng machine metadata.

@Pilow Ok I can confirm that this is extremely like this issue with the disks disappearing but still boot up and run fine lol

No disk on XO v5

Disk show up on v6

Fixed it by REVERTING the SNAPSHOT....

Seem others was able to migrate the VM out and back in to fix it as well which seem ridiculously time consuming lol . I might try that for those that have no snapshot as its a lost cost...

I think I am going to try wiping out everything and do a clean install and see what happen but will take a bit of time and report back...