Search results

  1. L

    [SOLVED] Fresh Proxmox Install with /dev to be fully populated error

    Re: Fresh Proxmox Install with /dev to be fully populated error I just installed Proxmox VE 3.4 and had the same problem: black screen after "Waiting for /dev to be fully populated". The graphics in my test system is integrated in the CPU (Intel Pentium G3220 - Hashwell architecture). Editing...
  2. L

    System freeze after kernel error in latest Proxmox VE 3.3

    Thank you for your answer, e100! I also have googled a lot finding 2.6 kernel bugs giving similar errors. I don't have any NFS resource mounted on this server (it only uses local storage), so I'd exclude anything related to NFS. Any other ideas? Thank you very much!
  3. L

    System freeze after kernel error in latest Proxmox VE 3.3

    Hello! I'm getting random freezes (every some hours) of a system running latest Proxmox VE 3.3 with kernel 2.6.32-34-pve. Just before the freeze, this is logged into the syslog. Do you have any idea? I tested the memory with MemTest86 for hours: 100% sane. Thank you very much! Dec 12 19:58:53...
  4. L

    Option async in storage.cfg is ignored in PVE 3.2

    Thank you very much Mr.Holmes, good to know!
  5. L

    Option async in storage.cfg is ignored in PVE 3.2

    Hello, I'm trying to mount a NFS share asynchronously and without remote locks. I added 2 options to my storage.cfg, changing options vers=3 to options vers=3,async,nolock Then I rebooted and run a cat /proc/mounts: 10.0.0.252:/proxmox /mnt/pve/proxmox nfs...
  6. L

    100% Disk space on OpenVZ

    I had the same problem in Proxmox 3.2-4 (I manually deleted some files from the private folder on the host) and running the following commands fixed the problem (thanks dietmar): # vzctl stop <vmid> # vzquota drop <vmid> # vzctl start <vmid>
  7. L

    Memory usage indication for OpenVZ containers

    Hi all! First of all, congratulations to the developers of this AWESOME virtualization platform! Second, I have an idea to suggest to the developers: at the moment the Proxmox GUI shows just the "used memory" of a VPS, which includes memory used by the programs + buffers + cache. I think that...
  8. L

    Openvz and rc.local

    I have the same problem with the same template :( Any solutions? My problem is only the rc.local not executing (although it is 755 and so should be executed). I don't have the map problem. NOTE: If I run "/etc/rc.local" from shell, it correctly executes! It just doesn't run at boot
  9. L

    High risk security bug in Proxmox VE 1.8?

    You're right, done! ;-) EDIT: Oh, no, the main title is not changed...So I ask the admins to kindly do it (you can delete it!).... Sorry for all this mess, I'll check the accuracy of OpenVas results next time ;-)
  10. L

    High risk security bug in Proxmox VE 1.8?

    Ahaha, I have no idea what the hell OpenVas found (he seemed to be very sure)... I'm sorry, I'll check it now to understand why the hell he did say that...
  11. L

    High risk security bug in Proxmox VE 1.8?

    Ignore me, false alert [NOTE: The following is a false alert, so don't care about it...It was an error of OpenVas obviously....I'm sorry!] Hi All, I set up a Proxmox VE 1.8 environment, all default, with Shorewall firewall configured. Then I updated it all (apt-get update and apt-get upgrade)...