I haven't tested performance yet, but I've configured the pass through for a GTX 1070 for transcoding on my mediacenter.

It's well recognized on the target VM (Linux) and by Nvidia drivers.

Hello @Andrew,

All my problems are now solved. They all came from the BIOS. I managed to update it with this solution :
https://www.youtube.com/watch?v=449N8h2GdlU

I had to rename the BIOS image name and use the automatic update tool.

@Andrew And what about the message

• xenoprof: Initialization failed. AMD processor family 25 is not supported

This server have a Ryzen 9 5900X. My computer a Ryzen 5 5800X. Same family. But it works on my computer. Worse, it worked on the server. Before

@Andrew Yes I unzipped the file. BIOS don't see zipped files anyway. The image is well seen by Q-Flash, but when I click on it I got the message, invalid image -_-

I can take a photo when I can

@Andrew That's what's weird. The boot order is correct. It's the XCP-ng EFI OS partition in first position.

As for the BIOS, I originally reset it because it wasn't registering changes properly, especially for the fans, and also because I couldn't update the BIOS.

I went and got the latest BIOS update for my Gigabyte B550 GAMING X V2 (rev. 1.3)
motherboard. Links here :
https://www.gigabyte.com/fr/Motherboard/B550-GAMING-X-V2-rev-13/support#support-dl

The current version is FB. I've tried the FC and FDc versions but I get a message telling me that the image is invalid.

I'm not sure what to do, maybe try contacting the manufacturer...

With the USB key, if I select it directly without going through the EFI partition, I get this screen and then nothing.

Do you think it could be a CPU problem? USB key with Debia, EFI and BIOS install works just fine...

Hello,

For a few days now, the server has been booting on the BIOS and no longer on XCP-ng. I have to override the boot to start. It's annoying but ok.

However, since today, I've been able to access this menu, it starts up fine, and there's the system initialization.

Except that after the last line, which indicates the processor and the number of cores available, I get a black screen and nothing happens.

This happened after a BIOS reset. Virtualization is enabled (SVM mode).
I get this result with : CSM disabled / Secure boot disabled, or with CSM enabled (set on UEFI only).
CSM disabled / Secure boot enabled -> no boot at all

Same result with an installation USB key, GPT partition (installed with Rufus). Am I missing something in the BIOS or is my motherboard not working?

I was able to boot onto the disk from my computer. Which has the following configuration: CMS disabled / Secure boot disabled. I used gdisk on the boot partition :

Note: This is a system that was originally installed on other hardware. I took the disks and put them on another server.

Thanks you

PS : It's not just a display problem. Impossible to access VMs that are in autostart mode. I can see in my box settings that the server is not connected to the network.

@olivierlambert "Please always use latest Node LTS."... Ok my bad. I didn't check which version is the LTS version.
Indeed, it works much better.
Thank you!

Hello,

I installed XCP-NG with XOA on a virtual machine to discover before installing it on a physical server (coming soon). Everything works fine, I was able to create a network, put pfSense in router etc, no issues.

I tried to install XOA from source on a Debian 11 machine, following the steps given by the documentation.

I can access the interface but problems occur when I connect my pool.

The pool is always disconnected with Error: socket hang up.

Voici ce qui se passe quand je lance yarn start

root@debian:~/xen-orchestra/packages/xo-server# yarn start
yarn run v1.22.19
$ node dist/cli.mjs
2023-01-11T19:33:02.656Z xo:main INFO Configuration loaded.
2023-01-11T19:33:02.660Z xo:main INFO Web server listening on http://[::]:80
2023-01-11T19:33:03.116Z xo:mixins:hooks WARN start failure {
  error: Error: spawn xenstore-read ENOENT
      at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
      at onErrorNT (node:internal/child_process:483:16)
      at processTicksAndRejections (node:internal/process/task_queues:82:21) {
    errno: -2,
    code: 'ENOENT',
    syscall: 'spawn xenstore-read',
    path: 'xenstore-read',
    spawnargs: [ 'vm' ],
    cmd: 'xenstore-read vm'
  }
}
2023-01-11T19:33:03.122Z xo:mixins:hooks WARN start failure {
  error: Error: spawn losetup ENOENT
      at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
      at onErrorNT (node:internal/child_process:483:16)
      at processTicksAndRejections (node:internal/process/task_queues:82:21) {
    errno: -2,
    code: 'ENOENT',
    syscall: 'spawn losetup',
    path: 'losetup',
    spawnargs: [ '-D' ],
    originalMessage: 'spawn losetup ENOENT',
    shortMessage: 'Command failed with ENOENT: losetup -D\nspawn losetup ENOENT',
    command: 'losetup -D',
    escapedCommand: 'losetup -D',
    exitCode: undefined,
    signal: undefined,
    signalDescription: undefined,
    stdout: '',
    stderr: '',
    failed: true,
    timedOut: false,
    isCanceled: false,
    killed: false
  }
}
2023-01-11T19:33:03.272Z xo:main INFO Setting up / → /root/xen-orchestra/packages/xo-web/dist
2023-01-11T19:33:54.173Z xo:main INFO + Console proxy (admin@admin.net - ::ffff:192.168.50.1)
2023-01-11T19:33:55.727Z xo:main INFO - Console proxy (admin@admin.net - ::ffff:192.168.50.1)
2023-01-11T19:34:02.723Z xo:main INFO + Console proxy (admin@admin.net - ::ffff:192.168.50.1)
2023-01-11T19:34:03.908Z xo:main INFO - Console proxy (admin@admin.net - ::ffff:192.168.50.1)
_watchEvents Error: socket hang up
    at connResetException (node:internal/errors:718:14)
    at TLSSocket.socketCloseListener (node:_http_client:463:25)
    at TLSSocket.emit (node:events:525:35)
    at TLSSocket.patchedEmit [as emit] (/root/xen-orchestra/@xen-orchestra/log/configure.js:135:17)
    at node:net:305:12
    at TCP.done (node:_tls_wrap:588:7)
    at TCP.callbackTrampoline (node:internal/async_hooks:130:17) {
  code: 'ECONNRESET',
  url: 'https://192.168.50.129/jsonrpc',
  call: {
    method: 'event.from',
    params: [ [Array], '00000000000000106186,00000000000000104805', 60.1 ]
  }
}

We can see that the call is made on https.

I redid an installation, but this time using XenOrchestraInstallerUpdater installing a certificate and I encounter the same problem.

Hardware config :

XOA Source

• Debian 11 (fresh minimal installation)
• 1 CPU
• Disk 10go
• RAM 2go
• NodeJS 19 from nodesource

XCP-NG

• XCP-NG 8.2.1
• 4 CPU
• Disk 2x90go
• RAM 16go

Did he encounter the same problem, or would he have an idea to solve it?

Thanks!