Recent content by littletiger

Tested fine! NFS within OpenVZ is ok once again. Thanks very much for the quick release!

Great News! Thanks very much for that. That NFS bug is massive pain, I was hoping they did not mean months :)

About the patch to fix this NFS bug for OpenVZ on 2.6.32. Does anyone knows what's this "missed the boat" means: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613170#59 How long do we have to wait for "the next" stable release ?

Comment: Proxmox VE 2.0 UI Just quick comment about using ExtJS for GUI. If you have already started using ExtJS then probably can ignore this comment. If you have not yet, then it might be worth taking a look at jQuery. To be fair, Ext JS is great for quickly getting well defined and good...

No, I have only been playing with Proxmox 2.6.32. They have moved the I340 out to another box, so I do not have a chance to try it on Proxmox 2.6.18 at this stage. Not quite sure what igb is on Proxmox 2.6.18, but if it is not igb_2.3.4, then it might work.

We tried the I340 on different 64-bit distributions and machines: 1. CentOS 5 - works immediately 2. Ubuntu 10.04 - works immediately 3. Debian Squeeze - needs update to igb_2.4.8 4. Proxmox 1.6 - needs update to igb_2.4.8 So looks like igb_2.3.4 was the problem for us.

I tried igb_2.4.8 again and it now works! Thanks very much of your help Tom.

We are playing with the latest Intel I340 Quad Port LAN card: http://www.intel.com/Products/Server/Adapters/esa-i340/esa-i340-overview.htm It is the first quad port to have PCIe Gen. 2.0 ... so very cool! However, it is WORKING with: * Ubuntu 2.6.32-24 (10.04) * igb driver 2.1.0-k2 But it is...

Sources for 2.6.24-12 (resolved) Sorry, NOT needed any more. I cannot delete this thread that I have started. Please ignore it. Sorry again for any inconvenience caused.

The Proxmox guys are always helpful and great with suggestions. It is not about whether Proxmox is open, it is about whether suggestions make sense. Developing 2 containers (Openvz and LXC), at this stage, will defocus EVERYONE. We already have the extra KVM virtualisation to handle ...

Thanks Tom, will try again then.

Previously I downgraded frompve-kernel-2.6.32-2-pve: 2.6.32-7 to pve-kernel-2.6.32-1-pve: 2.6.32-4 in order to reduce the Load Average. I saw that pve-kernel-2.6.32-2-pve: 2.6.32-8 is now available and upgraded to it. But the Load Average problem came back... Are there plans to...

Thanks for your detailed help, that worked great! CPU% dropped from about 3.9 to about 1.6. Although not as good as with 2.6.18 kernel, it is still a significant improvement for the 2.6.32 kernel. Thanks again.

Thanks very much for your reply. That was just the KVM process itself (the rest of the processes are all showing zero). Sorry, I made a mistake before it was not 1.8%, it was actually 4% with 2.6.24 and 2.6.32 kernels (compared with 1% of 2.6.18) You can see very clearly when we were using...

Thanks for your reply. Looks like I will need to run 2.6.24 or 2.6.32 then, it is a pity that those kernels use twice the amount of CPU running KVMs than 2.6.18 ... But that is for another thread :) http://forum.proxmox.com/threads/3969-CPU-Utilisation-2.6.18-vs-2.6.24