Xen Orchestra

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Subcategories

Management

VMs, hosts, pools, networks and all other usual management tasks.

229
Topics

1.6k
Posts

A

@fred974 Is this for production, or non-production?
Advanced features

ACLs, Self-service, Cloud-init, Load balancing...

73
Topics

637
Posts

D

@ronan-a Yes I'm on 8.3
Backup

All XO backup features: full and incremental, replication, mirrors...

245
Topics

2.4k
Posts

T

@stephane-m-dev for now it single error.
REST API

Everything related to Xen Orchestra's REST API

40
Topics

264
Posts

J

@samuelolavo Shell only handles string values, to pass other types to xo-cli you need to encode them in JSON and use the json: prefix:
xo-cli resourceSet.create name=test-resource subjects=json:'["d301d9ea-9e22-4480-bf40-111111111111"]' objects=json:'["8fb06362-d8fe-598b-f819-11111111111111"]' shareByDefault=json:true
Infrastructure as Code

Terraform, Packer or any tool to do IaC

20
Topics

188
Posts

S

@olivierlambert if that’s the case, great! I’m developing some modules for the xenorchestra terraform provider, and want to understand all the options.

G

Active directory authentication

• • gonzametal

12

0
Votes

12
Posts

91
Views

G

@dinhngtu LDP is using SSL, and no firewall between, so I think there be a ldaps misconfiguration
W

Solved Deleting a VM template?

• • webminster

3

0
Votes

3
Posts

35
Views

W

@Danp Thanks. My fault, I didn't notice the 2nd page of templates where it was.
G

This topic is deleted!

• • gonzametal

1

0
Votes

1
Posts

1
Views

No one has replied
D

XOA Failing on Check-in

• • DustinB

5

0
Votes

5
Posts

78
Views

A

Replying to myself here for an update.

I reinstalled the XOA appliance and imported my config. (On a different host in a different pool)
That took me back to XOA v5.98.1. Internet connectivity was fine.
I stayed on the Stable Channel and went up to 5.99.1. Internet connectivity was fine.

I have a Pool issue where the XOA was and I can't fix it until tonight. (I need to upgrade and reboot the master.)
H

xo-server-auth-saml

• • Honold

2

0
Votes

2
Posts

27
Views

O

Hi,

You should use the UI to config the plugin, but I suppose you are asking to pass extra parameters that aren't displayed/existing?
R

Solved Change the network device for remotes throws "mount.nfs: Connection timed out"

• • runevn

5

0
Votes

5
Posts

48
Views

R

@olivierlambert Oh my... I totally forgot to change the network interface on XO after the change. That was my mistake. Sorry.

But thanks a million for pointing it out.
F

Tag management for Storage not able to choose from existing tags

• • Forza

3

0
Votes

3
Posts

62
Views

M

Hi
Indeed. We will see how we can fix this bug.
Thanks
A

Solved Intermediate cert xen orchestra

• • astrugatch

4

0
Votes

4
Posts

77
Views

A

I bundled the cert and it is working as expected now.

Thanks!
J

Sum of actuall provisioned SR space compared to used space

• • johuus

2

0
Votes

2
Posts

50
Views

F

I haven't seen it in XOA, but in XCP-ng Center, this information is available:

f7ec1a2b-1d23-4258-93e4-a29f5ba00a48-image.png
A

Commit Number Not Updating?

• • AlexQuorum

5

0
Votes

5
Posts

62
Views

A

@Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.
I

Solved "Xenserver 8" with PVS Accelerator showing Full Orphan VDIs

• • infecticide

7

0
Votes

7
Posts

233
Views

M

Hi @infecticide, the fix for this issue has been been merged and will be available in the next release (5.100.1)
R

xoa not show host patch?

• • robyt

1

0
Votes

1
Posts

29
Views

No one has replied
T

Unsolved Storage Bar Graph Misinformation

• • tony

9

0
Votes

9
Posts

216
Views

T

I have another weird one. The numeric representative is correct, but the bar graph is unintuitive.

aa347240-cb22-4cde-acb0-ac741e44151a-image.png
J

Encrypt Server Passwords

• • jeffmetal

13

0
Votes

13
Posts

674
Views

J

@olivierlambert said in Encrypt Server Passwords:

I'm not saying it's not possible, I'm saying this will be at the huge expense of usability.

One such software implementation of a KMIP protocol server, which is in software form is an open source fork of HashiCorp Vault. This open source fork is called OpenBao (https://openbao.org/).
C

XOA / XCP-ng NTP?

• • Carello

4

0
Votes

4
Posts

89
Views

O

I think on recent XOA we even switched to systemd-timesyncd. Pinging @thomas-dkmt so he can update the doc to fix it (only the new doc directly! oh and you can ask @julien-f for details if needed, thanks!).
J

Solved Is it possible to do this with VM list filters?

• • JeffBerntsen

6

0
Votes

6
Posts

62
Views

J

@Danp You're right, I missed the question mark on it when I tried it before. With the question mark, it works. Thank you for your help.
X

Logs Partition Full

• • x-rayd

59

0
Votes

59
Posts

15.6k
Views

X

How can I determine which VM is causing this problem?
Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830066:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830198:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830311:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830458:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830605:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830712:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830797:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830885:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831006:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831094:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831185:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831260:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831333:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831407:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831478:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831551:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884264:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884519:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884615:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884721:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.923891:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924054:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924207:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924319:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924505:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924675:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924803:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924913:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927026:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927185:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927303:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927436:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927657:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927772:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927903:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927993:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928136:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928255:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928396:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928479:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932786:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932906:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017)
P

Solved Bug?? Tree view XO v6

• • ph7

3

0
Votes

3
Posts

58
Views

P

@Danp
Yes of course You are correct
I moved it to local storage a few weeks ago
My bad
K

Solved Filtering multiple hosts by name

• • kent

5

0
Votes

5
Posts

49
Views

O

That's the right way, yes 🙂 Enjoy!
P

Lots of performance alerts after upgrading XO to commit aa490

• • ph7

22

0
Votes

22
Posts

1.7k
Views

P

@ph7 said in Lots of performance alerts after upgrading XO to commit aa490:

@olivierlambert
One strange note when I get the alarms on e-mail during a full backup of my running XO

Alert: vm cpu usage > 65%, XO 67,8%

End of alert: vm cpu usage > 65% SyncMate 0,3%

End of alert is the wrong VM, should be XO.
In Dashboard/Health it's OK, it says XO in both alert and end of alert ??

Not a big deal for me, but I thought might as well report it

I added a new VM and put it in a backup job (which had a concurrency of 2) and got these new alerts:
ALERT: VM CPU usage > 80% XO5: 80.4%
End of alert: vm cpu usage > 80% HomeAssistant: 6,7%
It seems like the reporting has changed and is reporting the latest VM.

The host alert is reporting in the same way
ALERT: host memory usage > 90% X2 🚀: 92.7% used
END OF ALERT: host memory usage > 90% X1: 11.3%

I have changed all jobs to concurrency 1 and I have not got any SR alert

1 / 95

Solved Deleting a VM template?

This topic is deleted!

Solved Change the network device for remotes throws "mount.nfs: Connection timed out"

Solved Intermediate cert xen orchestra

Solved "Xenserver 8" with PVS Accelerator showing Full Orphan VDIs

Unsolved Storage Bar Graph Misinformation

Solved Is it possible to do this with VM list filters?

Solved Bug?? Tree view XO v6

Solved Filtering multiple hosts by name