FAILED_TO_START_EMULATOR restarted Xen stack tools and rebooted the host

Darkbeldin

@shakeel Did you checked the Bios mode on the advanced tab of the VM because if you imported it your probably in Bios mode but you should be in UEFI

shakeel

@Darkbeldin

Checked its uefi.

Darkbeldin

@shakeel And if you go to Bios and try to boot?

shakeel

@Darkbeldin
Same error after changing to BIOS.

vm.start
{
  "id": "fcc92397-758f-3ac2-a773-73549b55d826",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "FAILED_TO_START_EMULATOR",
  "params": [
    "OpaqueRef:7eb34388-bb14-480b-85cf-f4bab84d3f3a",
    "domid 11",
    "QMP failure at File \"xc/device.ml\", line 3366, characters 71-78"
  ],
  "call": {
    "method": "VM.start",
    "params": [
      "OpaqueRef:7eb34388-bb14-480b-85cf-f4bab84d3f3a",
      false,
      false
    ]
  },
  "message": "FAILED_TO_START_EMULATOR(OpaqueRef:7eb34388-bb14-480b-85cf-f4bab84d3f3a, domid 11, QMP failure at File \"xc/device.ml\", line 3366, characters 71-78)",
  "name": "XapiError",
  "stack": "XapiError: FAILED_TO_START_EMULATOR(OpaqueRef:7eb34388-bb14-480b-85cf-f4bab84d3f3a, domid 11, QMP failure at File \"xc/device.ml\", line 3366, characters 71-78)
    at Function.wrap (/opt/xo/xo-builds/xen-orchestra-202208200304/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xo/xo-builds/xen-orchestra-202208200304/packages/xen-api/src/transports/json-rpc.js:37:27
    at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
    at cb (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xo/xo-builds/xen-orchestra-202208200304/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Darkbeldin

@shakeel

Have you tryed restarting the toolstack on your host? or even restart the host if possible?

shakeel

@Darkbeldin

Two days back I didn't it worked, again after reboot the VM its not starting and give same error FAILED_TO_START_EMULATOR.

Darkbeldin

@shakeel How did you imported ,the VM? in which format? Is it possible to get this VM to test it on my side?

shakeel

@Darkbeldin
Using OVA export from VMware and then OVA import into Xen Orchestra
VM size is big 700 GB

Darkbeldin

@shakeel Perhaps you have another host where you could try importing the Vm to see if you have the same behavior? did you uninstall VMware tools before exporting the VM?

shakeel

@Darkbeldin
Currently no other host available, I think VM tools is not uninstalled let try reboot the host again start the VM if starts i will remove vm tools and check.

Darkbeldin

@shakeel VMware tools should be removed before exporting and perhaps also install xen tools.
See the doc here: https://xcp-ng.org/docs/migratetoxcpng.html#from-vmware

shakeel

@Darkbeldin
Let do that and check.

shakeel

@shakeel

We are planning to re-import the VM and check.

Another issue we trying to import FMG_VM64_XEN-v7.2.1-build1215-FORTINET.out.CitrixXen "fmg.xva" and getting below error.

shakeel

@Darkbeldin
importing VM FMG_VM64_XEN-v7.2.1-build1215-FORTINET.out.CitrixXen "fmg.xva" and getting below error.

shakeel

@Darkbeldin

Eish... so many problems are there in xcp-ng noting works properly, thanks let us revert back to VM Ware thanks for the support.

olivierlambert

This is community support here, so people are helping on their free time, when they can. If you want true assistance, you should probably contact our pro support

shakeel

@olivierlambert

But before moving all our productions and purchase pro-support/licenses we want to test. But Xcp-ng has many problems no evaluation versions available in test phase we are getting so many issues how can we go to production/Purchase pro -support without testing. We are testing different hypervisors like VMWare, XCP-ng & Promax we preferred to test our Test workload on VMWare & XCP-ng to choose the best.

On Vmware elevation everything works like charm no issue, and they have evaluation all our Test VM's works very well all testing done, we had impression on xcp-ng decided to test if everything goes well we will have it on production but we didn't see any significance most of the VM's won't work, multipath won't work.
Only advantage xcp-ng of we see is Backup comes with XOA.

As far our environment concerned VM Ware Vshpere essential kit suits and is cheap(3 Hosts 2 cpus each + 1 Vsphere) is USD 686 for 3 years where as xcp-ng&XOA 1,440 per year licenses expensive and no guarantee workload will work.

And many problems are there in xcp-ng, who ever the customer they will first try it in Test environment if all well the they will buy/purchase licenses/pro-support.

Anyway thanks above are my points am not any competitor/promoting VMWare am normal customer who is looking for better product/support after seeing some videos of Lawrence System in Youtube thought of using the xcp-ng and use in production, product out sight looks good but lack customer satisfaction.

Thanks will appreciated if xcp-ng team will give solutions/support and pricing that guarantee to test our workload so I can demonstrate to our management and get it on board.

olivierlambert

But before moving all our productions and purchase pro-support/licenses we want to test.

That's exactly what we do with our pro support. We work together to assist you on building a PoC.

You should have contacted us directly to discuss options if it was meant to run in production with pro support

shakeel

@olivierlambert

Our requirement is very simple we want to move 2 VMs from an hosting provider which are hosted on Vmware Esxi to our Data center Suse Linux (Hana DB) & Windows server 2019 (App Server).

And import some VMs example ForitManager, then gradually create VM's based on new requirements and have backups.

olivierlambert

Please contact us for that. We can discuss a plan to help you build the PoC and get pro support only after we validated it together. If at some point you are considering having support obviously