Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    A
    Ran into some issues with sdncontroller.py (XCP-ng 8.3 and xcp-ng-xapi-plugins-1.16.0-1) when creating traffic rules on VLAN VIFs (and networks) in XOA — same error on both Premium and Community. The problem turned out to be a line feed sent by XOA. On line 236 of sdncontroller.py, I added a fix that solved the problem, and it now works perfectly managing traffic rules in XO on VLAN networks: def update_args_from_ovs(args): # FIX: strip line feed (\n \X0a) sent by Xen Orchestra args["bridge"] = str(args["bridge"]).strip() # get parent... I had another problem when adding rules on networks that weren't connected on all hosts, because those hosts didn't have VMs running on that network (default). Manually connecting them worked fine. I think it's more of an XO error than xapi plugin, but worked ok in my case. Thanks for the great work!

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    M
    Same behaviour across XO, XOA + XCP-ng Centre. Not had this before, I'm struggling to restart VMs. I first noticed that some of the backup tasks yesterday were running way longer than they normally do, and then still running into today which is when I started investigating the issue. The biggest clue at the moment is when running the command; xe task-list uuid ( RO) : 92b59f22-15ae-2551-8839-f0f938a07af7 name-label ( RO): SR.scan name-description ( RO): status ( RO): pending progress ( RO): 0.000 uuid ( RO) : 880f0f4a-8e84-0954-2521-81831d559dd3 name-label ( RO): Async.VM.hard_shutdown name-description ( RO): status ( RO): pending progress ( RO): 0.273 Tried; xe-toolstack-restart Made no difference. Just seeing if there is any more debugging I can do to try and get this working without doing a full host power off/on. It's all strange though as the running VMs are all working fine. The Storage Repository it appears to be getting stuck on is the one storing the ISOs for the VMs. Yet nothing has changed at all. The Host can ping the Storage Repository fine too. Any ideas what to test to get this back working without a full Host reboot? I've been round the loop many times of killing the stuck tasks and then trying to Start/Stop VMs and same issue each time, just goes back to the same hung state. Storage Repository is on a Windows machine, so the only thing that is jumping to mind is some janky automatic Windows update that has kicked in and broken something. But it's strange the running VMs are still working with their ISOs sitting in that same Storage Repository (I'm not 100% clear off the top of my head if running VMs still require access to the ISO Storage Repository to be running post-boot)

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    C
    This happens to me mostly with non-config backups but occasionally a config backup will fail. The VM that fails the backup with the body timeout changes around every day, then once a week or so, every VM will get backed up. It only happens on this XO instance and only with the full backups. It doesn't happen on another XO instance that performs delta backups of the same VMs a couple hours later. [image: 1786119913263-0f04acef-0cd9-487c-8292-e27174bf9999-image.jpeg]

  • Our hyperconverged storage solution

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

  • Non-English speakers

    37 Topics
    131 Posts
    AtaxyaNetworkA
    @jeremie1977 Ah, oui effectivement je n'ai pas testé avec plusieurs disques ! Et j'ai du typo dans la doc, je vais faire une PR pour modifier Je pense que c'est du a la façon d'insérer les disques et les DVD coté XCP-ng. Je vais investiguer !