Team - XO Frontend group | XCP-ng and XO forum

MathieuRA

Issue identified.

@spelon If you're using XO from source, you can try this mra-fix-undici-xen-api branch, otherwise, feel free to open a tunnel so I can fix your XOA.

MathieuRA

@acebmxer If you can open a support ticket with a tunnel, it would be nice. I am not able to reproduce in my lab nether on our QA lab

MathieuRA

Hello, thank you. I'm taking a look at it.

JorisK

Wonderful !

JorisK

@probain @acebmxer @jr-m4
I made a fix; if you could confirm that the issue is resolved for you, that would be great.
Here's the branch: fix/update-transfer-size-calculation

pdonias

Hello everyone! We need you!

We're currently designing the XO 6 UI for non-admin users, and some choices are genuinely hard to make. If you'd like to give us your opinion, here's a 30-second survey with 2 questions we couldn't settle ourselves: https://survey.vates.tech/s/cms4nrqb4005wrw01021ru6dy

Thanks!

MathieuRA

@acebmxer Thank you for your quick feedback.

MathieuRA

Hi @acebmxer,

Can you test if the branch: fix_cloudinit_import fix your issue?
Edit: It is available on the master branch.

pdonias

@acebmxer I can confirm that, we'll fix it, thanks

pdonias

Hi @irtaza9, I think your question is about why the size input is disabled in your screenshot, is that right? This happens because there are two types of VDIs you can use when creating a VM:

A brand new VDI, created from scratch. You choose its size, and it will be created empty.
An existing VDI that is already attached to the template you're using. This VDI already has content and a fixed size, so it is simply cloned during VM creation.

Your case is the second one, which is why you can't change its size.

Team - XO Frontend

Posts

Member List