Categories

  • All news regarding Xen and XCP-ng ecosystem

    144 Topics
    5k Posts
    marcoiM
    Applied the latest pushed updated to production, no major issues. The only thing to note is my backup XCP config failed Sunday, some time post the patches being applied. The error was the Body Timeout Error. This morning the backup ran without issues. Not sure why, but it wasn't a big deal and it working now. So not sure tied in with patching or not.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    F
    @acebmxer What I'm up to is the following: Two separate VMs, each with one of these video cards and an 8-port PCIe serial controller assigned. I have 8 monitors for the setup; 4 per VM. The VMs will be used to run software which controls radio receivers and each display will act as a heads-up for a different instance of the software. I run this particular configuration with a Type 1 hypervisor on smaller systems but this is the first time deploying on larger-scale bare metal. As further experimentation I put the serial cards in the server and verified via lspci they were there. I ran xen-pciback.hide against each adapter by itself then against all three (including video card, per docs online) and they appear assignable when queried from the hypervisor's local command prompt. But the new cards (serial) don't appear in the drop-down of the Attach PCI section - even after a server reboot. A somewhat related question on keyboard/mouse pass-through: One has to have a separate mouse/keyboard for EACH VM running on the system in order for this to work properly, I assume? By separate, not the one used to access the hypervisor console itself.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    P
    Hello forum! I recently begun mirroring my full backups to backblaze and I've been getting the error "maximum size allowed is (your minPartSize for the chunk)" [image: 1782755451515-e9df4605-45a6-494e-912c-6e48f50615ab-image.jpeg] This error was supposed to be fixed, earlier this year, but I'm still getting it. Actually PR #9396 might only fix direct backups and not mirror backups... I'm running xo built last week. Object lock is set to 0 at backblaze for the time being, but I plan to turn it whenr this problem is over. This may be caused because I'm mirroring from a local nfs remote (not encripted) to backcblaze remote (encripted) ? Maybe this scenario wasn't tested. Anyway, everytime I run the mirror job the larger VMs would fail and all VMs would show warnings about issues checking XVA: [image: 1782755859883-97d973ab-83b9-4981-917e-efb374c879c2-image.jpeg] I've just bumped minPartSize to 100 000 000 (following the recomendation from Backblaze and hope that the maximum size allowed error goes away, though the warnings will still be there. Thank you, Pedro

  • Our hyperconverged storage solution

    48 Topics
    757 Posts
    J
    Here is the log from when xen04 last crashed xen04-jun12-journalctl-crash-summary.txt

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !