Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    D
    @yomeyo It's a client shutdown being misreported as a client error. I'll fix this in the next release. The warning on upgrade should be harmless and you can simply close the application/click OK as you've done.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    I put your colon-versus-equals question on a spare host, because I couldn't answer it from memory. With the colon form xe creates a key literally called auto_poweron:true with an empty value, so the entries you saw were three different keys and none of them was the real auto_poweron. Typing false afterwards just made another one. It exits 0 every time and prints nothing, which I'd call a rough edge rather than a feature, though I don't know whether the CLI is meant to validate map keys at all given other-config is deliberately free-form. Your sleep finding is probably the more useful half for whoever reads this next. The executable-bit part is in the docs now, it went onto the troubleshooting page after you reported it: https://docs.xcp-ng.org/troubleshooting/common-problems

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    poddingueP
    That question has come round three times on this thread since 2020, so it isn't a one-off. I'd rather not promise documentation I can't deliver, but I can take it to the people who decide and come back here either way, including if the answer is that proxy deployment stays an XOA thing. On the licensing side I'd sooner not encourage patching those checks out, mostly because I don't know what they're guarding. In the meantime, the two community scripts in this thread are what people are actually running, which is worth saying plainly even though it isn't the documented path you asked for.

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    134 Posts
    AtaxyaNetworkA
    Déja une piste intéressante, on dirait que pour une raison quelconque l'iso est mount deux fois [image: 1786437651889-14d66748-1d54-411a-b62a-a3691d6decd9-image.jpeg]