Cannot export VM in .ova file

olivierlambert

Hi!

Let me clear some things.

@dan2462 said in Cannot export VM in .ova file:

@olivierlambert

Sure, but why cant you guys make it "trivial" in XCP-ng Center? You praise XO so much, but one, it comes with limitations, 2nd its another 3rd party software and 3rd to get full capability it has to be paid, and lastly in order for it to be up to date you need it to have internet access given the license etc.

Because XCP-ng Center is not maintained by Vates, it's only community maintained. We discourage usage of it because there's only one person maintaining it on his freetime, @borzel : he's kind to do this, but he's alone. If you want to assist him and improve XCP-ng Center, go ahead.

It's far less 3rd party than XCP-ng Center which is mainly a clone of XenCenter for Citrix.

Also, Xen Orchestra is fully Open Source. So your statement about licensing is just plain wrong 3 times: If you don't want to pay, you can. If you have a paid license, it works offline too. You can also use XOA Free.

In short, when you build a closed end system its best to take in what you know or can open and double check. I like XCP-ng and I think you guys have done great job and will hire your system admin in the future but for now certain things have to be achieved and I prefer less systems and those few to work as stated.

I strongly recommend Xen Orchestra for a lot of reasons: XCP-ng team is working closely with Xen Orchestra, allowing new features to be added both in server and client. We can test it extensively interactions between those two. It's also completely independent from Citrix choices, which is far better.

We have plans for a XO Lite client that will be embed on XCP-ng, so we can remove the last use case for XCP-ng Center.

peder

@dan2462
Plug the USB stick into your XCP-ng server and run

dmesg | tail 
# You should see "sdb: sdb1" or something similar at the bottom of the screen
mount /dev/sdb1 /mnt
cd /mnt
# Make sure you've mounted the correct device and partition :
df -h . 
# You should see that it's the expected USB size

If that's the case run the xe commands to save on the USB.
When that's done you run

cd /root
sync
umount /mnt

Then it's safe to remove the USB

dan2462

@peder

Thank you. Unfortunately, that machine is in datacenter so dont have physical usb access.

Nevertheless, I found a way to do the conversion. Seems as XenConvert 2.3.1 is capable of doing it, however, its only that version that does it, the rest are all different.

Therefore, issue resolved for conversion, but i'm still wondering if im the only one that had that issue or is it quite common given the system version I have to xcp and the center.

Edwardwsr

Hi Dan2462, I would like you to go for the following steps. In the star just choose the virtual machine and pick the option that says File > Export to OVF. Now add a name for the OVF file and mention a directory in which you need to save it. Here mention if you want to export the virtual machine as an OVF, a folder with individual files, or as an OVA, a single-file archive. At the end press Export to start the procedure of OVF export. This step will take some time and a status bar lets you know about the progress of the export process. Apart from that, https://appuals.com/export-import-vm-oracle/ this website would be really helpful for you in getting to know much more about it. I hope that by following these steps you would be able to resolve this issue.

EdRoxter 0

Sorry for grave digging here, but since this answer ranks pretty high in the Google results, I thought I might add a possible solution:

During the export wizard in XCP-ng Center, you're being asked for the network configuration of the Transfer VM. As for my observations, two things are pretty vital here:

The network you choose to place the Transfer VM's virtual interface in must be reachable from your computer/XCP-ng center.
Enter a static IP configuration, DHCP has never worked for me, even though a DHCP server is running in the selected network.

Hope this helps some!

A Former User

Dear,
with a brand-new 8.2 xcp-ng server installation I was able to export ova from XCP-NG Center.
After upgrading it with latest patches (yum update) I'm not able to to export back ova.
I've done this test both on my production server and also installing it in a new system from scratch.

I've tried using both DHCP and static IP. no luck.

Thanks in advance for any feedback.

The log reports is the following:

