XCP-ng 8.0.0 Beta now available!
-
@olivierlambert Go figure - just two days after that posting, my creaky old HP DL365 Gen1 up and died. CPU 1 memory bank shows a solid set of lights for RAM sockets, i.e. the memory controller can't access RAM. Bummer.
My wife took pity on me - or got me a father's day gift, depending on your point of view - and sprung for a Dell R815, which is supported. Of course, I gave the 8.0 beta a spin.
Installation was slightly faster, but there have been a few minor quirks along the way:
- The USB key I stuck into the unit wasn't an option for the OS install, but did show up as an option when creating storage for VMs. No big deal, but still kinda strange.
- Peeking at a different console via Alt-F2 and Alt-F3 showed some patches? And the kernel/dracut root/boot installation section took a loooong time to complete; everything else flew by. If it's downloading those patches that would explain the delay - the unit has a slow wifi bridge connection.
Other than those, it seems fine. I'm still poking around it, getting a few for what's changed.
-
@apayne I'm not aware of the installer being able to download patches from the internet. Can you create a tarball of
/var/log/installerand make it available to me so that I check that?Not being able to install the system on usb key is a good thing: it is not recommended because it would wear out too quickly due to frequent writes.
-
@apayne For USB-Key see our FAQ: https://github.com/xcp-ng/xcp/wiki/FAQ#can-i-use-xcp-ng-on-a-usb-stick-like-esxi
-
Xen Orchestra is not letting me log in after deploying with the Quick Deploy. Always returns "invalid credentials". I have attempted to quick deploy a number of times with different usernames and passwords but no joy. As I am just kicking the tires I did not created an account on xen-orchestra.com so I left those fields empty, not sure if this would make a difference.
-
Please
yum updatebefore, we fixed some stuff regarding that. -
@apayne said in XCP-ng 8.0.0 Beta now available!:
@DustinB said in XCP-ng 8.0.0 Beta now available!:
[...] Citrix just waved their hands and said "these don't work anymore".As for so many other people: Start reading and understand what you read.
It's not said that they don't work anymore, what they say is: They don't care if any THESE CPU/PLATFORM RELATED PROBLEMS occure. They might try but will give up rather soon, as it's called "best effort".And a pretty good, understandable, reason is: Vendors don't help anymore, means in case something's wrong on that and you need their support, because you promised customers, that you support that... guess what?
Solution: Drop it!I'm sure you could get support forever - if you pay the right amount.
Otherwise: Somewhen it's time to replace old stuff and buy new(er), way less energy consuming, hardware.And why paying for Hyper-V? It's free, like the smallest version of VMware is. Most people and small companies are pretty fine with what their limits. Don't get me wrong: If XCP-ng continues the roadmap, I see a good chance to beat them up.
You should way more read about all of that, than yelling and complaining at/about Citrix or XCP-ng.
Edit:
"We still have the experimental ZFS support and zfs packages have been updated to 0.7.13. The known limitations (no VDI export...) remain for now."
As you posted it's on 0.8.0 now, you should update the startpost.
Also IIRC you said migration/export is still not supported with ext4/zfs etc. - when (or for what/when) will that change?
Do backup tools need to know about ext4... and/or does it make any difference for them, or is it just interally, so it's like as if nothing ever changed? -
ZFS in XCP-ng 8.0 is fully functional. Migration/export/backup, everything is working.
-
@cg re: old CPU support, the note was already taken
it just strikes me as ironic. I understand the need for less power hungry processing but in my case I’m using a hefty 260 watts idling for the server alone. I am guessing the old SAS/SATA enclosure I have rigged to it is another 300 or so at idle. That’s a lot of draw for “newer”, but the capacity is excellent so I won’t be needing more hardware. Plenty of room to spin up new VMs.Re: Hyper-V, I already use the 2nd Gen at work via old 2012r2 installs. It’s OK and gets the job done. However I’ve been tasked with shuffling and consolidating some older installations to newer hosts/hardware, and the move process is a bit clunky for that version. Device pass through seems a bit limited.
Last time I saw VMware it was a demo lab we did at work, and it too was “just ok”, that was with the vmsphere(?) web interface, etc. However last I heard they are slowly tightening the list of supported hardware drivers, and by extension, supported hardware. That was a few years back so maybe they have added new drivers.
XCP benefits from decades of Linux device driver development. It simply boots, and that removes a lot of “officially supported hardware” headache for me. And the price is right too
-
Sorry if this has been asked before but since the 8.0.0 is working very good, especially with XO backups, is there any estimation when the final release will be out ?
br, Pete
-
The official date is "when it's done" (understand: when we have enough community feedback and we did all our tests).
But no major block appeared so an RC should come really soon.
And remember: more community feedback: faster release.
-
@olivierlambert Please, how can I send good data about XCP-ng beta for two types of blades, from HP and Dell? Something like a Citrix Health check would do it?
-
Just let us know if everything is working for you, and what hardware are you using, that's enough for us
-
HP BladeSystem c7000 enclosure G2, with Proliant BL460c Gen8 servers. HP VC FlexFabric 10Gb/24-port modules.
Dell PowerEdge M1000e enclosure with PowerEdge M620 blades. 4x Dell MXL 10/40GbE modules. Those I/O modules gave errors with Xenserver 7.6, XCP-ng 7.6 - one of the redundant HBAs get disconnected with DMA errors in the hypervisor logs.
So far, so good with XCP-ng 8.0 beta. Not much load on the servers. Some fake loading with fio.
-
@olivierlambert said in XCP-ng 8.0.0 Beta now available!:
ZFS in XCP-ng 8.0 is fully functional. Migration/export/backup, everything is working.
So you should update the start post and a) fix version info and b) remove the "known limitations..." part.
I "upgraded" XS 7.6 on my Ryzen testmachine flawlessly to XCP-ng 7.6. Next steps will be:
Create ZFS RAID on other SSDs, see how dedup/compression works and what it takes (as it should be fully functional and transparent for XAPI and everything connected - right?)
And then upgrade to 8.x and see if everything comes back up. But need to puit the machine into rack first.
People should heavily consider ZFS and dedup - it consumes som RAM, but especially in VDI or closish VM environments (like running a bunch of identical Window Server OSs) can save up quite some space on your SSDs and bump the value heavily!
IIRC dedup requires 1 GB RAM per TB - which can be a pretty good deal, pricewise.@apayne said in XCP-ng 8.0.0 Beta now available!:
@cg re: [...] I’m using a hefty 260 watts idling for the server alone. I am guessing the old SAS/SATA enclosure I have rigged to it is another 300 or so at idle
Power must be pretty cheap at your place. Yeah external enclosures like HPEs D2x00 consume quite some power, too. In the long run changing to something small will be financially wise.
I can recommend not super up2date HP hardware. I'm also using some Intel DC S-ATA SSDs now on the HPE controller as read cache (recommendation from a friend who's working in a big datacenter with tons of HP(E) servers). Seems to be good and you can get 960 GB versions for less than 200 bucks.Re: Hyper-V, I already use the 2nd Gen at work via old 2012r2 installs. It’s OK and gets the job done. However I’ve been tasked with shuffling and consolidating some older installations to newer hosts/hardware, and the move process is a bit clunky for that version. Device pass through seems a bit limited.
Need to test XCP-ng and the passthrough for license dongles with XCP-ng for some usecases...
Even actual Hyper-V versions are free, there are special Images, that don't include a GUI etc.
(Though I crashed with Hyper-V once and never touched again)Last time I saw VMware it was a demo lab we did at work, and it too was “just ok”, that was with the vmsphere(?) web interface, etc. However last I heard they are slowly tightening the list of supported hardware drivers, and by extension, supported hardware. That was a few years back so maybe they have added new drivers.
I have some ESXis working. They do okay and customers only have small servers, which don't run into the limits. Hardware is rather actual, so I can't really say anything about it - but I know they have some support limitations.
-
@cg said in XCP-ng 8.0.0 Beta now available!:
@olivierlambert said in XCP-ng 8.0.0 Beta now available!:
ZFS in XCP-ng 8.0 is fully functional. Migration/export/backup, everything is working.
So you should update the start post and a) fix version info and b) remove the "known limitations..." part.
You're right. I have updated it.
-
In fact it was true until we release 0.8 in XCP-ng, but yeah, now we should update the doc
-
Works great for me, both with LVM SR and ZFS file SR!
Love it!Just one minor issue: I can't get an old Windows XP VM to boot with Citrix legacy PV drivers. It was working with xcp-ng 7.6, but no longer with 8.0 beta. It does not have internet access, It is needed to control old hardware for which no driver for newer Windows OSes exist.
-
Testing 8.0 beta on Dell R710, clean install. Everything I've tried so far works flawlessly. Installed XOA from welcome page and few Linux VMs. Also installed W2008R2 (using a Dell ROK licence I've found on the server with BIOS settings copied) and it also works fine. I've used Windows update setting in XOA method to get the PV drivers and they installed fine without disabling Driver signing. Only thing missing is a Management agent/tools. What would be a preffered method to install that on 8.0?
Edit: I've extracted managementagentx64.msi from Citrix Hypervisor 8.0 install ISO and installed it on W2008R2 VM. Worked like a charm.
-
Planning on testing soon. Haven't had much time at home lately to mess with the lab.
Thanks for all the hard work!
-
Sharing results of some tests I have been doing lately, maybe that can give ideas to other testers. Those are cross-pool live migration tests. The goal was to evaluate if creating a new pool and then live migrating the VMs from the old pool would allow to avoid downtime in every case.
Summary of the results: when it comes to migrating VMs from older versions of XenServer, the situation is better in 8.0 than it was in 7.6, because Citrix fixed a few bugs (that we reported). Some failing cases remains and will not be fixed because they would require patching unsupported versions of XenServer.
Tests done using nested VMs as the sender pool, and a baremetal XCP-ng 8.0 as receiving pool.
I have 4 test VMs to migrate. They are small VMs, with small disks and little RAM, and little load too. So if you have bigger VMs and can test, you know what to do!
- HVM Centos 7 64 bit from the "Centos 7" template (this is important). No guest tools.
- HVM Centos 7 64 bit from the "Other" template (this is important). No guest tools.
- PV Centos 6 64 bit from the Centos 6 template. No guest tools.
- HVM Windows 7 32 bit with PV drivers installed.
I have tested migration from XenServer 6.5, 7.0, 7.1 and 7.2 (all fully patched).
- From XenServer 6.5 to XCP-ng 8.0
- HVM Centos 7 from Centos 7 template: fails! The VDIs are transferred but when it comes to migrating the RAM and complete the migration it fails, reboots the VM and creates a duplicated VM in the target pool ! (same UUID). This is a bug that Citrix won't fix in older versions : https://bugs.xenserver.org/browse/XSO-932
- Other VMs: OK
- From XenServer 7.0 to XCP-ng 8.0
- HVM Centos 7 from Centos 7 template: same failure
- Other VMs: OK
- From XenServer 7.1 or 7.2 to XCP-ng 8.0: all good.
I have also tested storage migration during a pool upgrade (for VMs that are on a local storage repository and need to be live migrated to another host of the pool), to check if this fix we are trying to contribute upstream works as intended (it wouldn't work in XCP-ng 7.6 because of additional bugs fixed since by Citrix in CH 8.0) : https://github.com/xapi-project/xen-api/pull/3800. Good news, it worked (in my tests), so I consider leaving it enabled (it isn't in CH 8.0). Feel free to try it and report! It's still recommended to use shared storage for easier live migrations, but being able to do the migration when the VM is on local storage can still be handy. Reference: https://github.com/xcp-ng/xcp/issues/90
closed Allow migrate_send during RPU #3800
