First release of Xen Orchestra (based on xend, so oooold Xen API) was during summer 2009. Rewriting for XAPI is done back in 2013. It's been a bit longer than few years

Also, I can guarantee that if everybody had a similar experience than yours, nobody would have adopted our stack. I know it doesn't help you directly, but there's so many specific and external factors that can make your experience painful in your environment. There's no reason to reinstall XCP-ng, and what you think your network issue is, it's likely the pool member simply cannot joining the master.

Anyway, I hope the community will assist you as Tom started, so you can get on your feet. Thanks for keep trying, your feedback is important for us.

Yes, anything moving blocks around will generate more data to backup. So it might not be some specific files, just logs rotation or anything doing random write at many places

No. I'm saying that all VMs (HVM) are using RFB consoles, readable with VNC protocol (used by XO or a VNC client). There's no text console since it's like a screen in HVM.

If you are stuck on "Loading in progress", it's not a console issue, it's a VM issue. You can use a LiveCD to check what's going on.

Ping @lsouai-vates

It's not possible to have text on an HVM guest, it was only usable for PV guests. You can use VNC as I said, it's even inside our doc: https://docs.xcp-ng.org/vms/#use-a-vnc-client

Hi,

What do you mean? The host {{actions}} doesn't have any endpoint to stop it?

Hi,

HVM guests do no have text consoles but RFB consoles. Use XO or XO Lite to see VM consoles (or VNC if you really want to makes things more complex)

Backups are made by doing a VHD diff. A VHD block is 2MiB, if you modify just one bit inside a 2MiB block the entire block is needed to be exported.

MS OS are known to write a bit everywhere, so I'm not entirely surprised.

@AtaxyaNetwork said in XO update fails:

@edisoninfo Hi,
What's xo-install.sh ? It's a third party script ?

Very likely indeed

Those scripts really needs to make sure to provide the URL of the repo to report issues in a very visible way.

Thanks for your feedback, @florent will take a look.

In your XOA URL, just add /v6 at the end.

You can check the new network view in /v6 of your XO URL

I will let @florent answering this one

You need to swap the template in priority. This might drastically change the result

Have you read the doc first? https://docs.xcp-ng.org/xostor/

This gives a nice overview on how it works

@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

It's your call, but there's no guarantee it won't break for now, as the code is relatively young.

Ping @florent

No worries, always good to have feedback

I think the dev working on it had personal issues few days before the release, so at worst it will be there in a patch release or in 5.106. There's so much things in the pipe, it's possible sometimes they aren't shipped on D-day. But it will be there finally