Yes! That's a good guide for what you want to achieve

@yann said in New Rust Xen guest tools: @john.c OK, that will be useful when the repo is signed, but for now I don't see what adverse effect it can have. Do I miss something? Also we try to avoid breaking support for older OS versions, so we'll likely continue to advertise the old format for older versions of Debian. @yann From Debian 13.0.0 (code name Trixie) having repository signing is mandatory. Without it apt will straight refuse to install, update or upgrade its packages. Also doing with deb822 format will help to protect the GPG Key, used by Vates from abuse by another repository. Especially if that repository is hosting malware laden deb packages. As only the Vates repository can then use that signing key, as defined in the sources file. Refusing to install, update or upgrade is an adverse effect wouldn’t you say?

@AtaxyaNetwork said in Unbootable VHD backups: @Schmidty86 Try to detach the disk and reattach, it should be xvda in order to be bootable That's what I was thinking as well, but obviously something is off with this VM. @Schmidty86 is the old host still online? If so you might be able to perform a Live Migration or a replication job to copy it from the old host to the new.

I had this tab still open which lets me realize that despite we packaged vmfs6-tools and updated the documentation at https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/#local-migration-same-host, we didn't inform you here. Now it's done

AlmaLinux 8.10

That's nice! It means it scales relatively well with many threads, it's a good result

Hi, There is an issue and/or a PR (I don't remember where though) to have a specific extra file to manage user config without overwriting it. Until then, it will be overwritten after updates. @Team-XAPI-Network could provide the link to the issue (or PR?) and check to make it merged when possible

@mdavico said in Debian 9 virtual machine does not start in xcp-ng 8.3: Update: If I change the vCPU configuration to 1 socket with 4 cores per socket the VM starts correctly Interesring. First time I heard it had any effect at all on a VM.

@Danp Hi, I'll try this. Thank you very much. Best regards Mattmurdock78

@Danp Thank you.

Excellent news!

We don't have any feedback on that, so I can't tell

Hmmm that's a possibility. An interesting lead to explore. Ie trying to do it yourself to see if the result if the same?

@AtaxyaNetwork I appreciate the sentiment. I think this one is all on me as pointed out by @Danp .. My VDI's would not register without this step. I'm unsure as to why because the error logs were completely blank within XO. Your post in conjunction with the docs were extremely helpful though!

You are welcome Enjoy XCP-ng/XO!

Yes, the old method should work

Great! Thanks for the feedback

@Bastien-Nollet Thanks as always @florent