Search results

zpool import -f 14313209163207667065

Try import by id

Good afternoon, community, It seems to me that vm-uptime was not reset to zero in previous versions of proxmox during online migration, or is it my personal memory fault? In any case, there is a discrepancy between the uptime displayed in the VM Summary page and the actual value of this...

Hi, Thomas. Ok, is there any possibility to use the "pure serial console" installation today without waiting for the next release?

May be chown -R www-data:www-data /var/log/pveproxy I've seen it before.

Hello, community. Exerpt from https://wiki.debian.org/SAN/iSCSI <quote> There is no way to do this with the standard Debian initrd. The init4boot project supplies the needed infrastructure (especially an adapted initrd). Standard PXE / tftp boot with iSCSI root and XEN guest systems with iSCSI...

+1 too.

Hi, you can try to find logs here: /var/log/lxc/CTNUM.log regards, dale.

After some googling i found: http://timjrobinson.com/docker-lxc-set-memory-limit-invalid-argument/ so in my case echo $((1024*1024*1024*16)) > /sys/fs/cgroup/memory///lxc/120/memory.memsw.limit_in_bytes echo $((1024*1024*1024*10)) > /sys/fs/cgroup/memory///lxc/120/memory.limit_in_bytes...

In my case :( ~# free -h total used free shared buff/cache available Mem: 125Gi 43Gi 67Gi 121Mi 15Gi 81Gi Swap: 19Gi 10Mi 19Gi ~# cat /sys/fs/cgroup/memory///lxc/120/memory.limit_in_bytes...

Hello, this is running containers only related (VMs - OK), webui result - the same. ~# pct set 120 --memory 10240 400 Parameter verification failed. memory: unable to hotplug memory: closing file '/sys/fs/cgroup/memory///lxc/120/memory.limit_in_bytes' failed - Invalid argument pct set <vmid>...

Feature req. added 2019-09-12 https://bugzilla.proxmox.com/show_bug.cgi?id=2373 :(

Installed pve-kernel-5.3.7-1-pve - Ok.

Can confirm that this is "hardware dependent" problem. Another system with Intel(R) Xeon(R) Gold 6144 CPU @ 3.50GHz - Ok.

VM reboot in earliest stage with message: Physical KASLR disabled: no suitable memory region! hardware info attached root@b12:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.0.21-4-pve root=UUID=e48d586c-8f58-4b03-a081-cdcf4776c83c ro console=tty0 console=ttyS0,115200n8 nopti nospectre_v2...

:( nothing. Quick reboot after loading kernel and jumping to it.

After upgrade to latest pvetesting repo Linux VMs constantly reboot in cause using 5.0.21-4-pve kernel [Windos & CTs - OK]. Linux/x86 5.0.21-3-pve - OK. root@b11:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.21-3-pve) pve-manager: 6.0-11 (running version: 6.0-11/2140ef37)...

Really? root@b02:~# ls -la /var/lib/vz/images/101/ total 9960 drwxr----- 2 root root 4096 Aug 30 12:35 . drwxr-xr-x 5 root root 4096 Sep 11 15:28 .. -rw-r----- 1 root root 536870912 Sep 11 15:35 vm-101-disk-0.raw root@b02:~# mount -o loop,noatime...

dir: local path /var/lib/vz content rootdir,iso,snippets,images,vztmpl maxfiles 0 zfspool: z0 pool zp00l content rootdir,images sparse 1

lxc.arch = amd64 lxc.include = /usr/share/lxc/config/alpine.common.conf lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 lxc.monitor.unshare = 1 lxc.tty.max = 2 lxc.environment = TERM=linux lxc.uts.name = a1 lxc.cgroup.memory.limit_in_bytes = 536870912...