Search results

  1. J

    unable to install: "no cdrom found"

    I've installed proxmox a bunch of times and this is the first time I have got this error. Installing on an older reclaimed system. Thanks to the script posted above I have found that it is the "-t iso9660" argument to the mount command. With it, I get the same error I see on boot. Without it...
  2. J

    Proxmox 4.0 - Previously running LXC container won't start

    It's not a major update though. So you can't just apt-get dist-upgrade and reboot??? I think you've got more than just this problem then.
  3. J

    Proxmox 4.0 - Previously running LXC container won't start

    Yes. Update to 4.2 as per my post above.
  4. J

    Proxmox 4.0 - Previously running LXC container won't start

    Things are still happy after more than 2 weeks.
  5. J

    Proxmox 4.0 - Previously running LXC container won't start

    Just thought I would add this. After upgrading to Proxmox 4.2 yesterday I don't appear to be having this problem anymore. I'm pretty sure it was being caused by the bonded Ethernet interface. Proxmox 4.2 brought with it kernel 4.4.8-1-pve which appears to have fixed things. I won't be 100%...
  6. J

    Proxmox 4.0 - Previously running LXC container won't start

    Here's two: root@destiny:~# pct config 101 arch: amd64 cpulimit: 2 cpuunits: 1024 description: Ansible Configuration Management%0A hostname: young memory: 1024 net0: name=eth0,hwaddr=5E:91:7C:9D:C7:F7,bridge=vmbr0,ip=10.13.1.1/24,gw=10.13.1.254 onboot: 1 ostype: debian rootfs...
  7. J

    Proxmox 4.0 - Previously running LXC container won't start

    Output is: RTNETLINK answers: No buffer space available Dump terminated unable to add default vlan tags to interface veth400i0 lxc-start: conf.c: run_buffer: 342 Script exited with status 25 lxc-start: conf.c: lxc_create_network: 3084 failed to create netdev lxc-start: start.c: lxc_spawn: 954...
  8. J

    Proxmox 4.0 - Previously running LXC container won't start

    Oh, further to this, I tried starting from the command line again and get the same output. So I removed the network device from via the web interface and the container started up fine. It's a bit useless to me without an ethernet interface but definitely points to a networking issue.
  9. J

    Proxmox 4.0 - Previously running LXC container won't start

    This has become a bit more of an issue now. I'm now unable to start any new containers. Previously, I thought it was fixed in an update but turns out that rebooting just made it work for a bit longer than usual. Now though, I can't start any containers that weren't started on boot. Out put...
  10. J

    Proxmox 4.0 - Previously running LXC container won't start

    Got a bit of a problem with my shiny new LXC containers. When the system boots, everything starts up fine and is running very well. However, when I shutdown a container from the web interface regardless of whether I make a change or not, I'm unable to restart the container. Task output...
  11. J

    CT startup options?

    Hi all, with the update to 2.1 in documentation on the wiki for Virtual Machine Startup and Shutdown it states, "You can configure virtual machines (VM) and containers (CT) to start up and shut down with the host. Additionally, you can set the default timing and start-up order for selected VMs...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!