<![CDATA[Importing OVA - “Device Already Exists”]]>I’m really new to XCP-NG & XO but I’m loving it so far. Every VM I’ve migrated from ESXi has worked flawlessly - except one. One of them, whenever I try and import the OVA it errors out and the logs say “device already exists”. It goes and creates all of the VMs virtual hard drives. I’m at a loss as to what is actually going on. Can anybody point me in the right direction?

]]>https://xcp-ng.org/forum/topic/6001/importing-ova-device-already-existsRSS for NodeMon, 15 Jun 2026 21:21:02 GMTMon, 20 Jun 2022 20:32:02 GMT60<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 27 Dec 2022 17:33:58 GMT]]>@trent234 Interesting, good to know. I do know that XCP-ng only officially supports 7 network interfaces, so not really surprised by that. It supports more VHDs though so feel like I shouldn't be seeing this error.

]]>https://xcp-ng.org/forum/post/56526https://xcp-ng.org/forum/post/56526Tue, 27 Dec 2022 17:33:58 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 27 Dec 2022 00:36:11 GMT]]>FYI this same error occurs when I try to assign 9 virtual network interfaces for a new VM as well. So its not just a limit on drives.

]]>https://xcp-ng.org/forum/post/56502https://xcp-ng.org/forum/post/56502Tue, 27 Dec 2022 00:36:11 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 15 Dec 2022 20:56:09 GMT]]>@olivierlambert Just so you are aware, I just sent in a ticket for it a few minutes ago.

Thanks again for the help!

]]>https://xcp-ng.org/forum/post/56231https://xcp-ng.org/forum/post/56231Thu, 15 Dec 2022 20:56:09 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:54:29 GMT]]>No worries, next week is fine 🙂 Busy here too 😉

]]>https://xcp-ng.org/forum/post/56024https://xcp-ng.org/forum/post/56024Thu, 08 Dec 2022 18:54:29 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:39:53 GMT]]>@olivierlambert Will do! I will try to do that today, might be next week though, busy week so far at work lol.

Thanks!

]]>https://xcp-ng.org/forum/post/56021https://xcp-ng.org/forum/post/56021Thu, 08 Dec 2022 18:39:53 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:34:47 GMT]]>Please open a ticket so we can see in more depth what would be the best options 🙂

]]>https://xcp-ng.org/forum/post/56020https://xcp-ng.org/forum/post/56020Thu, 08 Dec 2022 18:34:47 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:30:54 GMT]]>@olivierlambert I would be interested, however this is a production environment, so what are the risks of that? Does it require a beta version of XOA to be installed?

Thanks for the help by the way, we aren't in some major rush so I don't mind tinkering a bit, just can't have anything cause stability issues.

]]>https://xcp-ng.org/forum/post/56019https://xcp-ng.org/forum/post/56019Thu, 08 Dec 2022 18:30:54 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:28:42 GMT]]>Would you like to participate to a very early beta test of our new capability to import the VM from VMware directly from VMware API to XCP-ng? (using Xen Orchestra)

]]>https://xcp-ng.org/forum/post/56018https://xcp-ng.org/forum/post/56018Thu, 08 Dec 2022 18:28:42 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:27:04 GMT]]>@olivierlambert Yes, that is correct, it's an exported OVA from VMWare using their CLI based OVA tool (since you can't do it in the GUI anymore). We are working with a vendor to validate their platform on XCP-ng so we can hopefully ditch VMWare and put everything on XCP-ng which is where the rest of our VMs reside.

]]>https://xcp-ng.org/forum/post/56017https://xcp-ng.org/forum/post/56017Thu, 08 Dec 2022 18:27:04 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:25:36 GMT]]>@planedrop are you importing this OVA from VMware out of curiosity?

]]>https://xcp-ng.org/forum/post/56016https://xcp-ng.org/forum/post/56016Thu, 08 Dec 2022 18:25:36 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Thu, 08 Dec 2022 18:22:28 GMT]]>@tjkreidl This is good to know, however doesn't really help when I am trying to import a OVA from a vendor.

@olivierlambert any suggestions here? I can submit an official support request if needed, just thought it'd be better to post this on the forums first. It is for a production environment though and we have been paying for support, so happy to go that route if needed!

I may also give the manual conversion to VHD format a shot and import those instead like @isd94 ended up doing.

]]>https://xcp-ng.org/forum/post/56015https://xcp-ng.org/forum/post/56015Thu, 08 Dec 2022 18:22:28 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 18:34:43 GMT]]>@planedrop Once the VM is up and has XenTools installed, you should be able to add a lot of disks to it. I ran some VMs with at least 6 or 8 VDIs, as I recall. For fun, I think I added round 20 to a test VM!

]]>https://xcp-ng.org/forum/post/55889https://xcp-ng.org/forum/post/55889Tue, 06 Dec 2022 18:34:43 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 18:18:41 GMT]]>@tjkreidl Interesting, I'll do some digging around to see if I can find any concrete info on this, feels like it should still import fine though and just maybe not work right after booting if that were the case though, right? Since the tools aren't even loaded until boot so it should still be able to create the VHDs and add them to the VM.

]]>https://xcp-ng.org/forum/post/55886https://xcp-ng.org/forum/post/55886Tue, 06 Dec 2022 18:18:41 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 18:17:58 GMT]]>@isd94 Hmmmm I'll consider giving this a shot, however my project here is validating a special piece of software with a vendor who may require the OVA be used as part of the setup, so would be great if that were possible.

]]>https://xcp-ng.org/forum/post/55885https://xcp-ng.org/forum/post/55885Tue, 06 Dec 2022 18:17:58 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 18:05:29 GMT]]>@isd94 My recollection is that to support 4 or more drives, XenTools has to be installed on the VM.
HTH,
-=Tobias

]]>https://xcp-ng.org/forum/post/55884https://xcp-ng.org/forum/post/55884Tue, 06 Dec 2022 18:05:29 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 18:03:47 GMT]]>@planedrop I ended up importing all the drives separately and then creating a VM and assigning the drives to the VM manually. It worked really well to be honest. I remember I had to mess around with it a lot, I can’t remember if I had to convert the drives to a different format or not but I’m leaning towards yes.

]]>https://xcp-ng.org/forum/post/55883https://xcp-ng.org/forum/post/55883Tue, 06 Dec 2022 18:03:47 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 17:55:36 GMT]]>@olivierlambert Yeah no problem!

