Hi everyone,

I just installed this 8.2.1 a Dell R630 and the installer was very smooth.
We chose to make a new installation since the host was running XS 7.2 and we wanted a fresh install, with that came the opportunity to leverage EXT and thin provisioning which seems to work just as it should.

We're also mounting a NFS SR for VM disks which works fine as well. I'll have to wait and see, but hopefully the problem with /var/log/snmpd.log is resolved now and no more alerts regarding disk usage

We're using Veeam for our VMware platform and XOA for our XCP platform and I have to say I prefer XOA. Why may one ask?
Well it is dead simple, its not bloated, you have a ton of options when it comes to configuration, destination, scheduling and so on.

Veeam on the other hand is A LOT faster, we're using a 10G link to our backup site and we're seeing speeds over 7Gbit/s when backing up our VMware platform and I know this is something Vates is working hard on improving in XOA.
Veeam also has application aware backups which is a big deal when you're running MSSQL inside your VM's - I dont think there is any plans from Vates in supporting this and this might be a big deal for customers comming from the VMware and Veeam-side.

According to Microsoft you need to use their built in backup feature or a software that supports AD and VSS which will tell the VM OS that it is going to be backed up.
Unless you do this there might be corruption of the AD Databases according to Microsoft.

ALL THO we've been backing up our AD servers with XOA snapshots (Both normal backup and incremental) and had only 1 issue since we started using XOA in 2016.
Since that issue we also use a guest agent (From Ahsay CBS) that makes a Windows System State backup and Windows System Backup.

More info about that can be found here:

https://wiki.ahsay.com/doku.php?id=public:version_9:client:9447_system_state_backup_vs_system_backup

A great opportunity for anyone who is into xcp, xoa and opensource software to join a great company

@olivierlambert said in XCP-ng 8.2.1 (maintenance update) - ready for testing:

Thanks a lot @nikade for your feedback! (also I love your avatar!)

Yeah, I gotta have my suit on my tux

I wanted to inform that I've tried iSCSI with multipathing as well and it works fine.
So far everything we need in our general production-environment seems to be working as it should.

@blackliner said in Sdn controller and physical network:

@nikade How do you "pair" the XCP-ng SDN with your routing setup?

You cant/dont, you'll have to setup each private network on the vyos router and then have the vm private network routed through it manually.

For example if you have private network 1 with subnet 192.168.1.0/24 you'd have to add this network to the vyos router and assign 192.168.1.1/24 on the router.
Then set 192.168.1.1 as default gateway in your vm's which uses this network.

Then you'll setup ospf or bgp on the vyos router manually with your upstream border/core-router or firewall. If the subnet is a private subnet you'll need to setup NAT as well somewhere before it reaches internet to NAT traffic from 192.168.1.0/24.

@Greg_E said in What should i expect from VM migration performance from Xen-ng ?:

@nikade

I've spent a bunch of time trying to find some dark magic to making the VDI migration faster, so far nothing. My VM (memory) migration is fast enough that I'm not concerned right now. and don't have any testing to show for it.

Currently migrating the test VDI from storage1 to storage2 (again) and getting an average of 400/400mbps (lower case m and b). If I do three VDI at once, I can get over a gigbit and sometimes close to 2 gigabit.

It's either SMAPIv1 or it is a file "block" size issue, bigger blocks can get me benchmarks up to 600MBps to almost 700MBps (capital M and B) on my slow storage over a 10gbps network. Testing this with XCP-NG 8.3 release to see if anything changed from the Beta, so far all is the same. Also all testing done with thin provisioned file shares (SMB and NFS). If I could get half my maximum tests for the VDI migration, I'd be happy. In fact I'm extremely pleased that my storage can go as fast as it is showing, it's all old stuff on SATA.

I have a whole thread on this testing if you want to read more.

You can see the migrate which was 400/400 and then the benchmark across the ethernet interface of my Truenas, this example was migrate from SMB to NFS, and benchmark on the NFS. Settings for that NFS are in the thread mentioned and certainly my fastest non-real world performance to date.

That's impressive!
We're not seeing as high speeds are you are, we have 3 different storages, mostly doing NFS tho. We're still running 8.2.0 but I dont really think it matters as the issue is most likely tied to the SMAPIv1.

We also noted that it goes a bit faster when doing 3-4 VDI's in parallell, but the individual speed per migration is about the same.

@planedrop said in XO - Restore Health Check:

I can confirm this is the case for me too, not a huge deal, but would be kinda nice if it could keep track of the name.

Thanks for verifying, it is probably an easy fix for the vates ppl

Hi everyone,

Has anyone else tried the Restore Health Check-feature in XO to test their backups?
I've used it now in my lab a couple of times and it works great, but one thing that bugs me out is that the name of the tested VM is no longer dispalyed after the TEST is finished because it was removed:

Instead of listing the name of the VM it just says "VM not found!"

We're using XO from sources:

Xen Orchestra, commit 8b7e1
Master, commit 587da

@Dataslak said in After installing updates: 0 bytes free, Control domain memory = 0B:

@nikade @olivierlambert @stormi @Danp @yann

Just wanted to say to you all:

Thank you for your contributions and kind helpful assistance which has helped me through this crisis.

I would have been in deep trouble without you. I respect your expertise, and appreciate deeply that you are working so hard to help us dumb users. I have learned a lot, and hope one day to become skilled enough to at least help other new users on this forum.

Best wishes
Aslak

Happy everything worked out, this is what this community is all about.
I've gotten a lot of help and given some too, it's all about helping out with the things that you can.
With time you'll be able to help out more and more and more

@DustyArmstrong thats super-strange, i actually have the same setup at home, 2 hp z240 machines running xcp-ng in a small pool.
xcp1 is always up and running, xcp2 is powered down when I dont need it, everything important is running on xcp1, maybe that's the reason I don't run into these issues.

@DustyArmstrong said in Network Management lost, No Nic display Consol:

@nikade sorry to drag this up but, is there a particular process or methodology to avoid this in the first place? Just had it happen on two brand new hosts, I had to re-install XCP from scratch. Bit worried if I reboot one of them now for any reason this will happen again. It happened on both the pool master and the slave, network completely wiped out on both.

Genuinely one of the most bizarre series of events I've ever experienced with server infrastructure, I could not understand what was going on until I found this thread.

What exactly happend? Could you try and explain in 1-2-3 steps?

I second all of @pilow points. We have been running a lot of Dell R630's with Intel CPU, Intel NIC, PERC H730i raid-cards and it has been flawless. Now we're using Dell R660's, but with newer spec's.
Tried Broadcom NIC's once, it worked, but had some weird performance issues from time to time.
Go with shared storage, NFS if possible (thin provisioning) and avoid XOSAN/XOSTOR, I don't think its battle-tested quite yet.

@olivierlambert great news, I had a feeling this was in the works! Thanks for the info.

@Pilow Well yeah, it was indeed shown under TASK but man, there's a lot of tasks:

Some kind of status would be nice on the "update" tab of the vm, as well on the pool "update" tab.

So im playing around with a test-pool i've recently setup to try and get my skillset up to date with xcp-ng and xo due to the latest Broadcom VMware changes to their partnerprogram.

I haven't been using xcp-ng a lot lately, pretty much only in my homelab as well as a colo machine that has basically been running on its own for quite some time.

I went to do what I always do when setting up a new xcp-ng machine, to the update tab and noticed there are 70+ updates in line. Nothing strange with that, this is a brand new installation, so I press the update button and after a while im seeing this:

An error occurred while fetching the patches. Please make sure the updater plugin is installed by running `yum install xcp-ng-updater` on the host.

I didn't bother too much, maybe something just went wrong? I then went on to install the 2nd machine (Im setting up a POC of 8 xcp-ng hosts in total) and I did the same thing, just to see the exact same thing.
This time I went to the stats tab, just to notice that there is indeed some load on the machine, this lead me to ssh in to the host where I noticed that it is actually running yum to update:

Is this per design? Why didn't it just tell me something like "Update in progress % done" or something like that? This makes it very hard to know whats actually going on, unless you ssh to the box and check ps.

@henri9813 Ahh alright, I understand now! Thanks for clarifying.

@henri9813 Maybe im now understaind the problem here? But a warm migration is a online migration, in other words a live migration without shutting the vm down and that is exactly how it should work.

@henri9813 Did you reboot the master after it was updated? If yes, I think you should be able to migrate back the VM's to the master, and then continue patcting the rest of the hosts.

@DRWhite85 then choose "other" as template to create a "generic" vm, then you dont have to worry about the template stuff.