Hey thanks for working on XCP-ng Center -- I find it a really useful tool.

Is this a README that describes how your project differs from XenCenter.

FWIW -- I had a similar problem with VMs going randomly down -- it wasn't windows but various BSD and Linux VM's. Sometimes they would run a few days, other times they would lock up every other day. Logs didn't help because when the VM locked, logs were not written. I even had the xcp-ng installation lock a few times, although it was usually on of the VMs. I started searching for faulty hardware and eventually SMART tested all the drives and mem86 the RAM. Turns out I had some bad RAM modules which I later RMA'd. With new RAM (after after thoroughly testing it), I haven't had any lock ups. I'm not sure this will help you at all.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning.

Thanks for update and the patch.

@nikade Hey thanks for for the link. I ended up just using a LetsEncrypt cert rather than self signed. I think had to add a DNS host override on my router to associate the Local LAN address of the xo server with the domain name of the server contained in the certificate -- Like 10.0.1.50 ---> xo.example.com. Thanks for pointing me in the right direction on this one.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning.

Thanks for update and the patch.

@olivierlambert

I'm ok with RTFM.

@olivierlambert
Hey thanks a lot -- that did the trick.

Just to be clear on my end -- when should a restart the toolstack?

Hi I'm running xcp-ng 8.2 and I've been doing so for a long time. Yesterday I received a notification about missing pool patches (with X0) and I installed chose the option to install the missing pool patches. In addition, I performed package upgrades of all the VMs (either apt for Ubuntu VMs or pacman for Arch VMs). One of my Arch VMs now fails to start and I'm receiving the error:

vm.start
{
  "id": "98a8dc5a-66f4-a475-ec2a-3de2df439629",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "FAILED_TO_START_EMULATOR",
  "params": [
    "OpaqueRef:d091d6c6-168a-4f6a-b365-c54cac642031",
    "domid 28",
    "QMP failure at File \"xc/device.ml\", line 3328, characters 71-78"
  ],
  "call": {
    "method": "VM.start",
    "params": [
      "OpaqueRef:d091d6c6-168a-4f6a-b365-c54cac642031",
      false,
      false
    ]
  },
  "message": "FAILED_TO_START_EMULATOR(OpaqueRef:d091d6c6-168a-4f6a-b365-c54cac642031, domid 28, QMP failure at File \"xc/device.ml\", line 3328, characters 71-78)",
  "name": "XapiError",
  "stack": "XapiError: FAILED_TO_START_EMULATOR(OpaqueRef:d091d6c6-168a-4f6a-b365-c54cac642031, domid 28, QMP failure at File \"xc/device.ml\", line 3328, characters 71-78)
    at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xen-orchestra/packages/xen-api/src/transports/json-rpc.js:36:27
    at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
    at cb (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:464:21)
    at process.topLevelDomainCallback (node:domain:152:15)
    at process.callbackTrampoline (node:internal/async_hooks:128:24)"
}

I actually went through the process of restoring a delta backup of this VM, and the restored delta backup has the exact same error, so I tending to think this is a problem with the hypervisor and not the actual VM. I've seen errors similar to this listed in other posts here on the forum, however it seems invariably there are posts saying -- yea --- this error message really needs to be more specific in exposing the underlying problem. I've tried ejecting v-CDR - xe vm-cd-eject --multiple however this command didn't exactly help. I'm booting via bios.

Here is my screenshot:

The listed containers don't exist on the host anymore.

@Rocky

I'm a little confused I guess. I have a PIF section. There is nothing under my Private Network area.

@Rocky
Yea it really stinks b/c I can't upload screenshot

So within XO
Home->Hosts-> Pick your Host
Choose Network
The third column is VLAN. You could type you VLAN information here.

However the only question I would have is what exactly do you want to tag, and what don't you want to tag. I believe if you typed in VLAN 999 for example, this would represent untagged traffic on this network.

@Rocky
What did you try. You can use XO or XenCenter.

All I have is a container tab. I tried to upload a jpeg screenshot but for some reason your forums isn't taking it and I'm getting a lot of pop up errors trying to insert the image. I followed the instructions linked by @jmccoy above. I already had an existing VM. Do you have any additional instructions?

By the way -- the error on the image upload was the following:

Something went wrong installing the "sharp" module /lib64/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/share/nginx/html/forum/node_modules/sharp/build/Release/../../vendor/lib/libpng16.so.16) - Remove the "node_modules/sharp" directory then run "npm install --ignore-scripts=false --verbose" and look for errors - Consult the installation documentation at https://sharp.pixelplumbing.com/install - Search for this error at https://github.com/lovell/sharp/issues

@jmccoy555

I tried the method you linked to with github. I was excited at first when I saw the containers tab in the UI. Later I created a number of docker containers and such within the VM. I came back later to the XO UI and saw none of the new containers. This feature seems a little bit borked to me.