HTTP handler of vm.import
undefined
{
  "code": "DEVICE_ALREADY_EXISTS",
  "params": [
    "1"
  ],
  "call": {
    "method": "VBD.create",
    "params": [
      {
        "bootable": false,
        "empty": false,
        "mode": "RW",
        "other_config": {},
        "qos_algorithm_params": {},
        "qos_algorithm_type": "",
        "type": "Disk",
        "unpluggable": false,
        "userdevice": "1",
        "VDI": "OpaqueRef:f0f82221-4a05-408d-9fab-1fbfc3c451b8",
        "VM": "OpaqueRef:c3c00d45-b356-49a2-9608-29e423ccaace"
      }
    ]
  },
  "message": "DEVICE_ALREADY_EXISTS(1)",
  "name": "XapiError",
  "stack": "XapiError: DEVICE_ALREADY_EXISTS(1)
    at Function.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/_XapiError.js:16:12)
    at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/transports/json-rpc.js:37:27
    at AsyncResource.runInAsyncScope (node:async_hooks:201:9)
    at cb (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
]]>https://xcp-ng.org/forum/post/55882https://xcp-ng.org/forum/post/55882Tue, 06 Dec 2022 17:55:36 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 06 Dec 2022 08:34:07 GMT]]>Please provide the exact error you have 🙂

]]>https://xcp-ng.org/forum/post/55863https://xcp-ng.org/forum/post/55863Tue, 06 Dec 2022 08:34:07 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Mon, 05 Dec 2022 22:06:28 GMT]]>Any update on this here? Just wanted to see if you found a solution. I have a OVA from ESXi that has 6 disks on it and 3 NICs and I am having basically the exact same error here.

However, mine only creates 3 of the 6 drives requested, it also seems to think there are duplicate drives or something along those lines (see image).

f6da6855-c810-4643-9865-775728a1ccbb-image.png

]]>https://xcp-ng.org/forum/post/55853https://xcp-ng.org/forum/post/55853Mon, 05 Dec 2022 22:06:28 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Sat, 25 Jun 2022 16:55:27 GMT]]>@olivierlambert I sent you a PM

]]>https://xcp-ng.org/forum/post/50523https://xcp-ng.org/forum/post/50523Sat, 25 Jun 2022 16:55:27 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Fri, 24 Jun 2022 20:15:57 GMT]]>So there's an issue when there's so many drives it seems. We'd like to have private access to this OVA to try to see what's going on.

]]>https://xcp-ng.org/forum/post/50508https://xcp-ng.org/forum/post/50508Fri, 24 Jun 2022 20:15:57 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Fri, 24 Jun 2022 20:13:24 GMT]]>@olivierlambert
I didn't see your reply, my appologies.

Here is what the log says:

HTTP handler of vm.import
undefined
{
  "code": "DEVICE_ALREADY_EXISTS",
  "params": [
    "0"
  ],
  "call": {
    "method": "VBD.create",
    "params": [
      {
        "bootable": false,
        "empty": false,
        "mode": "RW",
        "other_config": {},
        "qos_algorithm_params": {},
        "qos_algorithm_type": "",
        "type": "Disk",
        "unpluggable": false,
        "userdevice": "0",
        "VDI": "OpaqueRef:ceb1f386-f16f-4730-a4b6-bf2a48ce0e1b",
        "VM": "OpaqueRef:443efe69-7025-4a33-adab-51818258af24"
      }
    ]
  },
  "message": "DEVICE_ALREADY_EXISTS(0)",
  "name": "XapiError",
  "stack": "XapiError: DEVICE_ALREADY_EXISTS(0)
    at Function.wrap (/opt/xo/xo-builds/xen-orchestra-202205260849/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xo/xo-builds/xen-orchestra-202205260849/packages/xen-api/src/transports/json-rpc.js:37:27
    at AsyncResource.runInAsyncScope (node:async_hooks:202:9)
    at cb (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xo/xo-builds/xen-orchestra-202205260849/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

This has (unfortunately) 10 hard drives and 2 NICs. I can't see anywhere in XO where I can specify the MAC when I am importing the VM.

]]>https://xcp-ng.org/forum/post/50507https://xcp-ng.org/forum/post/50507Fri, 24 Jun 2022 20:13:24 GMT<![CDATA[Reply to Importing OVA - “Device Already Exists” on Tue, 21 Jun 2022 07:22:37 GMT]]>I suspect it's due to a similar MAC address 🤔

Do you have a more complete log in Settings/logs?

]]>https://xcp-ng.org/forum/post/50340https://xcp-ng.org/forum/post/50340Tue, 21 Jun 2022 07:22:37 GMT