You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.

You need a space between the URL and the user name.

@hvilches said in XCP-ng Center 20.03.00 released:

is-a-template ( RW): true

Looks like this is the culprit...

@flipsidecreations There's a new Netdata plugin, which appears to only be available in XOA Premium edition. It doesn't appear that you will be able to enable the new Advanced Live Telemetry using the versions you are currently running.

@olivierlambert The "quick deploy" via web worked correctly this time

Congrats!

Have you tried compress=zstd?

See these commits --

https://github.com/vatesfr/xen-orchestra/commit/270185d9dcaaad00899722112058fccda814d505

https://github.com/vatesfr/xen-orchestra/commit/bce0bf05e587ca2df46fd78b57d4553a03887b92

0 julien-f committed to vatesfr/xen-orchestra

feat(xen-api/examples/export-vm): add --gzip and --zstd

0 badrAZ committed to vatesfr/xen-orchestra

feat(xo-server): provide zstd compression for VM export (#3878)

See #3773

Are you using XOA or XO from sources? What version?

Edit: It fails for me as well. Here are the details from the logs --

Jun 06 13:55:04 ubuntutest xo-server[729]: 2020-06-06T13:55:04.705Z xo:xapi DEBUG Creating VM SexiLog
Jun 06 13:55:04 ubuntutest xo-server[729]: 2020-06-06T13:55:04.791Z xo:xapi DEBUG Creating VDI Hard disk 1 on Local storage
Jun 06 13:55:04 ubuntutest xo-server[729]: 2020-06-06T13:55:04.792Z xo:xapi DEBUG Creating VDI Hard disk 2 on Local storage
Jun 06 13:55:04 ubuntutest xo-server[729]: 2020-06-06T13:55:04.793Z xo:xapi DEBUG Creating VIF for VM SexiLog on network Pool-wide network associated with eth0
Jun 06 13:55:05 ubuntutest xo-server[729]: 2020-06-06T13:55:05.195Z xo:xapi DEBUG Creating VBD for VDI Hard disk 1 on VM [Importing...] SexiLog
Jun 06 13:55:18 ubuntutest xo-server[729]: 2020-06-06T13:55:18.640Z xo:xapi DEBUG Creating VBD for VDI Hard disk 2 on VM [Importing...] SexiLog
Jun 06 13:55:18 ubuntutest xo-server[729]: 2020-06-06T13:55:18.656Z xo:xo-server WARN possibly unhandled rejection {
Jun 06 13:55:18 ubuntutest xo-server[729]:   error: TypeError: Cannot read property 'grainLogicalAddressList' of undefined
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract.<anonymous> (/opt/xen-orchestra/packages/xo-server/src/xapi/index.js:1461:17)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract.apply (events.js:315:20)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/src/configure.js:95:17)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract.onheader [as _onheader] (/opt/xen-orchestra/node_modules/tar-stream/extract.js:180:10)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract._write (/opt/xen-orchestra/node_modules/tar-stream/extract.js:249:8)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract._continue (/opt/xen-orchestra/node_modules/tar-stream/extract.js:212:28)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at oncontinue (/opt/xen-orchestra/node_modules/tar-stream/extract.js:67:10)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract.ondrain (/opt/xen-orchestra/node_modules/tar-stream/extract.js:87:5)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract._write (/opt/xen-orchestra/node_modules/tar-stream/extract.js:249:8)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Extract._continue (/opt/xen-orchestra/node_modules/tar-stream/extract.js:212:28)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at oncontinue (/opt/xen-orchestra/node_modules/tar-stream/extract.js:67:10)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Source.onunlock (/opt/xen-orchestra/node_modules/tar-stream/extract.js:73:24)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Source.apply (events.js:315:20)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at Source.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/src/configure.js:95:17)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at endReadableNT (/opt/xen-orchestra/node_modules/tar-stream/node_modules/readable-stream/lib/_stream_readable.js:1094:12)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at processTicksAndRejections (internal/process/task_queues.js:84:21)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at runNextTicks (internal/process/task_queues.js:66:3)
Jun 06 13:55:18 ubuntutest xo-server[729]:       at processImmediate (internal/timers.js:429:9)
Jun 06 13:55:18 ubuntutest xo-server[729]: }

That looks like an "orphaned" disk, which should be fine to delete. You can view any existing instances of these by selecting "Orphaned disks" from the filter in the bottom right.

If you experience these on every backup, then there's something off in your setup.

@amp88 FWIW, there's an open issue on GH dealing with this.

@RicknTX1 Been there, experienced the same issue.

See here for more details.

You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.

Do you have useSudo configured in the xo-server configuration file?

https://xen-orchestra.com/docs/installation.html#sudo

@Strebor AFAICS, xe vm-import doesn't offer an option to specify the compression level, so I am going to assume that it handles this automatically.

Have you tried compress=zstd?

See these commits --

https://github.com/vatesfr/xen-orchestra/commit/270185d9dcaaad00899722112058fccda814d505

https://github.com/vatesfr/xen-orchestra/commit/bce0bf05e587ca2df46fd78b57d4553a03887b92

0 julien-f committed to vatesfr/xen-orchestra

feat(xen-api/examples/export-vm): add --gzip and --zstd

0 badrAZ committed to vatesfr/xen-orchestra

feat(xo-server): provide zstd compression for VM export (#3878)

See #3773

You would make the change under Settings > Servers. Only the pool master should be listed there.

@Psynapsx said in Power on mode greyed out:

All I did I few days ago is that I changed my pool master from server3 to server4

Did you update XO as well so that it connects to the new pool master?

This is the "bible" for installing from source -- https://xen-orchestra.com/docs/from_the_sources.html. If you installed following these steps, then you would want to continue the same process and perform the steps under Updating.

FWIW, you may have to perform additional steps to get the VM fully updated / working, such as --

• Update Node to latest LTS version
• Install any new dependencies

You can also just export the current XO config, build a fresh VM, and then import the config from the old install.

@maxcuttins I could be wrong, but I imagine that existing Windows 7 VMs will continue to function just fine after upgrading to CH 8.2 or XCP-ng 8.2.

@dsiminiuk You should only be adding the pool master in XO, not the slaves.