FAILED_TO_START_EMULATOR restarted Xen stack tools and rebooted the host
-
Thanks for the update, but XOA free won't cover backups which is necessary.
-
Then, how do you handle backup with VMware Essential kit?
-
@shakeel
Importing linux VM from another virtualization system is a more complex thing.
First of all, you must remove the driver packages specific to the initial virtualization.
In the second, you have to rebuild the kernel and initramfs. Now you will have different names of the HDD and possibly a new partitions name or soft raid.
After doing this you should no longer have kernel panic and it should work.
I recommend using a live CD, specific to the linux version.On Windows it is easier with a sysprep or more difficult with a driver injection, especially xenbus. Same problem here, different HDD name.
I managed to migrate, like this, from Hyper-v, VMWare, VirtualBox to Xen
If it doesn't work directly, you can try from initial virtualization then to VirtualBox and then to Xen. -
We can use HDP license free for VMWare & Hyper-v backup.
-
Thanks, let try it and check.
-
@shakeel said in FAILED_TO_START_EMULATOR restarted Xen stack tools and rebooted the host:
We can use HDP license free for VMWare & Hyper-v backup.
So you are using a 3rd party tool and then compare to XCP-ng/XO pricing where everything is included
If you want assistance before and while running in production, please be serious and consider contacting us (as I said, there's contact forms on our multiple websites, like https://vates.fr and https://xcp-ng.com).
-
@olivierlambert
We are very serious but we don't need all those features, our requirement is very simple- hypervisor with basic functionality + Backup that it.In this case VMWare essential is very cheap compared to Xcp-ng. If any option available like above ready to get it on board now.
VMWare essential per host /year its - USD 78
Xcp-ng per host/year its USD- 600 -
What you actually did:
- ask on a community/public forum for free assistance (while using a community supported only client for XCP-ng, so likely without reading any part of the doc): it's fine but you get what you paid for, ie: $0.
- complain it doesn't work and said you'll go back to VMware
- not even taking the time to look at our pricing BEFORE. So showing that you aren't even considering it despite doing production stuff.
- not even trying to contact us (so we could have sorted that together)
- comparing prices of different things (I bet you also missed this blog post)
No, really it's not serious.
If you want to move forward and consider using it in production, now you know what to do: we are happy to discuss and see how we can help. Since you avoided that from the start, if you still don't do it, I will believe you came here thinking you can run your production for free while counting only on the community and rant about the fact it doesn't work. This is not the way to do things around here.
-
@shakeel Don't you still have to pay the Yearly 600$ licence for essential? and 308$ for each support ticket? or 980$ for yearly support?
-
We wanted test first since currently vms are on Esxi to move to xcp-ng. If everything goes well we planned to move production by purchasing the pro-support/licenses.
Later when budgeting, management wanted to see and compare prices with different products (as per our requirement).
As per our very small environment concerned we won't get any issues with VMWare if any may be 1 call per year. if any issue VMWare support its per call basis USD 49 an hour.
Also Xcp-ng we won't get issues only issues we will get only when migrating or converting VMs from VMware to xcp-ng.
