Search results

  1. B

    [SOLVED] LXC Container didn't start

    Ok, thank you. I will tried it next time, for now it works :-)
  2. B

    [SOLVED] LXC Container didn't start

    I solved this now. I mounted the raw image with (mount -o loop image.raw /mount/point/) and then add this "pve-ignore" files. Now the vm starts. Thank you!
  3. B

    [SOLVED] LXC Container didn't start

    Ok, thank you. But I cannot start the VM. Is there an other way to start my vm?
  4. B

    [SOLVED] LXC Container didn't start

    A little update. In the container runs a software which controles "/etc/hosts, /etc/hostname, /etc/resolv.conf". It is important that this files didn't change. Perhaps the software manufactor has changes something in the vm that this files cannot be changes. This could be the problem because on...
  5. B

    [SOLVED] Static IPv6 - Lost route after a while

    Hi, I tried net.ipv6.conf.eth0.accept_ra=0 but this didn't help. But the problem is gone. Perhaps there was a mistake in the network. Thank you.
  6. B

    [SOLVED] LXC Container didn't start

    Hi, I updated a few openvz container to lxc. One of them didn't start. I get the following message: lxc-start -lDEBUG -o 151024082_start.log -F -n 151024082 close (rename) atomic file '/etc/hosts' failed: Die Operation ist nicht erlaubt error in setup task PVE::LXC::Setup::pre_start_hook...
  7. B

    [SOLVED] Static IPv6 - Lost route after a while

    Hi, I have a strange problem. I use a server at ovh with ovh proxmox 4 template. IPv6 is working. I defined static entries as described in the wiki. But after a while i cannot access the vm via ipv6. When i make a ping from the vm to any ipv6 address, i get the message network is unreachable...
  8. B

    [SOLVED] LXC IPv6 Problem

    Hi Ovidiu, I could fix it this way: 1. Stop VM 2. Delete VM network interfaces via webgui 3. Start VM 4. Clear /etc/network/interfaces 5. Stop VM 6. Add VM network interfaces via webgui - MAC: generate a new mac for your failover ip in ovh customer interface and copy this here - IPv4...
  9. B

    [SOLVED] LXC IPv6 Problem

    I could solve the problem. It was an vm which I migrated from openvz. It looks like the interface config wasen't correct. There were old entries from openvz. Removing this didn't do the trick. So I removed the interfaces config and added network config via webgui again. Now it is working. So i...
  10. B

    [SOLVED] Proxmox 4.2 GUI problem

    I allowed always pop-ups from the website and now the problem is gone.
  11. B

    [SOLVED] LXC IPv6 Problem

    I followed this article but it doesn't work. I also disabled the firewall. Ping from host to google works. Ping from vm to host works. Ping from host to vm didn't work. Ping from vm to google didn't work: PING google.de(par10s22-in-x03.1e100.net) 56 data bytes From par10s22-in-x03.1e100.net...
  12. B

    [SOLVED] Proxmox 4.2 GUI problem

    Clearing browser cache didn't help. proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve) pve-manager: 4.2-2 (running version: 4.2-2/725d76f0) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.2.8-1-pve: 4.2.8-41 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-39 qemu-server...
  13. B

    [SOLVED] LXC IPv6 Problem

    Hi, I updated one Server (at OVH) to Proxmox 4.2. I make a new install with ovh template. IPv6 on Host side works but in lxc vm not. Here my config: Host: iface vmbr0 inet6 static address x:x:x:x:: netmask 64 post-up /sbin/ip -f inet6 route add x:x:x:xff:ff:ff:ff:ff dev...
  14. B

    [SOLVED] Proxmox 4.2 GUI problem

    Hi, I updated one Server (at OVH) to Proxmox 4.2. I make a new install with ovh template. In the gui I have a problem. If I click something with a new box (add nfs storage, or add network, etc) it takes a long time and the box layout crashs. It will be schown in the left top corner and i cannot...
  15. B

    pve-firewall status update error

    Hello, in syslog I saw a lot of this lines: pve-firewall: status update error: ipset_restore_cmdlist: ipset v6.12.1: Error in line 2: Set cannot be destroyed: it is in use by a kernel component Does anyone know what this mean? Greetings Alex