Posts made by tony

I have another weird one. The numeric representative is correct, but the bar graph is unintuitive.

@olivierlambert But for my case, I have nothing else in that NFS share except XCP-ng VHDs (single SR folder with nothing outside it). For my case (currently) I checked du -h on my NFS share and I get 572G and df -h shows about the same usage 572.1G. If I add total allocated disk space from all VMs using this NFS share, it is only 450G, so this means there are 100G+ of file system usage (from snapshots?).

I can now understand what the numbers represents (the actual physical disk usage not VM disk usage) but the bar graph still doesn't show the same thing. So just to clarify, does the bar graph actually show VM disk usage and not physical disk usage?

@olivierlambert Thank you for replying, it is indeed what the NFS share reports as free, but why there is such a discrepancy in NFS file size and actual VM disk size? Is it to do with VDI coalescing?

@peder The bar is correct I think, after adding all the disk allocated I get 450 GiB, but the number 715.95 GiB used is incorrect. I can't figure out where does this number come from, may be it also counts backups? But I don't store backups on this nfs share.

Hello, anyone have this problem or is it just my configuration?

The number says 200 GiB free, which should be around 20% free, but the graph clearly shows more than 50% free.

Ok figured it out at the end using xe pool-list on the existing pool gives me a list of existing hosts on the pool, and there was one that has been taken offline, without detaching in XO. So I did a xe host-forget uuid=<host uuid> because xe pool-eject doesn't work on offline host. And now I can add the new host just fine. Thanks everyone for helping!

Updating the BIOS of the new host made no differences. So I tried to add it to my test pool and what do you know, it works without any issue and the test pool has a master of even older CPU so I don't think its compatibility issue.

There must be something wrong with my main pool that I'm trying to add the new host to.

@nick-lloyd The new host is has new CPU, the old host already in the pool has older CPU. I will try to update the BIOS of the new host and see if it helps. I don't think the old host will have any updates.

@nick-lloyd They are both xeon but around 4 generations apart, how do I check if they are compatible? I have successfully added a non xeon with a xeon to the same pool before (there were warnings that some feature set will be disabled) so I thought this should be fine too, but please let me know otherwise.

More information, both are XCP-ng 8.2.1, I ran the host-all-editions command and both returns just xcp-ng

@nick-lloyd They are not in the same pool yet, because of the error above, the new host cannot be added to the pool. I ran the host-license-remove command on the new host and still the same thing, the result of the host-license-view remains unchanged.

@nick-lloyd Which host should run remove the license from? The new host or the master of the pool?

I checked both hosts with host-license-view and they have the same output:

restrict_vswitch_controller            : false
                           restrict_lab: false
                         restrict_stage: false
                   restrict_storagelink: false
     restrict_storagelink_site_recovery: false
               restrict_web_selfservice: false
       restrict_web_selfservice_manager: false
                  restrict_hotfix_apply: false
          restrict_export_resource_data: false
                  restrict_read_caching: false
                          restrict_cifs: false
                  restrict_health_check: false
                           restrict_xcm: false
       restrict_vm_memory_introspection: false
            restrict_batch_hotfix_apply: false
            restrict_management_on_vlan: false
                      restrict_ws_proxy: false
                          restrict_vlan: false
                           restrict_qos: false
         restrict_pool_attached_storage: false
                        restrict_netapp: false
                     restrict_equalogic: false
                       restrict_pooling: false
                             enable_xha: true
                      restrict_marathon: false
                restrict_email_alerting: false
        restrict_historical_performance: false
                           restrict_wlb: false
                          restrict_rbac: false
                           restrict_dmc: false
                    restrict_checkpoint: false
                   restrict_cpu_masking: false
                    restrict_connection: false
                        platform_filter: false
                     regular_nag_dialog: false
                          restrict_vmpr: false
                          restrict_vmss: false
                  restrict_intellicache: false
                           restrict_gpu: false
                            restrict_dr: false
                   restrict_vif_locking: false
            restrict_storage_xen_motion: false
                          restrict_vgpu: false
    restrict_integrated_gpu_passthrough: false
                           restrict_vss: false
       restrict_guest_agent_auto_update: false
    restrict_pci_device_for_auto_update: false
                    restrict_xen_motion: false
              restrict_guest_ip_setting: false
                            restrict_ad: false
                   restrict_nested_virt: false
                 restrict_live_patching: false
         restrict_set_vcpus_number_live: false
                     restrict_pvs_proxy: false
                 restrict_igmp_snooping: false
                           restrict_rpu: false
                     restrict_pool_size: false
                           restrict_cbt: false
               restrict_usb_passthrough: false
                 restrict_network_sriov: false
                      restrict_corosync: true
                   restrict_zstd_export: false
          restrict_pool_secret_rotation: false

