[PVE-User] Stability problems in PVE 1.1?

Venefax venefax at gmail.com
Fri Feb 27 18:59:40 CET 2009


I will try again when the next version of KVM is released. Red Hat just
released its latest version. 5.3 and it did not include KVM. They know.
I think that Proxmox should consider troubleshooting the Dell Manager issue.
The software is there, it installs, but it rejects the user name and
password. If one hardware component is faulty, and you cannot use the Dell
manager... how do you identify the issue with Dell's support? That exactly
happened to me. The memory was bad. But the most important task is to be
able to detect obsolete firmware, like the raid firmware. In summary, unless
the Dell Manager works it is absurd to use Proxmox in production. Since Dell
represents 40% of the server market, it is Proxmox-Debian who has to support
Dell, and not the other way around.


Federico 

-----Original Message-----
From: Shain Miley [mailto:smiley at npr.org] 
Sent: Friday, February 27, 2009 12:51 PM
To: Martin Maurer
Cc: Venefax; ttcom at mellonway.com; proxmoxve
Subject: Re: [PVE-User] Stability problems in PVE 1.1?

Also,
I am using Proxmox in production on several DELL 2950's and two 1950's 
just fine.  I am running both OpenVZ and KVM servers without issue.  I 
cannot speak about the HP or IBM hardware...however I have had no major 
issues on my setups (other then one NFS issue that was resolved when 
OpenVZ released a new kernel).

I think there is still a little bit of room here to try and diagnose the 
issue and resolve the problem before we just write off a whole project 
and an entire distribution...one that has been working well more quite a 
few folks.

Shain

Martin Maurer wrote:
>> -----Original Message-----
>> From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-
>> bounces at pve.proxmox.com] On Behalf Of Venefax
>> Sent: Freitag, 27. Februar 2009 16:52
>> To: ttcom at mellonway.com; 'proxmoxve'
>> Subject: Re: [PVE-User] Stability problems in PVE 1.1?
>>
>> I had to abandon Prxmox VE because of similar issues, including memory
>> running out on an openvz container. But I believe the main issue is
>> Debian,
>>     
>
> [Martin Maurer] 
> The main issue is for sure not Debian. KVM is currently under heavy
development and there is fast progress in stability from week to week. For
most people it is quite useable already but I agree KVM  could be more
stable especially for windows multiprocessor guests and virtio (also I am
waiting for the windows virtio block drivers). 
>
>   
>> because Dell does not support Debian and the drivers, in my opinion, are
>> not
>> the same quality of the Red Hat (Centos) or Suse drivers, which are
>> supported. So Proxmox should have chosen a better underlying OS, instead
>> of
>> Debian. Now look at this: in a corporation we only buy Dell, HP or IBm
>> servers, because they do have 4 hour hardware response support. Not even
>> Supermicro gets in. Proxmox has a great product but it should run on an
>> enterprise-class OS. I spent two days with Dell trying to install the
>> Hardware Manager on Debian, to see of there are issues with memory,
>> processor or disks, and Dell could not make it work. You cannot deploy a
>> machine on a rack that you cannot manage.
>> Federico
>>     
>
> Dell has no management software for deb based systems (Debian/Ubuntu) and
that's why you think Proxmox choose the wrong distro? You should blame Dell
that they do not support a huge part of the Linux market. But as far as I
know, they are working to support Ubuntu which is more or less identical to
Debian/Proxmox VE Kernels.
>
> Br, martin
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>   




More information about the pve-user mailing list