2022-02-27 20:40:18,971 INFO  Audit [Main program thread] - Operation started: ExportApplianceAction: xcpserver: VM bdc057c5-d2c4-a3ff-e307-fe510de32146 (VM1): Pool 0bc5c93d-6cfc-811a-cf85-0b72732ca6e5 (xcpserver): Host 7314e7fb-cd5f-481b-a464-86b3acc3ae5c (xcpserver): 
2022-02-27 20:40:24,867 ERROR XenOvfTransport.iSCSI [30] - Failed to start Transfer VM.
There was a failure communicating with the plug-in.
2022-02-27 20:40:24,868 ERROR XenOvfTransport.Export [30] - Failed to transfer virtual disk C:\Backup\VM1\6ad97f18-51e4-45ed-b088-bfa2affc1b87.vhd
System.Exception: Failed to start the Transfer VM. ---> XenAPI.Failure: There was a failure communicating with the plug-in.
   at XenAPI.JsonRpcClient.Rpc[T](String callName, JToken parameters, JsonSerializer serializer)
   at XenAPI.Host.call_plugin(Session session, String _host, String _plugin, String _fn, Dictionary`2 _args)
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   --- End of inner exception stack trace ---
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.iSCSI.Connect(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.Export._copydisks(EnvelopeType ovfEnv, String label, String targetPath)
2022-02-27 20:40:24,877 ERROR XenOvfTransport.Export [30] - Export failed
System.Exception: Failed to transfer virtual disk C:\Backup\VM1\6ad97f18-51e4-45ed-b088-bfa2affc1b87.vhd. ---> System.Exception: Failed to start the Transfer VM. ---> XenAPI.Failure: There was a failure communicating with the plug-in.
   at XenAPI.JsonRpcClient.Rpc[T](String callName, JToken parameters, JsonSerializer serializer)
   at XenAPI.Host.call_plugin(Session session, String _host, String _plugin, String _fn, Dictionary`2 _args)
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   --- End of inner exception stack trace ---
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.iSCSI.Connect(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.Export._copydisks(EnvelopeType ovfEnv, String label, String targetPath)
   --- End of inner exception stack trace ---
   at XenOvfTransport.Export._copydisks(EnvelopeType ovfEnv, String label, String targetPath)
   at XenOvfTransport.Export._export(Session xenSession, String targetPath, String ovfname, String vmUuid)
2022-02-27 20:40:24,877 ERROR XenAdmin.Actions.AsyncAction [30] - System.Exception: Failed to export. ---> System.Exception: Failed to transfer virtual disk C:\Backup\VM1\6ad97f18-51e4-45ed-b088-bfa2affc1b87.vhd. ---> System.Exception: Failed to start the Transfer VM. ---> XenAPI.Failure: There was a failure communicating with the plug-in.
   at XenAPI.JsonRpcClient.Rpc[T](String callName, JToken parameters, JsonSerializer serializer)
   at XenAPI.Host.call_plugin(Session session, String _host, String _plugin, String _fn, Dictionary`2 _args)
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   --- End of inner exception stack trace ---
   at XenOvfTransport.iSCSI.StartiScsiTarget(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.iSCSI.Connect(Session xenSession, String vdiuuid, Boolean read_only)
   at XenOvfTransport.Export._copydisks(EnvelopeType ovfEnv, String label, String targetPath)
   --- End of inner exception stack trace ---
   at XenOvfTransport.Export._copydisks(EnvelopeType ovfEnv, String label, String targetPath)
   at XenOvfTransport.Export._export(Session xenSession, String targetPath, String ovfname, String vmUuid)
   --- End of inner exception stack trace ---
   at XenOvfTransport.Export._export(Session xenSession, String targetPath, String ovfname, String vmUuid)
   at XenOvfTransport.Export.Process(String targetPath, String ovfname, String[] vmUuid)
   at XenAdmin.Actions.OVFActions.ExportApplianceAction.Run()
   at XenAdmin.Actions.AsyncAction.RunWorkerThread(Object o)
2022-02-27 20:40:24,878 WARN  Audit [30] - Operation failure: ExportApplianceAction: xcpserver: VM bdc057c5-d2c4-a3ff-e307-fe510de32146 (VM1): Pool 0bc5c93d-6cfc-811a-cf85-0b72732ca6e5 (xcpserver): Host 7314e7fb-cd5f-481b-a464-86b3acc3ae5c (xcpserver): Disconnecting virtual disk 6ad97f18-51e4-45ed-b088-bfa2affc1b87.vhd ...

olivierlambert

I wouldn't rely on XCP-ng Center for that. Xen Orchestra will have OVA export in the April release. VMDK export is already there

A Former User

@olivierlambert thanks, OVA export in april will be a very great feature that complitely allow me to forget xcp-ng center

olivierlambert

Indeed, we are close to finish it, maybe even March release Hang on!

rowie

@olivierlambert
and how to export the xo appliance with xo?

olivierlambert

Like any other VM?

rowie

@olivierlambert
playing arround since hours to migrate my xcp-ng (running on my HP Gen8 Microserver) to a bigger SSD.
cloning the disk with clonezille wasnt successfull so i decide to start from scratch.

Exporting xo with xcp-ng center -> pain in the ass
ex and importing vhd manually -> same pain in the ..

i am working since years with vmware and proxmox but this one was challenge ... such a "simple" think
now i have created a new vhd ... and copy the old xo vhd over it ... rescan .. works

i couldnt find a working tuto for doing this the right way ..

br,
rowie

olivierlambert

Maybe your question was not clear, you asked to export XO with XO, you didn't talk about XCP-ng at all It was a typo then, you meant XCP-ng?

rowie

@olivierlambert
yes, xcp-ng! sorry for confusing

xcp-ng Center isnt working great in such things right?

olivierlambert

XCP-ng Center isn't an officially supported client for XCP-ng in the first place, as per https://docs.xcp-ng.org/management/

rowie

@olivierlambert

ah, ok. that explains a lot!
What is the best way to migrate xcp-ng to a larger hard drive??

olivierlambert

Depends a lot on what you have available. IMHO, I consider the system as disposable, since you can export the metadata, reinstall and import the metadata again. Or backup your VM, reinstall, restore. Or migrate out to another host, reinstall, re-migrate the VMs.

So many possibilities, that all depends on your setup.