Posts made by kevdog

@olivierlambert

Well damn -- you're right.

Well VM now up and running. Just have to figure out how networking works in this new copied VM. Thanks for help.

@olivierlambert

Here is my Home view screen -- the VM I'm trying to copy is called "Arch Time Machine". It's up and running on the original hypervisor. There are no running or halted VMs on the second hypervisor

@olivierlambert

Sorry both are 1TB -- I'll correct my prior post to reflect

Here is how I copied the VM --

I choose the SR (zfs disk on hypervisor #2) and chose zstd for compression.

@olivierlambert said in Question regarding copying of VMs within storage pool:

The VM should be visible on the second host, likely in a "halted" state.

Not exactly what I'm seeing here -- in fact I don't see any evidence of any halted VM -- probably because I did something incorrectly.

On the second hypervisor I running a 1Gb nvme drive which was partitioned during the installation process with partitions of /var/log, /boot, /efi, /, and SWP.

I have a second 1Gb SATA drive which I added as a zfs storage pool accessible as /mnt/tank.

Within the zfs pool I can see the copied VM (aedbfce5-7365-4d16-b39c-0b3c93a210f6.vhd).

Do I need to create a VM on the second host using this particular .vhd file?

So I've recently been blessed by building a second xcp-hypervisor. I'm trying to copy/recreate a VM on the second hypervisor which is located on the initial hypervisor.

I've added both the initial and second hypervisor to a pool. From within Xen Orchestra I selected the hypervisor I wanted to copy and selected the copy option and chose the destination to be the local zfs storage located on the second hypervisor. I waited about 30 min for VM to be copied.

Now what do I do? The copy operation completed -- how do I create the VM the second host using this copied image? Confused what to do at this point.

@lawrencesystems

Possibly I'm thinking about this all wrong, but I usually keep all my management interfaces on a different VLAN other than native. Perhaps the wrong approach.

Re: Change management network interface?

So I'm referencing the thread above.

I'm playing around with a new xcp-ng installation -- been awhile since I've done this -- amazing how much I forget after you get a system up and running.

Anyway I'm trying to set the management interface up using VLAN 40. I have no idea how to do this as it defaults to VLAN1. It's frankly very very awkward as it's not possible to specify a VLAN within the xcp-ng configuration screen.

I believe I was able to change the vlan management by connecting the new instance to my currently running XO server -- add a new tagged network associating it with the current XO host, and then the option suddenly appeared within the drop down list within the managment console terminal. (Hopefully that makes sense).

There is probably a way to do this via the command line, however the referenced command: xe host-management-reconfigure pif-uuid=<PIF_UUID> doesn't exactly have anything to do with VLANs that I can find. In fact the Citrix Documentation isn't very elusive about this either. I guess I'm looking to do this all at the command line, XO, or at the management console without having to jump back and forth between methods which makes the process clumsy.

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.

@julien-f

Ahh - very nice -- I guess the point of my post was pointless.

Thanks for help.

@julien-f

I reviewed your commit, however I don't understand your heading (remove TLS config to use native settings).

If not specified in the config.toml file, what are the native settings? Where are these specified?

@julien-f

Snippet of config.toml file:

# These options are applied to all listen entries.
[http.listenOptions]
# Ciphers to use.
#
# These are the default ciphers in Node 4.2.6, we are setting
# them explicitly for older Node versions.
ciphers = 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!SRP:!CAMELLIA'

# Tell Node to respect the cipher order.
honorCipherOrder = true

# Specify to use at least TLSv1.1.
# See: https:#github.com/certsimple/minimum-tls-version
minVersion = 'TLSv1.2'

secureOptions = null

#secureOptions = 117440512

At least for me including those options didn't work.

Oct 27 14:54:32 ubuntuxo systemd[1]: Started XO Server.
Oct 27 14:54:33 ubuntuxo xo-server[103642]: ✖ Unexpected character, expected "nan" at row 115, col 18, pos 3784:
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 114:
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 115> secureOptions = null
Oct 27 14:54:33 ubuntuxo xo-server[103642]:                       ^
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 116:
Oct 27 14:54:33 ubuntuxo xo-server[103642]: TomlError: Unexpected character, expected "nan" at row 115, col 18, pos 3784:
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 114:
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 115> secureOptions = null
Oct 27 14:54:33 ubuntuxo xo-server[103642]:                       ^
Oct 27 14:54:33 ubuntuxo xo-server[103642]: 116:

If I changed the secureOptions back to prior value with minTLS version the server would at least start, however I have no way to verify if functioning correctly.