@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

@acebmxer Can you provide me with the logs from xo-server at its launch?

Here you go. I made the changes you last suggested to me then I did a restart - sudo systemctl restart xo-server

before change-log.txt
after change-log.txt

Let me know if i did that correctly or if you need more information.

@MathieuRA

I appriciate your assistance with this but broke everything.... no /v5 or /v6 responce.

Anyone using this script - https://github.com/ronivay/XenOrchestraInstallerUpdater able to get this working with v6 as default?

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167                                                                                                                                                          
168 '/v5' = '../xo-web/dist/'                                                                                                                                
169 '/' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

i have applied updates to my 2 amd home lab hosts. Ryzen 7700x and 7950x amd x670e mobo's. No issues to report. Windows vm migrated between hosts no isssues. No issues with windows vm booting with uefi enabled prior to update.

@MathieuRA

Yeah i dont understand why this is not working or why it is working the way it is.

With this config below. Still defaults to v5 but links going to v6 and back to v5 work but defaults to v5. I do get a different login screen. I have also tried accessing via ip versus via proxy, same difference. I have tried to reach out to the creator of the script but waiting for their reply back.

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/' = '../xo-web/dist/'  
169 '/v6' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v6/api' = '[protocol]//localhost:[port]/api'
174 '/v6/api/updater' = 'ws://localhost:9001'
175 '/v6/rest' = 'http://localhost:[port]/rest'

@mathieura

Maybe this has something to do with the script i used to install xo but i can not get v6 to be the default. The links going from v6 to v5 work but just defaults to v5 and accessing. i use port 443 for xo and i do use a proxy.

from the config.toml file

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/' = '../xo-web/dist/'
169 '/v6' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

this config breaks everything. Nothing works.

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/v6' = '../xo-web/dist/'
169 '/' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

Original config

[http.mounts]
164 # Uncomment to setup a default version.
165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source
166 # '/' = '../xo-web/dist/'
167 
168 '/v5' = '../xo-web/dist/'
169 '/v6' = '../../@xen-orchestra/web/dist/'
170 
171 [http.proxies]
172 # [port] is used to reuse the same port declared in [http.listen.0]
173 '/v5/api' = '[protocol]//localhost:[port]/api'
174 '/v5/api/updater' = 'ws://localhost:9001'
175 '/v5/rest' = 'http://localhost:[port]/rest'

@MathieuRA

Just updated to the current commit 7c176. And all is working as in test commit. Question what is needed now to make v6 the default? Still as previously or has anything changed this last commit?

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

mra-fix-proxies

Confirm test branch works... This is with Ronivay's script. Include_V6 option is set to false in config file. Maybe that is why it still defaults to v5. At least all links work now...

@Forza its the only disk for vm the drive for windows. Reinstall windows... NO...

@ph7 VM was already moved to a new SR.

Other windows VM. I Have not looked at my work production environment yet, or linux vms.

@ph7

So question what happens when i thinks the vm disk is full? When will it clear up? Only thing i can think of was coping 13gb veeam ISO over few times testing things and stuff. but that has been a while now.

@ph7
My used space does not add up to actual used space in vm.

This might have something to do with the script i have been using up till now to update XO-CE but just to document here.

Master, commit 7cf97

XOA v5 links not working...

@paco Go to the vm in question and go to the storage and disable the CBT. Once migrated you can reneable or the backup job will reenable.

I had issues i could not move to new SR when CBT was enabled.

FYI we have the Broadcom NetXtreme Gigabit Ethernet (BCM5720) in Dell R660 and Broadcom Adv. Dual 10GBASE-T Ethernet in Dell r640.

Currently have no issues with ether nic in XCP-NG 8.3

@pdonias

I can confirm with @probain with UI bug.

If i start new vm from template and select the template Ubuntu 24.04.3 to start.

Then switch to any other template (pic below shows Rocky Linux template) the storage name does update by adding *_qxaj at the end but still remains named ubuntu not rocky linux. Also see the description bug appear.

If i switch back to the original template (second template switch) the storage name drops the _qxaj and description bug goes away.

@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

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso.

This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

@bvitnik thanks didnt know about the purge option. It didnt show on sudo apt --help

Are the new rust xen-guest-agent ready for production? Should I stay with the traditional xe-guest-utilities on the guest tools iso?
While trying to uninstall the xen-guest-agent and install the xe-guest-utilities I ran into this...

Is dpkg -l | grep xe not the proper way to detect what tools is installed?

test@Test:~$ dpkg -l | grep xe
ii  byobu                           6.11-0ubuntu1                           all          text window manager, shell multiplexer, integrated DevOps environment
ii  libxext6:amd64                  2:1.3.4-1build2                         amd64        X11 miscellaneous extension library
ii  plymouth                        24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer
ii  plymouth-theme-ubuntu-text      24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer - ubuntu text theme
ii  publicsuffix                    20231001.0357-0.1                       all          accurate, machine-readable list of domain name suffixes
ii  python3-pyparsing               3.1.1-1                                 all          alternative to creating and executing simple grammars - Python 3.x
ii  screen                          4.9.1-1build1                           amd64        terminal multiplexer with VT100/ANSI terminal emulation
ii  tmux                            3.4-1ubuntu0.1                          amd64        terminal multiplexer
ii  whiptail                        0.52.24-2ubuntu2                        amd64        Displays user-friendly dialog boxes from shell scripts
ii  xe-guest-utilities              7.30.0-13                               amd64        Virtual Machine Monitoring Scripts
rc  xen-guest-agent                 0.4.0                                   amd64        Guest Agent for Xen-based virtual machines
test@Test:~$ sudo apt remove xen-guest-agent
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'xen-guest-agent' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
test@Test:~$ dpkg -l | grep xe
ii  byobu                           6.11-0ubuntu1                           all          text window manager, shell multiplexer, integrated DevOps environment
ii  libxext6:amd64                  2:1.3.4-1build2                         amd64        X11 miscellaneous extension library
ii  plymouth                        24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer
ii  plymouth-theme-ubuntu-text      24.004.60-1ubuntu7.1                    amd64        boot animation, logger and I/O multiplexer - ubuntu text theme
ii  publicsuffix                    20231001.0357-0.1                       all          accurate, machine-readable list of domain name suffixes
ii  python3-pyparsing               3.1.1-1                                 all          alternative to creating and executing simple grammars - Python 3.x
ii  screen                          4.9.1-1build1                           amd64        terminal multiplexer with VT100/ANSI terminal emulation
ii  tmux                            3.4-1ubuntu0.1                          amd64        terminal multiplexer
ii  whiptail                        0.52.24-2ubuntu2                        amd64        Displays user-friendly dialog boxes from shell scripts
ii  xe-guest-utilities              7.30.0-13                               amd64        Virtual Machine Monitoring Scripts
rc  xen-guest-agent                 0.4.0                                   amd64        Guest Agent for Xen-based virtual machines
test@Test:~$ 

@bvitnik that worked.

@bvitnik said in Custom config / cloud-init:

@acebmxer Did you do:

cloud-init clean --logs --seed

before converting the VM to template?

Also, network configuration is not part of the cloud-config (aka user data). In XO, there is a separate field called "Network config" where it should be specified. See examples at the end of the guide I pasted earlier. network: key should also be removed (commented in the examples).

besides getting it working on fresh vm from the ubuntu template from the Hub. I do have that command in script to prepare the vm to create a template from it. AI says this will cause the vm not to recreate the 50-cloud-init.yaml file. So how do I work around that also.