Hi, I'm trying to add a new host to my existing pool, both are XCP-ng 8.2 but I'm getting an error about wrong edition. Can someone point me into the right direction please. Here is XO's log:

{
  "sources": [
    "1da4fc28-e460-7c6a-7c2b-86d4e012dfe6"
  ],
  "target": "6feb400c-180a-9c49-e0e2-1439a11f971c",
  "force": true
}
{
  "code": "LICENSE_HOST_POOL_MISMATCH",
  "params": [
    "Edition \"\" from pool is not known to v6d."
  ],
  "call": {
    "method": "pool.join_force",
    "params": [
      "192.168.137.231",
      "root",
      "* obfuscated *"
    ]
  },
  "message": "LICENSE_HOST_POOL_MISMATCH(Edition \"\" from pool is not known to v6d.)",
  "name": "XapiError",
  "stack": "XapiError: LICENSE_HOST_POOL_MISMATCH(Edition \"\" from pool is not known to v6d.)
    at Function.wrap (file:///root/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at file:///root/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:449:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Seems to be working now with commit c0d20, thank you.

Sorry @olivierlambert I just updated a couple of days ago and thought I was on latest, I'll update again and recheck. Thank you.

I just notice the encryption textbox at the bottom, I don't have anything filled in, could this be the issue?

Hi,

I've been using pool metadata backup for a while now without problem, but for the past month it just won't work. I am not sure whether it is related to new updates or not but did update XOCE to the latest git commit 84e38 and the problem persist.

The backup job failed after a few seconds with the below error:
Error: timeout while getting the remote 32cb6a61-ac0c-4f40-a8ea-d99b5291747d

I checked the remote page and ran health check, which seems fine.

I even tried ssh into the XOCE VM and check /run/xo-server/mounts/32cb6a61-ac0c-4f40-a8ea-d99b5291747d and I can see all the files there.

I tried deleting the remote and recreating it, no luck. I tried deleting the backup job and recreating it, no luck. I tried deleting xo-config-backups and xo-pool-metadata-backups to let it try to start fresh, also no luck.

Note that I have 2 backups, only metadata one failed, the normal VM backup seems to be fine, using the same remote.

What am I missing here?

Thanks,
Tony

@ninghe Are A and B identical servers? No shared storage? Does it work if you use normal snapshot mode?

Its a start of something great, need more functions though! For example:

• VM controls (start/stop)
• VM Information
• VM Import/Export
• Add/remove storage
• SR Information
• Insert/remove dvd
• Toolstacksrestart
• Warnings (low memory/storage space)

@toby4213 said in GPU passthrough - Windows VM doesn't boot correctly:

This is the only GPU installed on the system, no integrated graphics(Ryzen 5 3600). This shouldn't be a problem right?

I had this problem before and XCP-ng won't boot without another graphic card to display its xsconsole. It might have been changed in latest version of XCP-ng but if not you'll have to have at least 1 graphics card for the host (can even be an iGPU) and another PCIe card for the VM.

Also support for GeForce graphics card for VM is still in BETA stage so it might not work 100%, if you want to be sure then try your GRID card which might work better. AMD cards will work for sure even with vGPU.