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
    D
    Update on the situation... It was permission issue, setting up correct permissions after the upgrade solved the problem. During my testing I've also found out that not setting sleep in rc.local will not trigger autostart, in my scenario "sleep 60" (seconds) was barely enough, so to make sure all other hardwarde is booted up (storage, switches etc) before booting up VM's, in my scenario 300 seconds is set. I prefer using rc.local and setting up autostart via vApps because you can fine tune starting order of the apps and delay start for each. In regards to colons vs equals: If you go with colons, you can simply type whatever you want, eg. "xe pool-param-set uuid=<VM_UUID> other-config:whateverthefuype:true" -> you will not any prompt that command does not exist or similar. I am not sure if that's supposed to be like that?! My problem here is resolved, maybe this will help someone in the future.
  • 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!
  • 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]