Topics created by borzel

Has anyone tried importing VM with XCP-ng Center 20.04.01 to XCP-ng 8.2? I'm getting 1Mbps transfer speed.

When I connect the same XCP-ng Center 20.04.01 instance to XCP-ng 8.0 and do an import I get 100Mbps transfer speed.

Anyone can help?

I suspect the slow upload during import is related to this... https://xcp-ng.org/forum/post/34970 ?

So far working great!

@olivierlambert Excellent! Thanks!

@olivierlambert said in XCP-ng Center 20.03.00 released:

why it's not the opposite (XenCenter should change this)

This would be the logical change, which would allow all existing snapshots to work as designed. Making the change in XO would require maintenance on all existing XO-created snapshots.

Just to know the headline and interesting points, not to make a copy here 🙂

@Appollonius @borzel They've been saying that it'll be relevant for 20 years, though. 😛

@enes-selcuk I didn't get your point. Do you have a problem right now or did you just want to give advice to other people? I thought your were in trouble 🙂

(because I did pre-release the XCP-ng PV-Tools, I basically know this stuff (a bit))

@stormi Yes, it's present in both. That's what drew me to the 8.0.1 release - I hopping this was fixed from version 8.
I will go ahead and open an issue on github.

The drivers install fine on Windows 2022 21H2 (Build 20348.169).
Like previous versions, the system hangs as soon as the VIF state changes.

It's Javascript, so there's no really mandatory tools:

Any text editor supporting editor config for basic rules formatting is a good start A GitHub account Same recommendation for the dev env than running XO from the sources: NodeJS 8 and yarn

That's pretty much it.

@borzel In my humble opinion, I would say no because then you are deviating from industry standard naming. The reason for standards is so that everyone will know what you are talking about as long as you follow the standard.

Lowercase b always means bit and uppercase B always means Byte. Please do not change this. It is trivial to learn the standard. It is less than trivial when people start making up their own abbreviations for things (though admittedly this one isn't rocket science to figure out).

Since ZoL 0.8 is here, supporting O_DIRECT, everything might just work out of the box. We'll try it and report 🙂

And also:

https://github.com/xcp-ng/xenadmin/issues/186

ducarpit created this issue in xcp-ng/xenadmin open Cannot change VM RAM memory from XCP-ng Center 20.04.00.32 #186

@borzel Does this still work with current versions of the guest tools?

Thank You for the update.

@r1 the way the rook-ceph works that you pass raw disk to the Debian host and then it creates the OSD and cluster, I have few issues with this:

Adding and removing k8s nodes is just few commands and very quick and zero downtime for apps, but if I am running rook-ceph, I need to rebuild the cluster every time I do that and thats extremely time consuming and extra over head. The size of each VM that is being backed up daily/weekly is also extremely big and consumes a lot of resources and storage space.

Instead if you get a xcp-ng native local cluster that can be used by VM's as local block type SR that would simplify the implementation many times.

Wooohooooo !! We have a connection 🔌

0_1543525292373_4649e57e-4925-46e0-8aa6-84789150df8c-grafik.png

I tested on a fresh 2016 install. The install went well and the management agent was installed. I enabled VSS but the VSS snapshots don't seem to be working.

To compare I installed the citrix client tools on a fresh 2016 install and VSS does work.

Hello all together,

here is a updated version of the installer that removes also old citrix tools/drivers:

https://github.com/xcp-ng/xcp/issues/23#issuecomment-435696690

olivierlambert created this issue in xcp-ng/xcp closed Windows PV tools #23