@acebmxer

I think I need to update mine, probably a ton of commits old by now.

@aesparragon said in ️ XO 6: dedicated thread for all your feedback!:

It looks like the same IP addresses are being displayed for multiple adapters. Each adapter should only show its own assigned IP addresses.

I saw that the other day, you should be able to expand the next block to the right to see the individual connection ports. I think this is one of those "need to get accustomed" to the new interface things. But I'd agree that it is more clear in XO5.

XO-Lite does break them down by PIF, but does not currently show the IP address of that host. Seems like we are wanting a mix between XO-Lite and XO6.

@acebmxer

I need to check, I think my from sources is also doing this, light/dark stays but I need to check themes and see. That said I am probably 3 dozen commits behind at this point and probably going to wait until next week to update any of my XO from sources (yes two, one VM and one on bare metal Debian as a backup).

@florent

Thanks. I'm still going to wait until next week, my schedule just doesn't give me the time right now. But nice to know that when I do update, it will be fixed and my laziness prevented a problem for me

I think I'll get my pool updated today, only been waiting a week at this point.

@probain

I'm still on an older commit, being lazy and haven't had the time to update. Next week is Microsoft updates day, I may deal with XO the same day.

I run health checks on mine every night when they backup, so for me this could get big very fast. I think I'm going to continue to wait until there is more news on this issue, or I'll have to uncheck the accidental deletion box (not my desired choice). I'll let you know next week what I decided.

@probain

Not that this is an answer, but what happens if you uncheck the deletion box, and delete them manually?

[edit] strike all that, I found them in XO5 and removed them. It was the reshuffling of where things are between the new interface.

@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.

@john.c

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.

@Whitebeard

Log into XO lite and start it back up, this definitely works.

@olivierlambert

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.

@benapetr

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.

@paco

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?

@john.c

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).