I came across this and the solution I upvoted i.e. renaming in pool view, works for me. However, I would like to +1 the idea @Forza put in his post. Cause organizing it all can get quite confusing. XOA being the excellent tool that it is, has this lacking.

For those who come across this and feel discouraged? Do please mention your needs to the team here! They are VERY good at putting these kinds of things on the roadmap if there is a need/want for it!

For myself, I use a spreadsheet to keep track of networks, hosts and pools. I do not rely on XOA alone. Which tbh is probably best practice anyway, in case a backup fails or the world blows up.

@dgmcdona I am using both the XOA enterprise and the community edition.

I updated the community edition of XOA to the newest version using the script that is on github , I linked to the script in my last post. Does that pull in the fix or do I have to apply a patch within XOA? I am confused as to what a github pull request is.. I am a noob at this clearly. I do run the community and it's updated. What else do I need to do to apply the patched code to my XOA community instance?

Thanks!

Greetings all

browser - Brave (Chromium 85.0.4183.102)
XOA community edition - updated today via script

xo-server 5.66.2
xo-web 5.70.0

I am also having this issue. It's an ova file from virtualbox - I created it back in 2018 , if that is part of the problem?

Here is my error log:

bubbles: false
cancelBubble: false
cancelable: false
composed: false
currentTarget: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
defaultPrevented: false
eventPhase: 0
isTrusted: true
lengthComputable: true
loaded: 0
path: []
returnValue: true
srcElement: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
target: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
timeStamp: 379669.2550000007
total: 3307068416
type: "error"
__proto__: ProgressEvent
(anonymous)	@	index.js:224
o	@	asyncToGenerator.js:17
(anonymous)	@	asyncToGenerator.js:30
Promise.then (async)		
o	@	asyncToGenerator.js:27
(anonymous)	@	asyncToGenerator.js:35
t	@	_export.js:36
(anonymous)	@	asyncToGenerator.js:14
(anonymous)	@	index.js:216
(anonymous)	@	index.js:276
(anonymous)	@	utils.js:174
t.exports	@	_arrayEach.js:15
t.exports	@	forEach.js:37
r.mapPlus	@	utils.js:174
(anonymous)	@	index.js:264
o	@	asyncToGenerator.js:17
(anonymous)	@	asyncToGenerator.js:35
t	@	_export.js:36
(anonymous)	@	asyncToGenerator.js:14
(anonymous)	@	index.js:237
(anonymous)	@	index.js:206
Promise.then (async)		
value	@	index.js:174
executeOnChange	@	LinkedValueUtils.js:130
(anonymous)	@	ReactDOMInput.js:239
o	@	ReactErrorUtils.js:24
s	@	EventPluginUtils.js:83
executeDispatchesInOrder	@	EventPluginUtils.js:106
d	@	EventPluginHub.js:41
p	@	EventPluginHub.js:52
t.exports	@	forEachAccumulated.js:22
processEventQueue	@	EventPluginHub.js:250
(anonymous)	@	ReactEventEmitterMixin.js:15
handleTopLevel	@	ReactEventEmitterMixin.js:25
p	@	ReactEventListener.js:70
perform	@	Transaction.js:141
batchedUpdates	@	ReactDefaultBatchingStrategy.js:60
batchedUpdates	@	ReactUpdates.js:95
dispatchEvent	@	ReactEventListener.js:145

I do see this line

DOMException: The requested file could not be read, typically due to permission problems

What perms do I need to set on the ova to let it read this ova and import? I regret that I can not share the ova file as it is private but I can try and debug perhaps?

Here is the error log from XOA Enterprise (I run both VMs) when trying to import the same file.
xo-server 5.64.1
xo-web 5.67.0

bubbles: false
cancelBubble: false
cancelable: false
composed: false
currentTarget: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
defaultPrevented: false
eventPhase: 0
isTrusted: true
lengthComputable: true
loaded: 0
path: []
returnValue: true
srcElement: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
target: FileReader {readyState: 2, result: null, error: DOMException: The requested file could not be read, typically due to permission problems that have …, onloadstart: null, onprogress: null, …}
timeStamp: 23579.565000000002
total: 3307068416
type: "error"
__proto__: ProgressEvent

Anything else I can provide to help debug, lmk. Thank you.

Edit - I attempted to import via the windows xen center and that also failed to import. I can attach logs if you tell me how, but I think xen center is another dev team. I might need to somehow convert my ova file from 2018 to a newer standard somehow?

The private ova file is a debian 8 system with the default gui install. It has a VMDK as it's disk format.. I am fairly certain I would have set that up as dynamically allocated.

@MichaelCropper
I was struggling with this also. A class I am taking I wanted to set up a CentOS 8 VM.
I used CentOS 8.1.1911-x86_64-boot.iso for the install.
Using the graphical installer I just accepted the default group which for this ISO is "Server with GUI"
I also installed the "Development Tools" package (not that I think that matters for this issue)
When I booted I got the "black screen of death" (it now has official name lol)
I did a shutdown graceful shutdown of VM.
I went to the "Advanced" tab and switched from VGA 8 to VGA 16 (VGA was on by default).
When I created the VM I used the CentOS 8 template btw.
I rebooted the screen and.. yup I got the GUI login screen!

I hope this helps.

ps make sure you install those xen tools right away and then reboot.. otherwise , it's painful.