I will create a card for this feature request to discuss with the whole XO team. I will keep you updated here

Hi @Andrew.
This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): fix incorrect state when remove server #8854

Hi @irtaza9
You have a typo in your vm-templates URL.
fields instead of field

Hi @irtaza9
FYI, for about 2 years, VMs expose a creation field:

"creation": {
    "date": string,
    "template": string,
    "user": string
  },

With this you can filter VMs by creation.user to list only VMs created by a user.
/rest/v0/vms?filter=creation:user:<user-id>

Hi.
The IPMI plugin is only used to display hardware information if you are using mona_1.44gg.

To display if a BIOS update is available, we mainly fetch this endpoint: https://pictures.2cr.si/Images_site_web_Odoo/Pages_produit/VATES-BIOS_BMC_last-version.json

Does your host have access to this endpoint?
What is the ouput of xo-cli host.getBiosInfo id=<host-id>

Hi,
Since XO is a client, I don't think it's a good idea to have this kind of feature. In this case, a VM could be restarted from sources other than XO, and would not apply the new VDI size.

However, I believe we can handle this situation by implementing a modal that appears when editing the VDI size of a running VM. This modal can offer the option to restart the VM immediately and apply the changes. In my opinion, removing the "pending" state will prevent confusion

@MajorP93 can you try this branch? mra-fix-redirect-https It should fix your issue with redirectToHttps=true

Thank you all for your feedback!

@ashinobi Several bug fixes related to VM migration are on the xo5/fix-bulk-migration branch. Could you please test to see if they solve your issue?

While investigating the code, I found something unexpected. We don't have exactly the same behavior for migrating from the Home/VM view and from the VM view itself.
I will try to fix this and it might solve your problem.
I will come back to you when I have opened the branch to allow you to do some tests on it.

Hi @Kptainflintt,

I don't think this is related to XO6, but probably to this PR: https://github.com/vatesfr/xen-orchestra/pull/9231
VDIs with snapshot_of: <something> are now recognized as snapshots

spacotte-vates opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): improve handling of xapi snapshots #9231

ping @melissa-fr

@Pilow Hi.
I've managed to reproduce the issue. I'm currently investigating it

@wmazren Hi.
Weird,i am unable to reproduce the issue..

Can you show us the output from the following command?
xe vbd-param-list uuid=c6f4c7fa-4f6f-7999-d13c-3a29d887d828

@fluxtor Hi.

Could you try disabling the redirectToHttps option in your configuration?
This should resolve the issue. You can re-enable the option once the patch release 6.0.2 is available.
Alternatively, if you absolutely need this option, you can open a support tunnel so I can apply the fix directly to your XOA instance.

@fcgo Hi.
The OTP field is in the preferences property

E.g.

  {
    "email": "foo",
    "permission": "none",
    "pw_hash": "***obfuscated***",
    "preferences": {
      "otp": "<value>"
    },
    "groups": [],
    "id": "694e8856-04c9-448b-90ef-2beb96d119cb",
    "name": "foo",
    "href": "/rest/v0/users/694e8856-04c9-448b-90ef-2beb96d119cb"
  }

@MajorP93 can you try this branch? mra-fix-redirect-https It should fix your issue with redirectToHttps=true

@MajorP93 I think I am finally able to reproduce the bug. I will try to fix it

@acebmxer
Perfect.
Thank you all as well! Early testing and feedback are very precious to us.

@acebmxer I want logs from the journalctl.
sudo systemctl restart xo-server
sudo journalctl -fu xo-server