@gduperrey Skylake-S Xeon here w/o patched bios, works fine so far.

edit: double checked /proc/cpuinfo, seems the ucode update is applying correctly, so, yeah, it worked.

just joining the crowd of "seems fine"

root@lenovo150
--------------
OS: XCP-ng release 8.2.1 (xenenterprise) x86_64
Host: ThinkServer TS150 70LUS00C00
Kernel: 4.19.0+1
Uptime: 7 mins
Packages: 551 (rpm)
Shell: bash 4.2.46
Terminal: /dev/pts/13
CPU: Intel Xeon E3-1275 v5 (8) @ 3.600GHz
GPU: Intel HD Graphics P530
Memory: 560MiB / 2498MiB

note: only on 8.2.1 because I don't feel like even potentially breaking anything right now out of sheer laziness but its been rock solid so far

[19:51 lenovo150 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

and

[19:52 lenovo150 xtf]# ./xtf-runner -aqq --host
Combined test results:
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP

and of course

[20:00 lenovo150 ~]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:

@MichaelCropper I don't think that's entirely fair-there are plenty of homelabbers that purely do it as a personal side project, even if few of them end up on xcp-ng.

I mean, I'm certainly one of them.

Bumping my lab to staging right now-if you don't hear back, assume everything works fine.

@crembz not supported per https://www.intel.com/content/www/us/en/support/articles/000093216/graphics/processor-graphics.html

root@lenovo150
--------------
OS: XCP-ng release 8.2.1 (xenenterprise) x86_64
Host: ThinkServer TS150 70LUS00C00
Kernel: 4.19.0+1
Uptime: 7 mins
Packages: 551 (rpm)
Shell: bash 4.2.46
Terminal: /dev/pts/13
CPU: Intel Xeon E3-1275 v5 (8) @ 3.600GHz
GPU: Intel HD Graphics P530
Memory: 560MiB / 2498MiB

note: only on 8.2.1 because I don't feel like even potentially breaking anything right now out of sheer laziness but its been rock solid so far

[19:51 lenovo150 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

and

[19:52 lenovo150 xtf]# ./xtf-runner -aqq --host
Combined test results:
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP

and of course

[20:00 lenovo150 ~]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:

@MichaelCropper I don't think that's entirely fair-there are plenty of homelabbers that purely do it as a personal side project, even if few of them end up on xcp-ng.

I mean, I'm certainly one of them.

@gduperrey Skylake-S Xeon here w/o patched bios, works fine so far.

edit: double checked /proc/cpuinfo, seems the ucode update is applying correctly, so, yeah, it worked.

just joining the crowd of "seems fine"

Bumping my lab to staging right now-if you don't hear back, assume everything works fine.

@pdonias One of my VMs isn't reporting an IP address. Do you think that could do it?

Same as the OP.

netbox.synchronize
{
  "pools": [
    "582481e9-4e61-a060-6c09-530e35606504"
  ]
}
{
  "message": "ipaddr: the address has neither IPv6 nor IPv4 format",
  "name": "Error",
  "stack": "Error: ipaddr: the address has neither IPv6 nor IPv4 format
    at Object.parse (/opt/xo/xo-builds/xen-orchestra-202112260451/packages/xo-server-netbox/node_modules/ipaddr.js/lib/ipaddr.js:929:19)
    at Netbox.#synchronize (/opt/xo/xo-builds/xen-orchestra-202112260451/packages/xo-server-netbox/src/index.js:560:35)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202112260451/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
}

Its the 5.66.1 release commit-so its damn close.

I think so? Unless my script isn't updating the plugins, which is totally possible.

edit: quick look at github says my plugins are fine