@MathieuRA Thanks for doing the fix, I have tested this and I confirm it is working. I am able to migrate VMGuest to a different host by ticking the check box in the vmlist. [image: 1709761883728-29d4f92f-f074-488d-b2b3-27b74c2e0ae4-image.png] [image: 1709761905422-0b61a637-4dac-41a4-9aba-ba7c6db85c8b-image.png]

@olivierlambert Oh, I misread the documentation. Thanks anyway for answering my question.

@dinhngtu said in Windows VMGuest changing network cause the guest to crash: This is a driver bug that we fixed in XCP-ng Windows tools v9.0.9030 but hasn't been integrated by Citrix yet. You can try it out if you're not running a production system. Gosh, we are now officially faster than Citrix to detect and fix bugs even in the Windows PV driver

@splastunov I realize this thread is old, but I think there is important info to keep connected to this thread for future readers. The IP locking trick doesn't seem to prevent all traffic -- it only prevents traffic that has an IP that isn't 255.255.255.255 (and possibly others as well). That is, I can still successfully acquire a DHCP IP even when the IP locking mechanism is engaged. I think this is important for others to know since it doesn't fully isolate VMs like the OP wanted. UPDATE: Setting the locking mode to "disabled" is what you want -- not "locked". Disabled will drop all traffic; locked simply checks if the set of IPs in the VM is permitted. Source: https://docs.xenserver.com/en-us/citrix-hypervisor/networking/manage.html#vif-locking-mode-states

@olivierlambert I do not understand wha t you mean by "You probably need to transform the disk in a "regular" and not snapshot". Not sure on how to do that, please provide the steps or if you have SOP ready, please point me to the SOP document.

@olivierlambert Oh I see, thanks for the help.

Okay so that's fine on this side.

@olivierlambert Yes, thank you so much for the big help.

@olivierlambert Thank you for sharing that information, that is an additional knowledge for me.

@MathieuRA Indeed, that's the right way to do it, I think

@stormi Thanks for the big help that fixed the issue.

@olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8 It's not perfect but that should help Example: vm.start { "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f", "bypassMacAddressesCheck": false, "force": false } { "errors": [ "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)", "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)", "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)" ], "message": "", "name": "Error", "stack": "Error: at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15) at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7) at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)" } 2 julien-f committed to vatesfr/xen-orchestra feat(xo-server): better info when failing to start a VM Fixes https://xcp-ng.org/forum/post/47329