I think the usual stuff: https://docs.xcp-ng.org/troubleshooting/log-files/

No it shouldn't. Have you removed the passthrough from the VM too? Without logs it's hard to tell, take a look inside if you can spot something

Are you sure your OS (TrueNAS) isn't waiting for the PCI device that's not passed through anymore?

Is it possible to tell us more about the need? Maybe it could help us to think about something on our side

We could probably make the doc even more precise. Adding @thomas-dkmt in the loop for that.

Yes but why it works with some and not others. I suspect the firmware version in the NIC itself.

Hmm it doesn't ring a bell to me. I would suggest to open a ticket in parallel so someone could take a look on next week

Hi,

Are you using QCOW2?

Exactly and that's what does the Rolling Pool Update feature

But how one could check the integrity of a few blocks without context of the parent?

If I remember some previous discussions, EVE-ng uses some features that doesn't work in nested mode with Xen.

Adding @florent and @bastien-nollet in the loop for reading those ideas on better reports and proxy automation on assignation.

We are not energy efficiency experts, while EasyVirt people are. I think they already have some stuff and it might be just a matter of plumbing.

This will be likely handled by EasyVirt I suppose. Thanks for posting your idea!

You cannot share the same LUN between different pools (butyou can share the same SAN with different LUNs)

1. Yes you can
2. All VMs booted after the join won't use the most recent CPU features that you don't have on your old CPUs.

The only trick is for previously existing VMs with recent CPU: you need to shutdown then start then again to be sure they aren't using those features (features are applied on boot). So it's doable, but both options are possible.

Thanks!

@anthoineb or someone from the @team-storage, you might want to take a look (IDK if it's a known problem internally)

@Pilow Thanks, it's promising but we'll wait for more runs on your side If it's that, at least it's not a biggie in the end!

Hi,

Adding a VIF is like plugging "live" a new network card in a physical system. It's still up to your operating system to handle it. XCP-ng doesn't know what's inside a VM, it's up to the VM OS to do what it has to do (like on a regular physical hardware system).