Search results

  1. B

    Proxmox VE 4.4 released!

    It's already mainline (since yesterday). Of course it's long from being considered stable or even put in longterm support, but I am not thinking in the short term. And, may be, the feature could even be backported (just a thought).
  2. B

    Proxmox VE 4.4 released!

    Hi, I hope this is the right place. What's your planning on (Intel) virtual GPU support? it's already in mainline kernel (4.10). If you have no planning, at least a very approximate ETA? It would be awesome to be able to start taking advantage of the iGPUs on E3 Xeons.
  3. B

    Full node hangs for seconds at CT/VM creation/deletion/bootup/backup (mdraid1+LVM)

    Hello, the title describes the problem pretty well. It's a single node with no cluster or any "exotic" external storage. The problem has been happening for a while now, may be some months (we've learned just to not backup entire VMs and not to restart them unnecesarily, and never at heavy usage...
  4. B

    Backup job failed with err -5 - Input/output error

    @Cerias thanks for the answer, but unfortunately that was not the problem. I couldn't even really fix it (even converting the image failed, and after filling some disk space inside the VM it "input/output error" crashed, so I think the disk image was somehow corrupt/faulty). I could save the...
  5. B

    Backup job failed with err -5 - Input/output error

    Hello, I have this very same issue, filesystem is ZFS (VM on zvol and backup storage either the very same ZFS filesystem or NFS, there is sufficient space in both and always fail at exactly the same percentaje in every attempt). This is a serious problem for me right now because my dedicated...
  6. B

    Can't ifup/ifdown alias addresses inside LXC container

    Hey, if you mean the network to work, you have to ONLY configure the vMAC, and inside the container you configure it normally (/etc/network/interfaces for Debian-based, or /etc/sysconfig/network-scripts/ifcfg-ethX and /etc/sysconfig/network-scripts/route-ethX for RHEL-based, though I haven't...
  7. B

    PVE 4.0 LXC on ZFS-Storage fails

    Thank you very much, would it be possible for it to autodetect the proper mountpoint? that would be awesome :)
  8. B

    Outdated kernel sources @ git.proxmox.com? (Proxmox VE 4.0)

    Hi, I'm not very much into compiling and sources, so if this post is fundamentally wrong for some reason, sorry in advance. For example I sense that may be using "Ubuntu-4.2.0-14.16" sources along with "config-4.2.2-1-pve" would give me the exact results I want? (no compatibility issues, lack...
  9. B

    Can't ifup/ifdown alias addresses inside LXC container

    If anyone cares at all, it now works (don't know if already fixed while beta or if after final release, but it works).
  10. B

    Can't ifup/ifdown alias addresses inside LXC container

    Hi, after the little problem I had in an OVH server with the default IP assignment way for LXC containers in latest Proxmox, they gave me a working temporary (I hope it's) solution, that basically is to only create the NIC from the Proxmox GUI, and configure the IP addresses from within the...
  11. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc Hi, the temporary solution is good enough (besides the problem I describe below), but please consider allowing the parser to not deny such networking scheme. By the way, I'm not sure if I should open a new...
  12. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc I feel dumb now, I've not tried yet but seems logic. You should consider allowing the parser to process OVH-like networking scheme, and (somehow) more than one non-consecutive IP/CIDR on a single vNIC...
  13. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc I know it's not considered valid, but it's 100% for sure the scheme used by OVH. A weird one? yes, but that is (unless one have a vRack enabled server with your own VLAN/s, that are few models). I am not an...
  14. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc Not really using "plain LXC" (I would temporarily if it's needed for the CT to have network until the bug is fixed), just I sent that config file and not the other. For being able to send you the proper one...
  15. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc I meant subnet mask not gateway T_T (gateway is hostip_first_3_octets.254 as I previously said). I will provide the config file but it's of no interest given the problem is the needed configuration isn't...
  16. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Re: lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway sc I'm so tired I accidentaly pressed enter while editing the title, it should be "LXC container 'unable to parse ipv4 address/mask' with OVH's mandatory bridged networking scheme" (if such a large title even...
  17. B

    lxc CT "unable to parse ipv4 address/mask" with OVH's bridget networki gateway scheme

    Hi, I have a non vRack dedicated server with latest Proxmox 4.0 beta2, and I want to create at least one LXC container with some public IPs. The (mandatory?) gateway for bridged VM network configuration on (non vRack) OVH dedicated servers is [First three host IP's octets].254 (for example...
  18. B

    OpenVZ released 3.X kernel

    Thanks for sharing! this is very interesting even being aware that it might be far from stable, like Neil Armstrong said: "that's one small step for an IT guy, but a giant leap for the IT industry!!"