Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    M
    @anthoineb @gduperrey @bleader Hi! Thank you very much for your responses. I actually found the issue and it was not caused by the XCP-ng patches. Appearently one of my switches had a malfunction and lost it's jumbo frames config on the ports involved... It seems like this happened in the time frame between XCP-ng updates . Last time I used this setup the jumbo frames / storage setup was working fine so I thought it might be related to these patches. Anyways sorry for taking your time in this regard- Best regards

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    J
    I feel like I used to know this answer, but that could be my imagination. I have a Windows Server 2008 R2 Standard VM that was exported from Xenserver 6.5 perhaps 10 years ago. The export is servername.ovf along with a pair of [uuid].vhd files. The source of the export was an HP server with a paid of Xeon E5s... maybe 2640 or similar. The new target is variety of Dell Poweredges with various "modern" Xeons (eg, 6226R). There's a HUGE architectural difference. I have tried: Importing the OVF, which fails complaining about the disks TAR'd the OVF and VHDs into an OVA, which also fails I've tried these with two versions of XCP Center and two versions of XO targeting three versions of XCP (8.1, 8.2, and 8.3) Importing just the VHDs via XO, that fails I poked around on the google and Gemini suggested using vbox to convert the VHD to a VMDK, but I think that's incorrect, and it doesn't work anyway.... Vbox bombs out with "could not get the storage format" of the VHD. Does anyone have any idea on how I might be able to get this ancient @$$ VM running again?

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    P
    Hello forum... On delta backups we can use CBT and NBD to speed backups. Why is it not possible to use NBD on full backups ? just curious... Thank you, Pedro

  • Our hyperconverged storage solution

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

  • Non-English speakers

    37 Topics
    135 Posts
    AtaxyaNetworkA
    Pour l'ISO montée deux fois : My bad, j'ai ajouter un truc en trop sur mon précédent fix. Une PR est en cours pour corriger ça. Pour le problème principal : J'ai identifié la cause, mais je n'ai pas encore de solution. Sans les drivers Xen (non initialisés avant l'installation), une VM est limitée à 4 périphériques. La séquence de boot ne peut donc pas détecter le second disque contenant le fichier Kickstart (ks). Côté Packer, on semble être bloqués par cette contrainte XCP-ng. Les seules alternatives actuelles seraient de se limiter à : 2 disques + 2 CD ou 3 disques + 1 CD + HTTP (Note : L'installation manuelle fonctionne car l'installateur démarre directement, avec le driver xen_blkfront, alors qu'avec Packer, l'injection de notre fichier interrompt le flux de démarrage classique). Je vais fouiller encore un peu, mais sans certitude d'un contournement possible. (et je regarde pour ajouter le CDlabel)