@RobWhalley I think in the beginning i had that option enabled in my backup jobs, but found it was a hassle to move VMs between hosts with it on so i turned it off for all backups. Might be why my jobs worked because i had already done that switch in the past.

posted in the other thread as well but Xen Orchestra, commit 1a7b5 backups are working again. I tested configure and vm backups. They are being backup to NFS share.

updated my two hosts without issues.

updated on my three servers no issues.

try downgrading your nfs to use version 3. I think version 4.x has performance issues.
in you settings-->remote, you can edit the nfs mount for backups and add in the -o options section.

I dont know the exact command but you can try using nfsvers=3 and see if that helps.

scratch that prior comment. My backups are all setup as delta backup with schedule 2nd run that forces full backup. So i believe both are working correctly.

if you can also try deleting all the backup snapshots of the VMs in the backup and running full backup then the delta backup jobs.

looks good
Xen Orchestra, commit 384bb
Master, commit 384bb

thanks for quick fix

@Joe_dev I have a MF unit with similar igpu. I was not able to get it working under any virtualization platform. There is something about amd igpu that makes passing it hard. I believe some have had it working under proxmox with custom kernel and video bios. I never bothered trying all that out so i just gave up on the unit.

@andriy.sultanov is there a way to allow all devices (even if we blow up the system lol)

For example in the docs there a usb filter list you can edit
/etc/xensource/usb-policy.conf

anything similar for pcie? Can something be added with disclaimer you break it on you etc?
Maybe make it a command line option to disable the pci device filters for users that want to pass through special devices.

im seeing a similar thing in lastest version of XO (self built)
lspci showing more items the XO is showing for the host.
I just added a usbc card for example and its not showing up in XO.

curious how does this work, dont you need to put in a username and password/IP address for ipmi details. I havent looked at docs or tried this out, just wondering. I think on ESXI i had to setup the ipmi with such details before i could issue power on etc.

also noticed a new issue- seems like changes i had in the /etc/xensource/usb-policy.conf file for usb was lost during the upgrade.

I have some usb comm devices i use with a home assistant VM and they were gone post the upgrade.

anyway to make those change last post upgrade? Maybe make then options in gui so a config file can always be reflective of gui settings?

@stormi The original thread is here
https://xcp-ng.org/forum/topic/10374/xcp-with-opnsense-vm-running-att-bypass-is-vlan-0-network-possible/14?_=1766094991961

updates done on my two main servers and one dev box i happen to power on today. so far so good.

PS: Any way to get the following included on the next update for networking? I need it to run a scenario with opnsense vm. right now i have a script i run manually after rebooting the server.

ovs-ofctl add-flow xenbr3 "table=0, dl_dst=01:80:c2:00:00:03, actions=flood"

thanks

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

@marcoi check with who wrote your script to install XO from sources.

https://github.com/ronivay/XenOrchestraInstallerUpdater - this has a option in config file to enable v6 during install/upgrade.

or try -

cd /opt/xo/xo-web
yarn run turbo run build --filter @xen-orchestra/web

that worked thanks!

what build version of XO will start showing v6 interface? I may have missed the announcement.

i am currently on Xen Orchestra, commit f4988
Master, commit f4988 and when i try the menu link

I get a new tab with error below

anything i am missing? or is the XO build not out yet?

@Joe_dev I have a MF unit with similar igpu. I was not able to get it working under any virtualization platform. There is something about amd igpu that makes passing it hard. I believe some have had it working under proxmox with custom kernel and video bios. I never bothered trying all that out so i just gave up on the unit.

@manilx same here

Xen Orchestra, commit 45ef6
Master, commit 45ef6

getting build error as well. I run the update every morning to build XO.
Currently running at below version as the update failed

Xen Orchestra, commit 676b0
Master, commit bf705

• Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-back
up-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-server-transport-email, xo-server-transport
-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
• Running build in 21 packages
• Remote caching disabled
@xen-orchestra/qcow2:build: cache miss, executing e9d3169e4c8d9523
@xen-orchestra/qcow2:build: yarn run v1.22.22
@xen-orchestra/qcow2:build: $ tsc
@xen-orchestra/qcow2:build: src/disk/QcowDisk.mts(94,52): error TS2365: Operator '&' cannot be applied to types 'bigint' and 'number'.
@xen-orchestra/qcow2:build: error Command failed with exit code 2.
@xen-orchestra/qcow2:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@xen-orchestra/qcow2:build: ERROR: command finished with error: command (/opt/xo/xo-builds/xen-orchestra-202510281011/@xen-orchestra/qcow2) /tmp/yarn--1761660713548-0.01268
3662235605908/yarn run build exited (2)
@xen-orchestra/qcow2#build: command (/opt/xo/xo-builds/xen-orchestra-202510281011/@xen-orchestra/qcow2) /tmp/yarn--1761660713548-0.012683662235605908/yarn run build exited
(2)

 Tasks:    26 successful, 28 total
Cached:    0 cached, 28 total
  Time:    11.108s
Failed:    @xen-orchestra/qcow2#build

 ERROR  run failed: command  exited (2)
error Command failed with exit code 2.

updated my two hosts without issues.