Unable to create VM

[Sugarat]

Hi there.

I am currently testing XCP-NG. I installed onto a server and all has been quite smooth sailing. Now I wanted to see if I can add another host to the pool and migrate the VM's between them. So I added an external NFS server, and have added the NFS SR to the pool. However, after adding the second XCP-NG host to the pool, I am unable to create a VM. When I click the create button it shows an error. Looking in the log it says:

no object with UUID or opaque ref: OpaqueRef:32cbe139-e607-6f84-e29b-a6b1d24f213c

Can anyone suggest where to look for further diagnosis of this issue?

Many thanks

[Danp]

@Sugarat If you are running XO from sources, make sure you're completely up-to-date with the latest source. There was a fix released for this earlier this week.

[Sugarat]

@Danp Thanks for that. I built the XO from source a few days back, but maybe it just missed that. I'll rebuild now and see what happens.. Thanks

[Sugarat]

I have just rebuilt the XO install, and that error has... apparently changed into a different one. Create VM operation still fails, but this time the message is:

HANDLE_INVALID(SR, OpaqueRef:NULL)
This is a XenServer/XCP-ng error

Hmph

[Danp]

@Sugarat I'm not able to replicate here. Can you check under Settings > Logs to see if there is an entry there with a detailed error log?

[Sugarat]

@Danp I tried removing the second host from the pool but it now still will not allow me to create a VM.

Ah, nice. I did not know that you could drill down into the error. The dump is as follows:

vm.create
{
  "clone": false,
  "existingDisks": {},
  "installation": {
    "method": "cdrom",
    "repository": "8eb59f38-25e2-4486-b7c2-98dc938e1fc6"
  },
  "name_label": "Windows 10 (64-bit)",
  "template": "3d3a2920-24c8-f280-5c27-1e4d4a82253c-7774689b-4ca1-4dea-8545-dddd6b64c17f",
  "VDIs": [
    {
      "bootable": false,
      "device": "0",
      "size": 34359738368,
      "type": "system",
      "SR": "3d615d9a-4b54-cf75-ef43-0d08bbf0a640",
      "name_description": "Created by XO",
      "name_label": "Windows 10 (64-bit)_epunu"
    }
  ],
  "VIFs": [
    {
      "network": "945f1105-893e-becc-35fe-0a97328ee7ac",
      "allowedIpv4Addresses": [],
      "allowedIpv6Addresses": []
    }
  ],
  "CPUs": 2,
  "cpusMax": 2,
  "cpuWeight": null,
  "cpuCap": null,
  "name_description": "",
  "memory": 4294967296,
  "bootAfterCreate": true,
  "copyHostBiosStrings": false,
  "createVtpm": false,
  "destroyCloudConfigVdiAfterBoot": false,
  "secureBoot": false,
  "share": false,
  "coreOs": false,
  "tags": [],
  "hvmBootFirmware": "uefi"
}
{
  "code": "HANDLE_INVALID",
  "params": [
    "SR",
    "OpaqueRef:NULL"
  ],
  "call": {
    "duration": 8,
    "method": "VDI.create",
    "params": [
      "* session id *",
      {
        "name_description": "Created by XO",
        "name_label": "Windows 10 (64-bit)_epunu",
        "other_config": {},
        "read_only": false,
        "sharable": false,
        "SR": "OpaqueRef:NULL",
        "type": "user",
        "virtual_size": 34359738368
      }
    ]
  },
  "message": "HANDLE_INVALID(SR, OpaqueRef:NULL)",
  "name": "XapiError",
  "stack": "XapiError: HANDLE_INVALID(SR, OpaqueRef:NULL)
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202412191835/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202412191835/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:454:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"

[Subsystem3339]

I am having the same issue which I also have two hosts which I just updated my XO from source yesterday. My log looks the exact same.

[Danp]

Seems like it is missing the SR information during VDI creation. Does this also occur with other SR types, ie: local storage?

[Sugarat]

@Danp Yes. Even when I select a local SSD SR it still happens. I'm not able to create any VM's at all, no matter which SR I am selecting.

[MathieuRA]

Hi @Sugarat. thanks for the report.
Can you try this branch: fix-handle-inavlid-vm-creation?
This should fix the issue

[Sugarat]

@MathieuRA It does indeed Sir. Thank you very much!