@manilx
Everything I've used so far is 1920x1080 or higher resolution... I guess I'll have to use my ClockworkPi uConsole with it's 1280x720 screen and see what I can see, I may hate it on this little device.
As a Windows user, I've gotten used to things moving locations from one update to the next, but I get it, it's going to take some learning.
I'd say XO-Lite was minimally viable almost a year ago, you could get real work done bouncing between it and the host console (still in XO-Lite).
Both are getting better, it's going to be a journey and I'm warming up to some of the features in XO 6.
As to the discussion about the third party scripts, maybe if the official method had a script to make it easier/quicker to install we could all be on the same page. I've used both, and failed many times with the official method (several years ago) and it could be easier for people setting up labs to install it. But maybe that's the idea, make it long and tedious.
I'm just going to say that things like the new dashboard have grown on me, but needing to flip back to 5 for some things is a pain. Trying to be patient and truthfully I don't spend a lot of time in my system now. Log in to check backups, do some updates once in a while, etc. My system has become fairly stable.
That said, I did recently upgrade my lab, and that will get a ton more use in XO when I get back to some testing I'm doing there. Probably going to wipe out my lab and start over, planning that now. and it may or may not be XCP this time so I can learn the basics of a different system.
I was having similar focus issues with a Debian 12 VM today, switched to XO5 to get the work done. Every few seconds the green border would vanish, but when it came back nothing had reset so it was less painful, but still annoying enough to switch back to 5.
Log into XO lite and start it back up, this definitely works.
The odd part is that I'm happy with XO Lite, so not sure why 6 is causing me problems other than needing g to jump back to 5. I only have one XO new enough to be updated, I guess I need to update my lab since I'm in it a lot lately and come up with more productive comments for the team. The switch just immediately shocked me in a way that it shouldn't have done being that I've been using Lite to try and get ready.
Trying not to be negative, but I hate having to jump back to v5 to get things done.
Working on my production system today and I noticed something new.
Three hosts in a pool, doing a Rolling Pool Update.
I'm seeing VMs migrate to both available hosts to speed things up, this is not the actions I've seen in the past. Just an interesting thing to see all three host go yellow while it is migrating.
OK, only happened to evac the third host, evac second host was back to the normal move everything to the same host (#3).
And not sure why, but the process start to finish on host 1 was faster than the other two, host 1 is coordinator.
Also of note, there seems to be no place to do a RPU from within XO6.
Did the three hosts in my lab pool, nothing blew up so I guess that's good. Just nfs storage with a few windows VMs and a Debian 13 for XO from sources.
I think everything is now an efi boot, but no secure boot machines.
Thanks, I will have to play with this when I have time.
@benapetr
Pretty cool project, might be handy to learn to work with this.
Question: Will it run on a raspberry pi with a 1280x720 display? Specifically a Clockwork Pi uConsole with CM4 Rpi module with 8gb or ram.
That's my emergency computing device for when things fail, only thing it is missing is a kvm to USB module to look at BIOS on a server.
On the stuck server, could you warm migrate the vms to one of the other hosts? Or could you shut down a VM at a time and cold migrate them? The second option is certainly not ideal, but maybe?
I'll have to update group policy and check that out, would be a time saver. Everything I use is an Enterprise level of some kind, using EDU in production right now, and Pro/Enterprise evaluation in the lab.
I was looking at running a post imaging script to prevent some of the bloat, but a GPO might be easier.
Just wanted to add a comment:
Thanks for continuing to release the drivers in an ISO. I was having some slowness with the 9.0.9 versions that are currently included with XCP-ng, this is a new Windows 11 25h2 that I'm working with to prototype a workflow in my lab. I just grabbed the 9.1.x ISO from Github and copied it to my ISO SR and installed. There seems to be a slight performance increase in this Win11 VM. That said, 25h2 is horribly bloated with junk, so much so that I think I'm going to need to strip a bunch out before I put this version into production. This might be a condition for MicroWin customization.
Or maybe add a couple of things to the LTSC version (we have licensing for this at work).
200gb free space was enough in my production system to cause this. The only thing I didn't try was filling it up until I found the point where it started working.
Let's say you don't have the metadata backed up... Is there a way to boot from a rescue disk and save the metadata?
I haven't had too much difficulty hitting the esc key in time to get into the EFI config. Click the start VM button, quickly click away from the display area and click in the display area, then toggle the esc key until I see it take effect.
I know I have a couple running at 1920x1080, but that's actually kind of a pain. I only did that to try and get a larger RDP window, RDP may be limited by the original "monitor" resolution, but this might also be fixed in later updates. This one VM has been up for a few years. (edit, yes this has been changed, VMs with a 4x3 monitor now RDP is whatever I have set).
[edit] I just realized this was from 2024.
So far I only have 1 of my 2022 servers changed to the XCP-ng drivers and management agent, the only thing that happened was the NIC went back to DHCP and a short struggle to shift it back to static. I use the e1000 profile when I set up a VM.
This was previously using the Xen 9.4.x drivers downloaded from Xenserver.
The only other glitch is that if you migrate the VM to another host in the pool, the management agent is no longer detected. But additional migrations and rolling pool updates and reboots are not bothered by this. I'm told this will be fixed in the next version.
As far as the drivers themselves, I don't see any issues on this one VM.
I think I have another 2022 in my lab with the XCP-ng stuff installed, I'll have to check later. I've had no issues with it. These were both installed from the new Tools ISO that is default with the latest XCP-ng 8.3.x
I keep hoping to see an Alpha or Beta of XCP-ng 9 soon, but I think there is still a lot of work to be done on the host side and on the Xen Orchestra 6 side.
Going back up to the top of the thread, removing compression was what fixed this for me, and my backups are still saying they are successful (maybe I better check).
I wish there was an easier way to "right size" the storage on these Windows VMs, the suggestion is to copy the VM to a new and smaller "disk" but I haven't looked into what is involved to get this done.
My production pool upgraded fine as far as I can tell, but not so good with the windows drivers, I'll make a thread on the drivers.