Categories

  • All news regarding Xen and XCP-ng ecosystem

    140 Topics
    4k Posts
    G
    @olivierlambert I did post an alternative script here: https://xcp-ng.org/forum/topic/8620/usb-passthrough-override-script-to-ensure-usb-policy-conf-consistency But it was later removed due to request by @stormi . I'm currently using my script which basically backs up your settings and overrides the default one (after backing it up on first install) on every boot. I know its a crude way to handle but it was only meant to be temporary till you guys find a solution. I have reposted it.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    C
    As I can't find it anywhere: What exactly is happening on join/leave? Is the masking changing at runtime and affecting every new started VM, does the pool need to be rebooted after an older server has been removed, to "unlock" all features? I have a pool with HPE DL380 Gen 9 and 10 where Gen 9 will replaced with Gen 12. So I assume it makes sense to remove 9 first, then add 12. But how exactly is the masking process working? Should I reboot Gen 10 first (shutting down all VMs) or add 12, move VMs over... or just shutdown and start all currently running VMs? In the early days (~XenServer 6) it had to be done manually by getting CPU features, calculating the commons and give it as parameter to join command. What I did not see though, is: How exactly is it working on removal and what's best practice. (also: should be added to documentations)

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    S
    Hello, When we do usual task such as creating/removing/migrating VM or starting console, XOA gets disconnected for about 30s then comes back again. We had many issues because our PoC Pool (hosted on OVHcloud Baremetal servers) was first installed using public IP then were re-configured to use private IPs : reconfigure management IP of every host changed reference master IP on /etc/xensource/pool.cfg generate new SSL certificates for every node of the pool Maybe we missed some reconfiguration due to lack of documentation. I might be wrong but when XOA looses connection, /var/log/xensource.log on pool's master node shows : Dec 27 21:35:45 xcp-ng-317 xapi: [ info||160 /var/lib/xcp/xapi|session_check D:468110568dff|session_check] Session check failed: the client used an illegal or expired session ref 'OpaqueRef:f679a584-7f81-dc17-8dde-c3a575a072ba' Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] session_check D:468110568dff failed with exception Server_error(SESSION_INVALID, [ OpaqueRef:f679a584-7f81-dc17-8dde-c3a575a072ba ]) Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] Raised Server_error(SESSION_INVALID, [ OpaqueRef:f679a584-7f81-dc17-8dde-c3a575a072ba ]) Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] 1/4 xapi Raised at file ocaml/xapi/session_check.ml, line 88 Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] 2/4 xapi Called from file ocaml/xapi/server_helpers.ml, line 75 Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] 3/4 xapi Called from file ocaml/xapi/server_helpers.ml, line 97 Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] 4/4 xapi Called from file ocaml/libs/log/debug.ml, line 250 Dec 27 21:35:45 xcp-ng-317 xapi: [error||160 /var/lib/xcp/xapi|dispatch:VIF.get_by_uuid D:dd849736b2fb|backtrace] Dec 27 21:35:45 xcp-ng-317 xapi: [ info||160 /var/lib/xcp/xapi|session.login_with_password D:f354a161de1a|xapi_session] Session.create trackid=c5635894fdaa50bf600bcc507ae8a7e3 pool=false uname= originator= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 Is it normal that XOA often looses connection to pool / master ? Is there anything we can do to avoid this ? Thanks in advance for your help !

  • Our hyperconverged storage solution

    39 Topics
    703 Posts
    S
    @ronan-a said in XOSTOR hyperconvergence preview: @peter_webbird We've already had feedback on CBT and LINSTOR/DRBD, we don't necessarily recommend enabling it. We have a blocking dev card regarding a bug with LVM lvchange command that may fail on CBT volumes used by a XOSTOR SR. We also have other issues related to migration with CBT. Is the problem still occurring on latest XCP-ng / XOSTOR version ? Not being able to use CBT on XOSTOR is a big issue for backup/replication.

  • Non-English speakers

    31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related