@irtaza9
Install the tools

@Dkurupp
I have no idea but have You tried
Restart toolstack or reboot the host

and xo/v6

@lsouai-vates
Looks to work now in v0.12.1 (c8f9d)

@gduperrey
Ran some test on my old i7 and it seems to work fine

@lsouai-vates
2025-06-24

2025-07-01

Hidden behind the tree view

Hi
Tested the new XO Lite
Under host dashboard the graph is not correct
If I hover over RAM usage and Network throughput (sunday June 30)
it says: Sunday June 23
Using Swedish keyboard

No stats before Friday

If I hover over CPU usage the "help text" is hidden behind the tree view.
Same in XOA latest/v6

@McHenry
To my experience, no. There will always be 31 deltas
After a few month's it can look like this:
MMMddddddddddddddddddddMddddddddddd

@stormi
Did some minor testing and it seems to work fine

And snapshot is 2h diff

I'm too triggerhappy
Not everything has changed.
The replication are still 2h off

Should have been 20:10 and 20:40

And in the schedule it still showing the next running in AM/PM not 24h

should have been 20:52

Buy I'm still happy

@olivierlambert @lsouai-vates
Everything now magically showing the right time and def. timezone

@coolsport00 said in Best Way to Live Migrate XO VM:

I guess I can remove my current ones temporarily from my current Pool and XO then add them briefly to the XOA...we'll see.

You can run several xo/xoa, connected to the same pool, at the same time. It can be quite handy some times.
The easiest way to deploy a xoa is from xo-lite

@lsouai-vates
Today I noticed that there is the same in xo5 (commit 25192)
Jobs with disabled jobs but scheduled in a sequence job are shown with Not backed up VMs

By the BCK_Running tag, it is backed up

@ThierryEscande
Ran some tests for 20 min
Seems to work fine

[18:39 x1 ~]# ethtool -i eth0
driver: e1000e
version: 5.10.179
firmware-version: 0.13-3
expansion-rom-version: 
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

@stormi
My old i7 with e1000e is working fine (except the version not shoving)

@stormi
I ran the xcp-ng-testing and now the migration seems to work

@stormi
If You are asking me, I can run the New update candidates for you to test! on my "production" home lab server if the testing repo still exist

Cold migration doesn't work, but Warm migration does.
No panic, I can wait for the release

@Andrew

looks like you need to yum clean all and yum update again.

Tried it but it didn't work
And I ran the rm -rf /var/cache/yum

[13:09 x2 ~]# yum clean all
Inlästa insticksmoduler: fastestmirror
Rensar förråd: xcp-ng-base xcp-ng-updates
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors

[13:14 x2 ~]# rm -rf /var/cache/yum

[13:14 x2 ~]# yum update
Inlästa insticksmoduler: fastestmirror
Determining fastest mirrors
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
xcp-ng-base/signature                     |  473 B  00:00:00     
xcp-ng-base/signature                     | 3.0 kB  00:00:00 !!! 
xcp-ng-updates/signature                  |  473 B  00:00:00     
xcp-ng-updates/signature                  | 3.0 kB  00:00:00 !!! 
(1/2): xcp-ng-updates/primary_db          | 238 kB  00:00:00     
(2/2): xcp-ng-base/primary_db             | 3.9 MB  00:00:00     
No packages marked for update

And rebooted