<![CDATA[XCP-ng Center 8.0.1 released]]>🎆 it's now released! https://github.com/xcp-ng/xenadmin/releases/tag/v8.0.1.26 🎆

]]>https://xcp-ng.org/forum/topic/1665/xcp-ng-center-8-0-1-releasedRSS for NodeMon, 08 Jun 2026 05:04:49 GMTWed, 10 Jul 2019 21:33:27 GMT60<![CDATA[Reply to XCP-ng Center 8.0.1 released on Wed, 24 Jul 2019 00:33:02 GMT]]>@stormi Yes, it's present in both. That's what drew me to the 8.0.1 release - I hopping this was fixed from version 8.
I will go ahead and open an issue on github.

]]>https://xcp-ng.org/forum/post/14753https://xcp-ng.org/forum/post/14753Wed, 24 Jul 2019 00:33:02 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Mon, 22 Jul 2019 15:22:26 GMT]]>XCP-ng Center is maintained by the community benevolently (mainly by @borzel), so I'm not working on it myself.

I suggest to open an issue on https://github.com/xcp-ng/xenadmin/issues referencing both threads to make sure the issue doesn't get forgotten.

Do you know if the bug is present in XenCenter 8.0 too?

]]>https://xcp-ng.org/forum/post/14676https://xcp-ng.org/forum/post/14676Mon, 22 Jul 2019 15:22:26 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Mon, 22 Jul 2019 14:59:10 GMT]]>@stormi Thank you for looking into this issue.

I'm running Windows 10 Pro 1809, OS Build 17763.593.
I have DotNET 4.7.2 installed.

Is there any additional information I can provide that would be useful?

]]>https://xcp-ng.org/forum/post/14673https://xcp-ng.org/forum/post/14673Mon, 22 Jul 2019 14:59:10 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Wed, 17 Jul 2019 08:26:59 GMT]]>@flatlinebb It's useful to know that the issue happens to some and not to others, even if that does not solve your problem.

It does not mean that no one is trying to find out what's happening.

]]>https://xcp-ng.org/forum/post/14547https://xcp-ng.org/forum/post/14547Wed, 17 Jul 2019 08:26:59 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Wed, 17 Jul 2019 06:33:43 GMT]]>Thank you, that's helpful. Open-source support at its finest.

EDIT:
Not the only person reporting this issue:
https://xcp-ng.org/forum/topic/1384/xcp-ng-center-8-0-0-bouton-edit-memory

]]>https://xcp-ng.org/forum/post/14544https://xcp-ng.org/forum/post/14544Wed, 17 Jul 2019 06:33:43 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Mon, 15 Jul 2019 20:43:52 GMT]]>@flatlinebb Hmm..., it's present here. XCP-ng Center version 8.0.1 (build 8.0.1.26) 64-bit. Windows 10.

]]>https://xcp-ng.org/forum/post/14520https://xcp-ng.org/forum/post/14520Mon, 15 Jul 2019 20:43:52 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Mon, 15 Jul 2019 19:24:11 GMT]]>Here is normal:

6fd985be-e97e-4fa6-9223-4e80e46aabee-image.png

Tested with Windows 10 and Server 2008 R2.

]]>https://xcp-ng.org/forum/post/14519https://xcp-ng.org/forum/post/14519Mon, 15 Jul 2019 19:24:11 GMT<![CDATA[Reply to XCP-ng Center 8.0.1 released on Mon, 15 Jul 2019 16:48:59 GMT]]>The "Edit..." button is still missing from the Memory tab on VM's:

v.7.6.3:
a5df2e2e-2d08-4867-95eb-a4ff557bb5f5-image.png

v.8.0.0 and v.8.0.1:
1c0dabfd-dae6-4325-a880-f6cdaee0f290-image.png

]]>https://xcp-ng.org/forum/post/14516https://xcp-ng.org/forum/post/14516Mon, 15 Jul 2019 16:48:59 GMT