XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. reiichi001
    R
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 5
    • Groups 0

    reiichi001

    @reiichi001

    0
    Reputation
    3
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    reiichi001 Unfollow Follow

    Latest posts made by reiichi001

    • RE: [dedicated thread] Dell Open Manage Appliance (OME)

      @AtaxyaNetwork could you please DM me a link to the current appliance you've been working on? I just started going through the same before coming across your blog.

      posted in Compute
      R
      reiichi001
    • RE: XenServer-8 to XCP-NG

      @stormi said in XenServer-8 to XCP-NG:

      But there's also the possibility that the platform number we use to detect an upgradeable product has changed.

      This is probably the case. When I tried in-place upgrades, XCP would sometimes see it, but not always. I expected that to be the case when trying out XCP 8.2.1, but this would still happen occasionally on XCP 8.3 as well. (Given that XenServer 8 is reporting itself as 8.4, Citrix probably did this on purpose.)

      I'm assuming this is also why XVA export/import also doesn't work and live migrations don't work?


      I did eventually just spin up Xen Orchestrator Community Edition in my environment so I could use Warm Migrations, as XO Enterprise does not offer those. (Knowing that if something went wrong, I wouldn't be able to get support for that, but it beats out having to rebuild around 200 customized-for-clients VMs and migrating their data using software tools)

      posted in Migrate to XCP-ng
      R
      reiichi001
    • Can one fully disable PCI and USB Passthrough?

      Hello,
      This is as the title states.

      I'm looking into using XCP-Ng in a production environment that needs to have restricted access for PCI DSS compliance. Previously, the servers were built on Citrix Hypervisor with a Xenserver Express license, so they didn't have the ability to connect anything regardless of whether the hypervisor supported it or not.

      As we're moving these servers to XCP-Ng 8.3, I've seen that our XO now shows support for PCI Passthrough and USB Passthrough.

      Will commenting out all entries in /etc/xensource/usb-policy.conf and adding a line for DENY # block all USB be sufficient for preventing USB passthrough through XCP-Center (I'm aware it's legacy / no longer supported) and Xen Orchestra?

      Is there another config file I can use to disable PCI passthrough? Or does this mean I will need to check with my coworkers who manage the hardware to see if we can disable it in BIOS/EFI via turning the iommu features off? Does XCP-Ng support disabling it from the bootloader, and is there a preferred method of doing that?

      posted in Hardware
      R
      reiichi001
    • RE: XenServer-8 to XCP-NG

      @olivierlambert said in XenServer-8 to XCP-NG:

      You can use warm migration to solve this. Also, we provide pro support and services to help you to migrate, it's probably a lot of time saved with our expertise

      Reply

      I have tried this over XOA, but it does not work with even a cold migration where the VM is shut down.

      This is the XOA error I receive when trying to go from XS8 (DBV 2024.0229) to XCP-ng 8.3 (build date Oct 11, 2024 4:26:51 AM / DBV 0.0.1 reported).

      We use XOA Enterprise 5.103.0 in this environment but would be planning to use XCP-Ng 8.2.1 community for these VMs in particular.

      If the recommendation would be to open a support ticket from my XOA account to help ease this process, I can do so. ...we were hoping XS8 would keep an indefinite trial, but that has been shown to not be in Citrix's interests.

      vm.migrate
      {
        "vm": "b62f3bf3-72b9-ad40-885f-77c69d5f0f1a",
        "mapVifsNetworks": {},
        "migrationNetwork": "eeb0d173-74b2-8f00-d5be-906339714f42
      
      ",
        "sr": "e20f5eac-f34d-7151-b1f6-5d6cb960843d",
        "targetHost": "523f39b6-d4e8-4347-94e2-5c6c9c9705ba"
      }
      {
        "code": "IMPORT_INCOMPATIBLE_VERSION",
        "params": [],
        "task": {
          "uuid": "816c7f21-8825-4ad8-1080-13c87edda67b
      
      ",
          "name_label": "Async.VM.assert_can_migrate",
          "name_description": "",
          "allowed_operations": [],
          "current_operations": {},
          "created": "20250204T00:32:55Z",
          "finished": "20250204T00:32:57Z",
          "status": "failure",
          "resident_on": "OpaqueRef:33c97776-8b37-455a-ab62-13139da98726",
          "progress": 1,
          "type": "<none/>",
          "result": "",
          "error_info": [
            "IMPORT_INCOMPATIBLE_VERSION"
          ],
          "other_config": {},
          "subtask_of": "OpaqueRef:NULL",
          "subtasks": [],
          "backtrace": "(((process xapi)(filename ocaml/xapi/importexport.ml)(line 373))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 1866))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2544))((process xapi)(filename ocaml/xapi/rbac.ml)(line 188))((process xapi)(filename ocaml/xapi/rbac.ml)(line 197))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 77)))"
        },
        "message": "IMPORT_INCOMPATIBLE_VERSION()",
        "name": "XapiError",
        "stack": "XapiError: IMPORT_INCOMPATIBLE_VERSION()
          at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)
          at default (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_getTaskResult.mjs:13:29)
          at Xapi._addRecordToCache (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1068:24)
          at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1102:14
          at Array.forEach (<anonymous>)
          at Xapi._processEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1092:12)
          at Xapi._watchEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1265:14)"
      }```
      posted in Migrate to XCP-ng
      R
      reiichi001
    • RE: XenServer-8 to XCP-NG

      I've got a similar situation to this thread.

      Currently, we have a mix of Citrix Hypervisor 8 (8.2 CU1 LTS), which is going end of support later this year. We use a mix of standard license and xenserver express licenses.

      I've been testing out migrations to both XenServer 8 through Citrix and XCP-Ng, but most of the staff I work with primarily use XenCenter for managing VMs, and XCP-Center hasn't quite had the ability to keep up with recent changes. We do have XOA as well, but as we make use of importing/exporting VM images quite often, XOA doesn't quite work work well here, which would mean having to have XenCenter for our licensed VMs and XCP-Center for our unlicensed ones if we go with XCP. But that's a tangent for context.

      What I've noticed is that I can upgrade from CHU8 to XS8 or XCP 8.2.1 fine, but there doesn't appear to be any way to "upgrade" or migrate from XS8 to XCP8.

      And exported XVA files from XS8 cannot be imported to XCP 8.2.1 or 8.3, which is a blocker if we want to fully migrate to XCP to keep our environment uniform.

      If I put in a XCP-Ng ISO (either 8.2.1 or 8.3), it does not offer the ability to upgrade from a XS8 install. XOA is also unable to copy a XS8 VM over to XCP 8.3.

      posted in Migrate to XCP-ng
      R
      reiichi001