[Unraid OS version 6.7.0-rc1 available]

   Just installed and no issues with install.  From LimeTech's feature listing I like the "under-the-hood" changes, and while I'm getting used to the new dashboard I like it. 

 

  My only initial criticism would be the banner info (top right-hand corner) and the first cell of the new dashboard is redundant information - then again, I've notice people have removed their banner, so this makes sense.  And yes, I know I can minimize the cell.  Second small criticism, I think that initial panel should have the Unraid version listed since it is listing banner info.

 

Thank you for all your work!

 

[6.6rc2 - update VM, add/remove vdisk]

Changed Status to Closed

[6.6rc2 - update VM, add/remove vdisk]

Updated to 6.6.0-rc4 and test again; working well.

Taking liberty of changing status to closed.

[6.6rc2 - update VM, add/remove vdisk]

Updated to 6.6.0-rc3 and test again.  The delete vdisk function is working correctly.  However, the "Add another vDisk" function behaves the same as 6.6.0-rc2; vdisk#.img missing from /mnt/path/domains/vmName/  and no XML generated, describing the new vdisk.

 

The "Add another vDisk" doesn't work for vms generated on rc3, or prior Unraid-version-vms (if that matters).  "Adding another vDisk" function does work from, //tower/VMs/AddVM (same function call between AddVM and UpdateVM, or are they different?).  

 

 

hydra-diagnostics-20180914-1604.zip

[[6.6.0 RC1] Docker CPU utilization reporting over 100%]

7 hours ago, Zack Pollard said:

Also dividing it by system cores or pinned cores, which makes more sense?

My answer is pinned cores. The stat is CPU usage of the container, and if one has pinned the cores that's the container's allocated cpu. Therefore (100% cpu) ==  (1 / ( X pinned cores) ) * ( sum( X pinned cores usage)   [ unit analysis: percentage = (no units)(percentage) ; OK ] 

 

If no pinned cores then let "X pinned cores" equal one, prevents divide by 0 and goes away in equation. 

 

An argument for this arrangement, say a user is unsure how much cpu to provision for a server, the user will better presentation of any over-head as it's provisioned. If the equation was 1/(all cores) if the container maxes out 100% would register as X / (all cores), and I could see some users think the container is OK because the CPU is never maxed - all the while the container could be choked up. 

 

Just my two-cents when I saw this bug today.