Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    stormiS
    @rzr said: Thank you again for feedback we will try to address reported issues on next batch (to come soon). Note that some issues are not related to this specific update batch, but might have been introduced on previous ones (TBC). Not knowing myself what it meant, I asked Philippe: it's about the nslookup issue. And potentially the issue reported by @ph7 but it's not clear to me yet if there was a problem with XCP-ng or Xen Orchestra. Anyway, basically this means that there's no known issue caused by this batch of updates, and that we'll keep addressing any relevant issue in the next updates if necessary, as usual.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    B
    @LucienLassalle Thanks for the quick response and the effort in recreating the issue! It all played out exactly as you laid it out, even the cert showing up as a .new.pem at first. Out of curiosity, what in your testing did result in causing this issue? Is it possible that my upgrade from 8.2 to 8.3 may have caused the underlying issue?
  • 3k Topics
    28k Posts
    A
    @olivierlambert Any chance of revisiting this issue and allowing a VM VIF MTU to be changed from XO? If not in the main display (where it shows the MTU), then in the Advanced settings window (which seems like a good and easy place to have the MTU option). I have a small XCP server that has MTU 9000 set on the main (and only) interface but most VMs need to be set to 1500. The windows Xen network driver just inherits the MTU from XCP. Yes, you can use the CLI in Windows or XCP to change it, but it would be nice to have it in XO for that VIF (VM restart required).
  • Our hyperconverged storage solution

    47 Topics
    750 Posts
    olivierlambertO
    Please disable HA and report if you still have the issue.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !