If I had my choice, Prevent Migration is more understandable.

Disable Migration, while it means the same thing, doesn't naturally come out of the English language.

@olivierlambert I was able to sort out the issue, it has to do with licensing and the fact that we aren't licensed to with "Live Migration" for this ESXi host.

Essentially this inquiry is solved.

@TechGrips While I can understand the desire to use removable USB as a Backup Repo, I would highly discourage it.

Managing and rotating USB drives is a pain, if they go to sleep, it's a pain, if they fail it's a pain, if you forget to rotate your drives, it's a pain.

I personally can understand the desire to do so, it's cheap and relatively affective if you can deal with these risks, however so is just using any NFS or SMB share and then having a replication script that could write to your USB, which you could then rotate. Separating your XCP-ng hosts, XO, and your backups is of critical importance because if you have any sort of server room environmental issues or failure, you're risking loosing everything.

XCP-ng and Xen Orchestra, while they do offer a ton of flexibility, there is obviously trades-offs to using less than ideal components, such as external USB drives as your primary backup repository.

If you really want to insist on using USB drives, you'll have to attach the drives to your host and then pass them through to your XO installation, which when you want to rotate those drives you'll have to update your Backup jobs within XO and confirm that your XO VM has the proper access to the drives. This seems like a lot of complexity for very little financial benefit.

Separately I think you're taking your own frustrations out on the community, because of a lack of understanding in the tooling that you testing in comparison to ESXi where you'd attach a USB drive directly, perform your backup, remove the disk and attach another.

I get that ESXi can make things "simple" but simple isn't always better.

HTH

The reason you wouldn't want to look at XO for this from a technical standpoint is because XO works at the hardware level of the hypervisor, dolling out resources to different VMs and creating backups.

You need to look at the content within a given VM and compare the file system difference from points A and B.

Only something that is operating within the file system would be able to readily tell you "Something has changed".

Odds are you have a user or several who are dumping files onto a share that they shouldn't be, or are replicating some cloud service to keep a copy on your server etc.

@flakpyro said in How to migrate XOA itself?:

@DustinB Are the any downsides to having two XOA instances pointing at the same pool? Since the config itself is stored at the pool level im guessing theres no downside?

IE: Priimary XOA running in core DC and secondary XOA running at your DR site. Is it just a matter of adding the pool on the secondary XOA and it downloads the existing config or did you need to do a full export / import?

If you import your configuration, each XO instance will think they should be running the backups as far as I've noticed. If I have two instances running with the same configuration, I simply disable the backup jobs on one of them.

The config file is just an XML that contains your existing instance. You can import it to any new XO instance and have the same exact configuration.

@yzgulec there really isn't any hard-fast rules to aligning CPU to vCPU. A Guest is going to need cores to operate no matter what.

If you're trying to min-max your CPU utilization for a given system, you might want to target the guest to use between 70-80% of it's vCPU all of the time.

This is all a part of system tuning and is always a shifting target, as CPU is shared among all VMs and DOM0.

As you increase the number of guests on a host, the CPU consumption will be increased, which means you may need to scale back on the vCPU a given VM has.

@stormi said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

Do others share this feeling and have this question after re-reading the whole announcement?

No it's pretty clear, update the drivers on everything as all versions are susceptible.

@olivierlambert I agree wholeheartedly with you on that. Keeping the system stock is best for support.

Separately, is there any planned work on officially integrating support for Uninterruptable Power Supplies and XCP-ng 8.3?

A question

• Have you clicked into the console screen before hitting F12?

You can disable all of the boot devices in the Advanced section of the VM, try disabling the HDD

Disable the Boot options if your system is making it past POST to quickly so you can get into the Guests BIOS.

@jasonnix said in A question for the creators of XO:

Hi @olivierlambert,
No, I'm not a bot. I asked it because I need your experiences. I want to make a panel for Xen.

So you know how to program with PHP and Ruby and not with Javascript, so the question is really "Why can't this be rewritten so I can help?"

@Danp said in Recommended DELL Hardware ?:

@DustinB said in Recommended DELL Hardware ?:

With local storage on each hosts, you won't be able to live migrate from 1 host to the other.

That's incorrect. The migrations will take significantly longer because the VDI will be migrated along with the VM's memory, but you can live migrate VMs between hosts even if the VDI are stored on local storage.

Sorry, I'm probably using a lazy definition of live migration. I know the VM and its memory can move.

Doesn't using non-shared storage ultimately cause the VM to be started on the other host?

@Pilow said in Recommended DELL Hardware ?:

@DustinB if he has CR, he could stop it, Failover, patch primary host, and eventually failback or reverse CR job

Yeah that would work, but would force some amount of downtime. Which most people say "we can't afford 5 seconds of downtime in a year" and then in the same breath say they have almost no budget.

@giejo said in Recommended DELL Hardware ?:

@Pilow thanks, don't want XO STOR for this use case, i just need one server in a room and the other in another.

Are you planning on performing Continuous Replication job from 1 host to the other? Just trying to gauge what your plan is for the split hosts to make sure you're not missing something.

With local storage on each hosts, you won't be able to live migrate from 1 host to the other. Singular Shared Storage (like a single Synology) creates a single point of failure, that you may want to avoid (but that needs clarification).

Where as two servers, each mirrors of each other with local everything, and just replicating VM's to each other every minute or so might be sufficient for your environment.

Of course you would still need to consider how you're going to patch the pool, since you won't be able to live migrate with shared nothing..

Pretty much anything would work, it would be recommended that you use current hardware. Current being a CPU not older than 5 years.

Ideally using shared storage, either using XCP-ng's VSAN offering or something like a NAS or SAN so you can migrate your VMs as needed.

Intel or AMD doesn't effect the equation, just don't use ancient hardware. If you need an HCL, I'd recommend you take a look at what Citrix has for their HCL and go off of that list, and having installed XCP-ng.

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

@DustinB

Yes dark mode light mode work just fine. Just themes do not stay applied. I tried from different computer and different browsers same results.

Win 11 pc with chrome and brave.
Ubuntu desktop - Brave and fresh install Firefox.

I even changed the domain name my XO-CE uses and same difference. It will stay working if i dont close the browser. The moment i close all tabs to the browser it defaults back to the default theme.

Open to other ideas.

I'm not surprised that it isn't "keeping" between different computers and to a lesser extent browsers.

Odds are it's a client-side cookie and nothing is saved to XO for your user account preference.

Interesting though.

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

Also themes are still not staying applied. Same with XOA.

Do you mean the light, dark and auto mode?

I've not had any issue with either XOA or my XOCE installs keeping my selected mode.

@blueh2o the community is going to need some help from you.

Are you using XOA or XOCE?
If using XOCE, what version?
What version of XCP-ng is installed on your host
What backup medium are you using, NAS, cloud, windows server?

More details please

@acebmxer Yeah a ~15 minute VM migration isn't unacceptable either right? Like any DR plan can simply put that into effect.

But maybe someone else has some ideas.

The 21.46MiB is per second, which is approximately 1/5 of a GB per second.

So that really all kind of tracks...

@acebmxer From the looks of it, I would assume you have a 1GB network interface somewhere in the mix. A switch or something...

But I don't think you should expect to get a full 1GB wire speed in this case either...