Importing OVA - “Device Already Exists”
-
@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.
-
@planedrop are you importing this OVA from VMware out of curiosity?
-
@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.
-
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)
-
@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.
-
Please open a ticket so we can see in more depth what would be the best options
-
@olivierlambert Will do! I will try to do that today, might be next week though, busy week so far at work lol.
Thanks!
-
No worries, next week is fine
Busy here too 
-
@olivierlambert Just so you are aware, I just sent in a ticket for it a few minutes ago.
Thanks again for the help!
-
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.
-
@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.
