Search results

Hi all, I've got a VM with initially about 100GB disk space which I want to enlarge. I've changed the disk size through the GUI rebooted but drive is not getting bigger. [root@dionysos ~]# df -kh Filesystem Size Used Avail Use% Mounted on /dev/sda2 115G 65G 44G 60% / tmpfs...

Thanks Fabian, they are working fine now.

Fabian, is not very clear to me what you are saying. How the rootfs is read only and is there a work around?

There must be a bug, can't be explained. I've re-formatted the server, restored those 2 VMs and then tried to create a 3rd one and it fails. Same error output as posted above.

and the diff as asked before (just replaced the hostname) root@proxmox0 ~ # diff /etc/pve/lxc/100.conf /etc/pve/lxc/102.conf 2,4c2,4 < cores: 4 < hostname: domain1.mydomain.com < memory: 4096 --- > cores: 1 > hostname: domain2.mydomain.com > memory: 4192 6,7c6 < net0...

Further to my post, just to add that any new LXC I'm creating gets the same error. This is on a clean server with a fresh installation, no modifications at all apart from the network config of course.

Hi Fabian, Here is the output with the debug option: root@proxmox0 ~ # lxc-start -n 102 -lDEBUG -F -o /tmp/lxc-debug.log unable to open file '/fastboot.tmp.27847' - Read-only file system error in setup task PVE::LXC::Setup::pre_start_hook lxc-start: conf.c: run_buffer: 405 Script exited with...

Hi LnxBill, pve-manager/4.4-12/e71b7a74 (running kernel: 4.4.44-1-pve) The VM that doesn't start is a new one, just did the OS installation and tried to started afterwards, nothing else.

It is strange however that a 3rd LXC doesn't start. Same behaviour like the 2nd one which I needed to remove it completely and create it again. The problem with this one is that it is been re-created and still doesn't start. Same template like the previous 2. I'm pasting below the debug info in...

ok it worked now. I removed and created again the LXC and works perfect. Many many thanks for your help.

This is what I did but the new LXC doesn't start at all. systemctl status lxc@101.service -l ● lxc@101.service - LXC Container: 101 Loaded: loaded (/lib/systemd/system/lxc@.service; disabled) Active: failed (Result: exit-code) since Thu 2017-03-09 22:50:36 CET; 24s ago Docs...

Thanks LnxBill. I've tried adding a 2nd LXC with .211 IP and .209 as the gateway but it doesn't start at all. Under my host interfaces file I haven't added any new vmbr. Am I missing something?

Thanks a lot for the reply, it worked fine! It's not clear however to me how the next IPs should be assigned in order to use all available IPs, from .209 to 222?

I'm getting nuts with this problem. Any help is very much appreciated. My new subnet is: Subnet: 88.99.181.208 /28 Usable IP addresses: 88.99.181.209 to 88.99.181.222 I enabled forwarding: sysctl -w net.ipv4.ip_forward=1 sysctl -w net.ipv6.conf.all.forwarding=1 In my host server I got...

What you mean a recent kernel version? The one I posted above (2.6.32-48-pve) which I got it is the latest and I got the problems with that, not the previous kernels.

I've got the same problem, any solutions?

Hi all, I've got plenty of GBs free but df -i reports: root@server1:~# df -i Filesystem Inodes IUsed IFree IUse% Mounte d on rootfs 5029888 5029888 0 100% / udev 1023481 336 1023145 1% /dev tmpfs 1024970 317 1024653 1% /run /dev/disk/by-uuid/1c56ce75-4d63-4489-9fce-c257d5269afa...

@LnxBil if you put the /etc/hostname in immutable the vm doesn't start afterwards. lxc-start 1458917760.765 ERROR lxc_conf - conf.c:run_buffer:342 - Script exited with st atus 1 lxc-start 1458917760.765 ERROR lxc_start - start.c:lxc_init:436 - failed to run pre-sta rt hooks for container...

Anyone with a suggestion on this?

Davidm, tried anything I found and simply doesn't work. I switched to KVM which works fine.