I finally got my lab updated and the two vms started, so far so good. Stats data is present, the first time I've seen any of my hosts pull 100% CPU. Hosts are little HP T740 thin clients with AMD V1756B processors and 64GB of ram, in a 3 host pool.
Sorry I can't bring more detail, not really doing work on my XCP lab right now, and lots of shake up around tech. space at work.
I decided to burn my lab down because of some trouble and wanted to start fresh to isolate any problems I may have created in the past. Wiped the disks, built a new NFS share ready for work, installed the XCP-ng OS and configured networking for the management interface on the local machines, all normal stuff. Went back to my desk and logged into XO Lite on each machine, using console --> xsconsole I was able to get all the hosts into a pool, and add an ISO and NFS SR, all seemed to work.
Went to the New VM to create a simple Debian vm on which I intended to host XO-CE from sources. Typed the info in, chose the Debian image from my ISO SR, the rest of the config as normal. Uncheck the boot after creation box, and create.
Click on the VM to bring the console up, then click power on... UEFI loader comes up, and ... Can't find the boot disk. Tried another iso that I knew was capable of EFI boot, same.
Realized I was trying to start in EFI, made a new one in BIOS mode, this one worked but now my screen shots are messed up so I'll probably have to go through and delete stuff with a different XO and go back to grabbing images of the process to write up "for the next guy".
Other than this small issue, it's working and doing it all from XO Lite. Yes still a bunch of missing features, but I know you are working on this. I just wanted to try things this way on this fresh build and see what I could get done from local console and XO Lite.
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.
Nothing really to add, my 3 host Intel production pool updated just fine. The load balancer is always a little weird, but I'm sure it is calculated based on CPU and RAM assigned to each VM, where I split things up based on workload.
It's a small system, and the real workload is handled by 3 Windows VMs so I tend to split them up onto one of the three hosts.
I may get to my lab in the next couple of days, but it isn't doing work so testing is kind of pointless right now. The only thing "doing work" is a VM with XO from sources.
BTW, the ram increase made zero difference in the VDI migration times.
I may still change the ram for each host in production, but I only have like 12 VMs right now and probably not many more to create in my little system. Might be useful if I ever get down to a single host because of a catastrophe. Currently running what it chose for default at 7.41 MiB, roughly doubled that in my lab to see what might happen.
Just got my VMware lab started so all this other stuff is going to back burner for a while. I will say I like the basic ESXi interface that they give you, I can see why smaller systems may not bother buying VCenter. I hope XO-lite gives us the same amount of function when it gets done (or more).
I was looking for a way to mark this solved, can't find it.
I haven't moved things, but after migrating my big lab to my mini-lab, I'm confident that the warm migration is the way to go. It was fast and seamless as long as you have the right network adapters set up. I had to fool with one of my networks to make a VM function, but that was certainly something I overlooked while setting up the mini-lab. A little testing before moving the VMs should make this go easily if using the old servers is the option for this project.
@coolsport00 You actually referenced my post, so I referenced yours as backup to the condition still being present. I think we just need to wait for them to finish making XO-lite what they seem to intend it to be, I think it's going to be good and I think they are doing a great job so far.
Also, I have a post somewhere about the UEFI not working from XO-lite, maybe they can be merged?
Having what is essentially XCP-NG Center from a browser would be nice, no more need to install something on a Windows machine just to get some basic stuff set up until you get a full XOA instance running. Yes I know you can just grab the demo with a single command, but sometimes you want to configure a few things first.
Tom Lawrence has a bit hub with all the artwork that he uses, you might want to find that and check it out.
[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.
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.