Error importing vhd or VM
-
@olivierlambert
steps are?- copy vhd to Xen local disk
- run command
xe vdi-imporrt "name".vhd
-
xe vdi-import uuid=uuid_of_vdi filename=filename_to_import_from --progress
-
import is ok
-
Good, then it's maybe your XO build. Could you try on a fresh XOA fully up to date on
latest
? -
@olivierlambert
XOA or XO form source ? -
I specifically said "XOA", so it's XOA There's no "latest" on XO from the sources.
-
@olivierlambert
For this I need to do a little more work, it gives the same error on import for xoa_unified.xva.
I'm going to bring the XOCE to a working version so I can import the xva -
You can deploy XOA without XO. See https://xen-orchestra.com/#!/xoa for example.
-
@olivierlambert
I have no internet for this network -
Then use
xe
CLI to import manually the XVA. But you'll need to update XOA with an internet access, in order to be onlatest
version. -
I managed to import it with XCP-ng Center (it was easier that way). After the update to latest, the same problem.
xo-server 5.109.0 xo-web 5.111.0Edit:
Downgrade to stable the same problem, but after 2 minutes of transfer
xo-server 5.107.5 xo-web 5.109.0 -
Is it possible to have access to this VHD file?
-
@olivierlambert
Ill share this vhdOn XOA stable I exported the VM and imported and all is ok, but on XOA I cant export VHD file ( no options)
Edit:
On XOA latest, I exported the VM (xva) and imported with no success -
You can export a VHD in XO. On the SR/disk tab, you should have an "export" icon to get the VHD.
-
@olivierlambert
This is what I have on XO on SR/disk tab
And this on XOCE
-
Yes, that's the export button. Are you on XOA Free for the first screenshot?
-
@olivierlambert
yes, I use XOA Free -
Can you try on XOA in trial? (if you trial expired, PM me your registered email so I can extend it)
-
I don't know how, but:
- XOA trial export can be imported with XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513
- XOCE export can not be imported with XOA trial
- XOA trial export can not be imported with the same XOA trial
I tested this 3 times with the same result
Edit:
I update XOCE in this morning and:- XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513 export, now can be imported with XOCE same commit, but not with XOA trial
- XOCE commit 675405f7ace55411b1ca0bbed8b9e31504fcc387 export can be imported with XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513, but not with XOA trial
I'll downgrade to XOCE commit 675405f7ace55411b1ca0bbed8b9e31504fcc387 to see what happens when I import XOCE commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513 export
Edit2:
It seems that the problem no longer appears after the commit cf4a1d7d40a16f08122ce7487dce7c8ab9d73513, for now
I still can't import with XOA trial, both VMs (XOA and XOCE) are on the same server. -
With commit 9ff305d5db2028c989df4b362db828f5bbb5b1b3, I get this error and can't export VM or VHD
HTTP handler of vm.import undefined { "message": "Xapi#watchTask() requires events watching", "name": "Error", "stack": "Error: Xapi#watchTask() requires events watching at Xapi.watchTask (/opt/xen-orchestra/packages/xen-api/src/index.js:691:13) at Xapi.createTask (/opt/xen-orchestra/packages/xen-api/src/index.js:636:10) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) at process.callbackTrampoline (node:internal/async_hooks:130:17) at Xapi._importVm (file:///opt/xen-orchestra/packages/xo-server/src/xapi/index.mjs:662:21) at Xapi.importVm (file:///opt/xen-orchestra/packages/xo-server/src/xapi/index.mjs:795:48)" }
And I get this on tasks