I upgraded to 6.3.2 and have a memory leak of some sort. Post below.

 

I tried rolling back to 6.2.4 and although it booted up ok, Docker says I need to re-download the image due to a bug and only one of my VMs appears (a Mint VM)

 

libvirt.log showed the following.

 

3+0000: 16742: info : libvirt version: 1.3.1
2017-03-02 23:52:46.633+0000: 16742: info : hostname: Tower
2017-03-02 23:52:46.633+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.633+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.634+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.634+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.635+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.635+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id

 

How can I get my VMs and dockers working again back in 6.2.4?

 

Thanks!

 

 

 

 

Edited March 7, 20179 yr by al_uk

Bump - Anyone any ideas on how to get the VMs working back on 6.2.4? 

maybe save the disk image elsewhere and do a clean unraid install on 6.2.4, then reimport the images and recreate the vm? might cause issues though if your vm is dependent on the uuid..... if you have an extra usb, you could download the trial and see if it will work that way. I would also use a copy of the vm image just to be safe.

I have moved the workloads from my main server to my test server which is also running 6.3.2.

 

The ONLY things now running on my primary server are base unRaid CIFS and NFS shares, and the plugins. Docker and KVM have been disabled.

 

My plan is to move the workloads back one by one.

 

But, how do I see whether I have a memory leak or not? My dashboard say that I am using 4% of memory, and my system stats say that only 500MB is free because the rest is used as cache.

 

In my original problem, the dashboard did not indicate a problem, it was only when the out of memory manager started killing services that I discovered a problem.

 

cAdvisor also just says that 97% memory is in use.

 

Here is my original post.

 

 

 

 

tower-diagnostics-20170307-1402.zip

CAdvisor is reporting the memory in use including cache. Which is correct because unused memory is wasted memory.

The dashboard excludes cache. Either way you're fine

Sent from my LG-D852 using Tapatalk

Server just failed again.

 

Base unRaid and plugins only, with CIFS and NFS access. Diagnostics from this morning are 2 posts above. The server works fine for a few hours. Then appears to run out of memory. This only happens since I upgraded to 6.3.2

 

 

All CIFS and NFS access has stalled.

 

The console is responsive at the login prompt, but if I press root [enter] the cursor just sits there, with no further messages. I can return to the login prompt by pressing ctrl-c

 

There is a sysrq help message - see screenshot.

 

 

 

 

 

On 3/4/2017 at 11:19 AM, al_uk said:

only one of my VMs appears (a Mint VM)

 

libvirt.log showed the following.

 

3+0000: 16742: info : libvirt version: 1.3.1
2017-03-02 23:52:46.633+0000: 16742: info : hostname: Tower
2017-03-02 23:52:46.633+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.633+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.634+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.634+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.635+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id
2017-03-02 23:52:46.635+0000: 16742: error : virDomainDefParseXML:15455 : unsupported configuration: unsupported HyperV Enlightenment feature: vendor_id

 

How can I get my VMs and dockers working again back in 6.2.4?

I'm not sure about the instability, but for the error above, 6.3.2 adds an extra line in your XML in the hyperV section referencing vendor_id. When I rolled my server back to 6.2.4, I deleted that line from the Windows 10 VM's xml, and it came back...

Thank you DB.

 

I have stopped the crashing for now by disabling most of the plugins. So have not rolled back to 6.2.4 at this point.

No Worries! Glad to hear the crashing has stopped!

 

I should probably mention that I plan on moving back to 6.3.2. I don't believe it was my issue. I'm fairly sure it was my automatic VM backup script that was force-shutting down my Windows VM, and then restarting it. After rolling back, I still had W10 VM issues, but once shutting off that script, my problems went away.