Search results

Im sorry, i was talking about he quotas on lxc container.

Is there any updates on this issue ?

Im in the same situation, but no response on this issue from anyone on the proxmox team

Bump!

Hi everyone, Im having a strange issue with lxc containers and ipv6. I set on every machine fe80::1 as ipv6 gateway. When using kvm, it comes up at boot it can ping externally any unicast ipv6 in the world, but when doing exactly the same in LXC, it takes time to start pinging (between 120 and...

After filling a bug with debian systemd maintainers the response was this: Can you disable AppArmor confinement and try again? (with lxc 3.x that means setting lxc.apparmor.profile = unconfined) Or use the config options from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916644 Please...

@t.lamprecht should i file a bug on debian on systemd package ?

Yes, it's working, at least for now i can continue testing. Thank you.

I'd try but that package (systemd_239) is no longer available in testing.... will have to wait for now.

Yes. Earlier I though of systemd update as the main issue on this, but maybe there is a workaround, or just it is not possible? My apparmor knowledge is scarce to say the least.

The Template is like this: Makefile: BASEDIR:=$(shell dab basedir) .DEFAULT_GOAL := all .PHONY: all all: info/init_ok global finalize finalize: echo "10.0 " > ${BASEDIR}/etc/debian_version dab finalize info/init_ok: dab.conf dab init touch $@ dab bootstrap --minimal...

Hi oguz, Yes: arch: amd64 cores: 2 hostname: host10.mydomain.com memory: 2048 net0: name=eth0,bridge=vmbr0,gw=192.0.2.1,gw6=2001:db8::,hwaddr=0A:C6:94:AB:B3:7A,ip=192.0.2.10/24,ip6=2001:db8:ffff::3/56,tag=10,type=veth ostype: debian rootfs: local-lvm:vm-9002-disk-0,quota=1,size=30G swap: 0

I reported the bug to Debian and with the new version of quota package, solved these issues.

Hi everyone, Just dropping a question i cant find around the forum. I managed to create an image using dab but since some days ago, im unable to install/start any service on the container. Im constantly getting apparmor errors like this one when installing mariadb: [510907.402767] audit...

This happens to me also with a image of debian buster. root@test-lxc ~ # quotacheck -cmug / quotacheck: error (1) while opening /dev/mapper/pve-vm--9002--disk--0 Downgrading to quota from debian stretch (Debian 9): root@test-lxc ~ # dpkg -i quota_4.03-2+deb9u1_amd64.deb dpkg: warning...

Incredibly, i opened this bug almost 3 years ago, but today with latest pve no-suscription happens again :p but this time with proxmox 4.3 @dietmar any ideas ? Booting from Hard Disk... Boot failed: not a bootable disk Booting from ROM... iPXE (PCI 00:12.0) starting execution... pveversion...

Nice, The fix is working, at least with VirtIO Network card configured. Nice job, a thanks a lot.

Hi everyone, I updated one of my servers to pvetest (To test precisely) new package versions. Now i create VMs (KVM) but PXE no longer works. When the machine is turned on, i get the following: Booting from Hard Disk... Boot failed: not a bootable disk Booting from ROM... iPXE (PCI 00:12.0)...

Ok. Im offering my help and time to upgrade the package and to make some changes to integrate new features. Its possible for them if they are clear and ok to accept them. I mean i dont want to work a lot on this to get it discarded.

This was understood the first time. Is there a specific reason for this ? I mean is because it has specific set of patches ? or it breaks proxmox integration in someway ?, it doesnt compile on wheezy due to missing dependencies ? Also if its a need for time to merge it and test it, im offering...