UnRAID with Ubuntu VM - slow??

[SliMat]

Hi All,

 

I am not sure whether this is an UnRAID problem or something else... so I am going to throw this in to the forum and see what advice I get

 

OK, I have been running a website in an Ubuntu VM on my HP Microserver G8 for a year+ and its been fine. I recently installed a new instance of UnRAID Server Plus on an HP Proliant DL380p Gen8 and have hosted it in a data centre... I copied the Ubuntu VM image over to the new server and created a new VM in UnRAID pointing it to the VM image I copied over. Everything works, except it seems quite slow... given that this DL380 has 16 CPU cores and 104Gb RAM, compared to the limited Microserver resources. As an example there is a fairly complicated PHP script which took about 1 - 2mins to run on the Microserver... but on UnRAID it takes about 4-5 minutes... so is much slower.

 

As a comparison, I moved my Microsoft Small Business Server 2011 over to the new machine in the same way as my Ubuntu machine and it is massively improved

 

So... does anyone have any ideas? The only noticable difference I have spotted is that when I created the Ubuntu VM on the new DL380p, it shows the machine type as Q35-2.11 (it selected this by default) whereas on the Microserver the Ubuntu VM shows as Q35-2.7.

 

The logfile in the DL380p Ubuntu virtual machine shows no errors, just a few warnings;

 

2018-09-23T09:32:45.842864Z qemu-system-x86_64: warning: no scancode found for keysym 0
2018-09-23T09:32:45.843066Z qemu-system-x86_64: warning: no scancode found for keysym 0
2018-09-23T09:32:45.843632Z qemu-system-x86_64: warning: no scancode found for keysym 0
2018-09-23T09:32:45.908115Z qemu-system-x86_64: warning: no scancode found for keysym 0
2018-09-23T09:32:45.910813Z qemu-system-x86_64: warning: no scancode found for keysym 0

 

While the logfile from the DL380p UnRAID server also has a few warnings to do with the sensors, but no errors yet;

 

Sep 24 16:22:13 DL380p-Rack kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
Sep 24 16:22:13 DL380p-Rack kernel: ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170728/power_meter-338)
Sep 24 16:24:03 DL380p-Rack kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170728/exfield-427)
Sep 24 16:24:03 DL380p-Rack kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
Sep 24 16:24:03 DL380p-Rack kernel: ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170728/power_meter-338)
Sep 24 16:42:14 DL380p-Rack kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170728/exfield-427)
Sep 24 16:42:14 DL380p-Rack kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
Sep 24 16:42:14 DL380p-Rack kernel: ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170728/power_meter-338)
Sep 24 17:21:17 DL380p-Rack kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170728/exfield-427)
Sep 24 17:21:17 DL380p-Rack kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
Sep 24 17:21:17 DL380p-Rack kernel: ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20170728/power_meter-338)
Sep 24 17:24:56 DL380p-Rack kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170728/exfield-427)
Sep 24 17:24:56 DL380p-Rack kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)

 

So anyone got any ideas?

 

Thanks in advance