Search results

I accidentally updated from 5.0 to 6.0 on 8.1.10 and wonder if it has any downfall. I have some legacy CentOS 6.10 pcts and from description of LXC 6.0, upstart support is removed. I am not sure how to interpret this change. I need to stick with 6.0 for some historical reasons on this box so...

Works in my case. Proxmox 8.1 lvchange -a y /dev/pve/vm-102-disk-0 lvreduce -r -L50G /dev/pve/vm-102-disk-0 lvchange -a n /dev/pve/vm-102-disk-0 pct start 102

Thank you. I downgraded and it worked using -l.

Fabian, I understand but, it didn't work for me. I had the latest pve version of lxcfs and had load average in container the same as host. Which version of yours have the patch?

Hello everyone, I am using Proxmox 6.1 with containers and I noticed that all containers are getting load average lick from a host. I checked lxcfs site and found this news from last year. https://discuss.linuxcontainers.org/t/lxcfs-3-1-2-has-been-released/5321 I installed the new lxcfs...

Are you using tuned with vm host or container host profile enabled?

I made a backup copy of the original Config.pm. After restarting pvedaemon and pveproxy newly created machine seems to work with MAC address added to the GUI and firewall works as well.

Added the patch in the Config.pm do you need to restart anything?

Thank you. Is it save to try the patch before the official package is available?

Any clue? How do you even debug this?

Maybe a clue Nov 6 03:40:43 virt3 pvedaemon[15570]: starting CT 104: UPID:virt3:00003CD2:00023167:5DC2870B:vzstart:104:root@pam: Nov 6 03:40:43 virt3 pvedaemon[5406]: <root@pam> starting task UPID:virt3:00003CD2:00023167:5DC2870B:vzstart:104:root@pam: Nov 6 03:40:43 virt3 systemd[1]...

No hardware address shown if I leave auto in the field.

arch: amd64 cores: 4 hostname: test3.teletownhall.us memory: 4096 net0: bridge=vmbr0,name=eth0,ip=10.10.10.11/24,gw=10.10.10.1,firewall=1 ostype: centos rootfs: volume1:vm-104-disk-0,size=80G swap: 4096

BTW, MAC Address is being generated, just is not being assigned to an interface in gui

When I create a new container I leave network interface set with auto mac. Recently container stopped displaying autogenerated mac in GUI. It shows empty space. The problem is that with firewall on interface enabled and no mac address displayed I loose connectivity. I can either disable the...

If anyone cares, I have no clue why I went through this ordeal. The only guess I have so far is the last time I had enabled both tests and no-subscription repositories. This time I didn't touch the test source at all. I updated to the latest no-sub and all Debian and rebooted several times...

Clean reinstall of PV 6 with non-subscription + Debian sources enabled. Two reboots no down negotiate so far, waiting and watching for any changes.

Ubuntu 18.0.4. wit kernel 5.0.23 has no problems either. So doesn't seem to be a generic kernel/driver issue here.

I attempted multiple proxmox kernels and behavior is the same. I even installed a native Debian kernel which is 4.19 vs proxmox 5.0. It is exactly the same behavior with all kernels it boots to 1000 Mbit and then ~38 seconds later port goes into a disabled mode and comes back as 100 Mbit. At...