@olivierlambert Ah! I didn't have any ISOs connected to the CD drive, but the VM did have quite a few snapshots. I deleted a majority of those (though not even all of them), and it migrated successfully. Thanks!

@McHenry

https://xcp-ng.org/docs/api.html

Restarting the API
Sometimes, you might want to restart the toolstack (API and storage stack). You can do it with the following command from the host console (or directly with Xen Orchestra):

xe-toolstack-restart

TIP
Restarting XAPI won't affect any running VMs. However, all backup/export tasks will be removed.

@olivierlambert said in VM Autostart order:

There's already the vApp support in XAPI since a while, so it's really only a XO Lite/XO matter.

Is the AutoStart vApp along with the script already created? If not then like I said its both.

Yes, it's a "definition" question/problem: a SR is the exact place where you store your virtual disk images. On NFS, it's a folder named after the UUID of the SR. As Dan said, if you connect to the same NFS folder, it will create a new folder for each new SR inside. So even if it's the same physical device/NFS share, there's many SRs on it.

For a block based SR, it's different: if you pass a LUN (in ISCSI for example), it will attach it and warn you: either you want to re-attach the previously existing SR (UUID etc) either you erase it completely to start from scratch. There's no "folders" on a block space like a LUN, so it's different.

@olivierlambert

Thanks Oliver, lots to learn.

p.s. Congrats on the 8.3 launch.

Thanks !

@Andrew it’s a simple dell USB-C to Ethernet adapter, nothing fancy.

I’m running XCP on a laptop with only USB-C ports…

I’m gonna try with other types of adaptors and we’ll see 😕

@olivierlambert

No problem however I am confused.

If I use XO, which does not need registration, and the proxy does need registration however is the proxy registration tied to the unregistered XO?

@olivierlambert
I will try to...
Perhaps, it is related to the untrusted certificate of my installation.

This requires some extra plugins to be able to do it, and as it's rather "advanced"/not usual for the main XCP-ng use cases (which is connecting to iSCSI/NFS/shared storages, it's not a priority. Which doesn't mean it's not a good idea or interesting, but there's some work to do it and then to maintain it.

@manilx Just out about this 🤔
ScreenShot 2024-10-04 at 10.39.51.png

Stupid me.... Could have used that a few times, between our production and backup pools which are different.

There's always something "new"

@olivierlambert
There is only "Dashboard/Alarms" and that is empty for me

@McHenry said in Understanding remote management using XO:

@Danp

I am using CE so I do not think XO proxy is available at this time.

You can setup a proxy yourself using the CE version, just like with everything with the CE version, your milage may vary.

@pdonias @julien-f yep fixed now, thanks.

@dguy313 Sunday's XO commit 030b3 solves the issue for me.

@julien-f is aware of this problem and we'll find a way to make it more obvious 🙂

you can't configure vGPU limitation at self-service rule, but user can select vGPU at VM creation based on that rule. So it would be unlimited. But i can't really check it with my nvidia cards.

and what is Share this VM?

We can make the message clearer, but we advertised multiple time that adding PCI passthrough UI required XAPI changed only available in 8.3