Search results

Oct 4 14:56:56 pve kernel: [56775.890084] device veth101i0 entered promiscuous modeOct 4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request Oct 4 14:56:58 pve lxcfs[1728]: call to list_children (name=systemd:/) failed: invalid request Oct 4 14:56:58 pve...

Another Pool, The problem only happens if the ZFS is busy/bogged down with I/O when you try and create the container, Id hope in a production system no one would let ZFS get that bogged down, but I can see it happening on lab system and also low end boxes such as the kind people tend to get...

Hmm I wonder if I've broken apparmor when adding NFS to the exceptions Weird thing is it's specifically the 15.04 container that causes that, the 14.04 image works perfectly even if I create a new container for it.

I'm not sure if it's something in my setup or if the Ubuntu 15.04 lxc template is broken, the containers create ok but when you start them they sit there using a few MB of ram and nothing else happens, Nothing at all on the console and also no DHCP occurs either. Debian 8 and Ubuntu 14.04...

mount: special device /Vms1/subvol-105-disk-1 does not existmounting container failed - command 'mount -o bind /Vms1/subvol-105-disk-1 /var/lib/lxc/105/rootfs/' failed: exit code 32 extracting archive '/zfsdata/dump/vzdump-lxc-105-2015_10_04-09_08_18.tar' Total bytes read: 1163151360 (1.1GiB...

It seems the default configuration blocks NFS mounts from within the LXC containers Although thankfully easy enough to fix. On the proxmox host add mount fstype=nfs, to /etc/apparmor.d/lxc/lxc-default-with-mounting then reload apparmor service apparmor reload Edit: Werid this worked...

Seems to be working other than an issue with LXC but I think I know why that is. I think it's because I had a second Zpool and its root was mounted locally as a directory, it seems to be automounting subpools in the wrong directory which is tripping up the container creation scripts.

Got this one when creating a LXC container on a zfs file system Disk's were under load at the time, it looks like the command did execute just took longer than proxmox was prepared to wait. Since lets face it people ARE going to put this on underpowered boxes in Homelabs/Cheap hosts.etc is it...

I like living on the edge, so I think I'll try the same, Worstcase I can always reinstall over the top, should have installed v4 to start with but went with 3.x even though it's just a personal box (i.e not doing anything critical)

I'm having this happen with a "Rockstor" appliance that seems to be based around centos7, usually when the Virt-Net is under high load. Currently there is a lot of network traffic between my VM's because I'm trying to use Virtualbox to convert a 200GB vhd file for a ubuntu VM into something...

Please consider supporting adding a HDD serial number in the .conf files, or at least randomly generating one. I was able to do it via the args option but it would have been a lot cleaner if I could have just put ,serial= in the config file...

I had a scary this morning stating that the automated backup I run on one of my Proxmox hosts had failed. It turns out it failed on the following - 105 Ubuntu-storage FAILED 00:00:01 empty device list VM105 actually has a single disk that is set to "No Backup" so the reason it failed is...

Will promox even actually let you create a cluster across to different data centres? Obviously unless you somehow link them over L2TP or some other form of VPN so the IP's can route to the other box it's likely that Migrate wouldn't work but it might still be useful for the ablity to "see"...