yeah that was it, i removed the ip address from cfg file and it working now.

Updated to commit -db8ad this morning and backup is working.

I got back into v5 url once i removed LISTEN_ADDRESS="" from my xo-install.cfg

the backup ran on Xen Orchestra, commit cb85e

@florent I posted this in the v6 master thread, but it opens to the old interface but sits with a still loading message.

@simonp I downloaded the branch but i have no idea how to run a backup in v6 interface and v5 isnt working with the latest updates to XO. How do i run a backup job manually in v6?

I just got hit with the backup error, not sure what version i was running but it was likely a3139 or higher. I have XO rebuild each morning to fetch latest updates.
Error I can find (interface jumped to v6 so still learning)

Can't init vhd directory without using alias

"Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602170700/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602170700/@xen-orchestra/backups/_cleanVm.mjs:75:5)"

"Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602170700/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602170700/@xen-orchestra/backups/_cleanVm.mjs:75:5)"

Backup to NFS share

I ran into backup failure this morning, I think someone else mentioned about it in another post. I went to check if there was a newer version of XO since usually things get fixed quickly. so I updated XO to build 9dbc09011.

Few things

• XO loads up now using interface 6 as default.
• As someone else mentioned, about version is blank in v6.
• When I click on V5 link it brings me back to V5 but its broken for me. Sits there saying loading.
  
• Havent tried using guide to go back to V5 to see why backup failed. Not sure if V6 has enough to figure out backup issue since i havent used it much.

Update: looks like it failing to get something on v5 url.

Update 2: I had to remove LISTEN_ADDRESS="" from my xo-install.cfg to get version 5 working again

applied latest patches to my two host pool without issue.

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.

@tc-atwork thanks for post, i wasnt able to get xo6 setup as i havent had time to play with it. I look forward to when it released. For now I just keep using xo-lite to open the console window.

@olivierlambert

I will have to figure out how to get XO 6 up and running.