Although it is nice that there is work arounds for the DNS spikes with either nscd or the in-process DNS cache, i think the DNS spikes are a symptom of a whole different issue.

I think we can safely assume that each DNS lookup is corresponding to one attempt at establishing a TCP connection then there is some code somewhere that spawns an awfull lot of short lived connections instead of reusing / pooling them - with all the issues that follows in that area (insufficient ulimit NOFILE, connections in TIME_WAIT/exhausting of client ports etc)

LeMatz
In the first picture of "hostname and dns configuration":
It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

When I (re)build on my 3 GB vm i use this before in order to keep nodejs at bay

export NODE_OPTIONS='--max-old-space-size=3072'

And then it runs smoothly

AlexanderK
before you spend more time on this i just want to make you aware of the fact that installing OSX on any non-apple hardware will breach Apple's EULA

From the blog post

Size: grow a VDI in size. It's fully thin provisioned!

Does this mean we finally have live/hot disk expansion ?

What is current status? What is the rough expectation of next alpha/beta release

If you should come with a highly insecure guess - when would you estimate that we see the first 8.3 alpha/beta release

When I (re)build on my 3 GB vm i use this before in order to keep nodejs at bay

export NODE_OPTIONS='--max-old-space-size=3072'

And then it runs smoothly

AlexanderK
before you spend more time on this i just want to make you aware of the fact that installing OSX on any non-apple hardware will breach Apple's EULA

Andi79
Is the problem occurring both when the vm's are on HDD and on SSD storage or only on HDD ?

Seems like it's also reported upstream
https://bugs.xenserver.org/projects/XSO/issues/XSO-1021

Although it is nice that there is work arounds for the DNS spikes with either nscd or the in-process DNS cache, i think the DNS spikes are a symptom of a whole different issue.

I think we can safely assume that each DNS lookup is corresponding to one attempt at establishing a TCP connection then there is some code somewhere that spawns an awfull lot of short lived connections instead of reusing / pooling them - with all the issues that follows in that area (insufficient ulimit NOFILE, connections in TIME_WAIT/exhausting of client ports etc)

LeMatz
In the first picture of "hostname and dns configuration":
It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

https://github.com/ronivay/XenOrchestraInstallerUpdater has just added experimental support for provisioning a XO proxy