Posts made by msagautam

Hi Guys,
I am not sure whether these are XOA issues or XCP-ng issues. I am experiencing the following issues when I tried to backup a Windows 7 VM:

1. When I use "offline snapshot" method to perform a backup, I got:

Error: VM_LACKS_FEATURE(OpaqueRef:6b7d4cd0-d8e9-414c-a865-66563ba8c27d)

2. Then when I shutdown windows manually, then tried to perform backup, I got:

VM_HAS_VUSBS(OpaqueRef:6b7d4cd0-d8e9-414c-a865-66563ba8c27d)

3. Then now, when I detached USB Passthrough (USB NIC for optional remote VPN access) to this VM, then when I tried to perform a backup, I get:

Error: SR_BACKEND_FAILURE_82(, Failed to snapshot VDI [opterr=Command ['/usr/bin/vhd-util', 'query', '--debug', '-vsf', '-n', '/dev/VG_XenStorage-f70a9d3e-5f10-8788-6f0c-16f592062c23/VHD-e34d8d0a-8fa6-4b25-b88c-4b75b814ebdd'] failed (error opening /dev/VG_XenStorage-f70a9d3e-5f10-8788-6f0c-16f592062c23/VHD-e34d8d0a-8fa6-4b25-b88c-4b75b814ebdd: -2): No such file or directory], )

I was wondering whether anyone has experienced these issues? If you have, then how did you end up backing up your VM?
By the way, with vanilla windows 7 installed on a new VM I could perform both delta backup and basic backup. Then after windows installed all the updates, I see this 3rd issue
I need the updates installed as some of the accounting software requires these windows updates.

@cg it works on restored VMs from pre-fix backups.
I haven't tested post fix backups yet. However, it also works on newly installed VMs.

Are you asking whether I can auto-power on the restored VMs from the latest commit of orchestra?
Answer: Yes, it works!
Reason: Looks like the parameter was not available before and julien-f has fixed it by adding the parameter in this commit: https://github.com/vatesfr/xen-orchestra/commit/e171d8ed0e786772c9ccdb7dd4127d42faae141a
Thank you all!

0 julien-f committed to vatesfr/xen-orchestra

fix(xo-server/vm.set): add `auto_poweron` to params

Related to b8524732ce5fc466ef73664ff02cd4e09fca7ad9

Fixes #4295

I backed up the server 3 days ago, which is when e171d8e commit has been made. So it is most likely that I have cloned from github and installed xo-server before this fix.
To answer oliver's question, the restore would still have the issue because the xo-server built is before the fix. So I will have to fetch the update and rebuild xo-server again, and then I have to backup for future restores.

@olivierlambert Thank you.
It looks like the backup generated from a different server does not work well for options such as "auto power on" when restored on a new server.
But if I just build xo from source in a new VM on the new server, "auto power on" works perfectly.

@olivierlambert I am building from source following this link: "https://xen-orchestra.com/docs/from_the_sources.html"
which refers to the following

git clone -b master http://github.com/vatesfr/xen-orchestra

Should I be cloning off a different repo instead?

Thanks, I am new to xcp-ng, XenOrchestra and these forums. Please forgive my newbie faux pas.

I found this when I hit the eye button:

m.set
{
  "auto_poweron": true,
  "id": "f39bfc1d-0e99-69ef-833c-db12c9490c6d"
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "code": null,
        "reason": "strict",
        "message": "should not contains property [\"auto_poweron\"]",
        "property": "@"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Object.factory [as invalidParameters] (/home/gautam/xen-orchestra/packages/xo-common/src/api-errors.js:21:31)
    at Xo.checkParams (/home/gautam/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:71:17)
    at /home/gautam/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:277:18
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/home/gautam/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:38:103)
    at _next (/home/gautam/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:40:194)
    at tryCatcher (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/promise.js:517:31)
    at Promise._settlePromise (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/promise.js:574:18)
    at Promise._settlePromiseCtx (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/promise.js:611:10)
    at _drainQueueStep (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/async.js:142:12)
    at _drainQueue (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/home/gautam/xen-orchestra/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5)"
}

There is not much information in the logs:

I did three clean installs of the xcp-ng and XO on 3 different hardware.
So far I am unable to get Auto Power on enabled through XO.
I keep getting "invalid parameters" such as here:

When I set auto power on from xcp-ng through cli, then I cannot disable auto power on through Orchestra. I get the same message.

Is there something I need to configure to get this option enabled?