Search results

I am seeing same issues with latest firefox browser on Ubuntu 20.04. What I have noticed is that if I open a spice against one of the guests then this sometimes gets novnc working (around 50% of the time). But often only solution seems to be to reboot proxmox. I have done the following too...

Hi - Just an update that since turning on write back cache this has been running without crashing. However I only did this against a single VM which used lots of IO, but I did not apply the same to another VM which does not do much io. All fine. My spec if this is helpful is (and I built this...

I think there is an issue with virtio and amd cpus. I too was facing loads of crashes. After lots of testing, got it working fine in 7 by changing disk from no cache to write back and and take ballooning off. See...

Great news. I too have been pushing it and no issues seen yet. @t.lamprecht (proxmox staff), is this something that can be looked at, to get fixed?

Read up on cgroups. Set one up and configure memory as required.

lxc.cgroup.memory.limit_in_bytes

Do you want to try changing disk from no cache to write back and and take ballooning off if used to see if that makes a difference. I am currently doing this and so far seems to be working great. Previously was crashing very quickly.

I agree this seems to be related also to io and I now think there may be an issue with virtio. I have changed disk from no cache to write back and and taken ballooning off, and I am now pushing the VM with huge reads/writes and touch wood it seems stable. Do you want to try the write back to...

I have switched off ballooning and much better. This is with extensive disk reads and writes.

I too am not using ZFS, but LVM. I have one large VM, allocated 14500gb (14tb) to do some chia mining. VM has 16g mem. If I plot using default 4gb ram then works fine for a long time, but if I run it with 8gb mem, then it crashes very quickly, often within minutes. So seems related to...

What I have noticed is that I allocated say 16gb mem to a container in Proxmox settings. Within the container I run ubuntu server 20.04. If I only use 4gb internally in the container then it runs fine. However the moment I push an internal job to use 8gb (still only 50%) of the allocation...

Update: I deleted the VMs that had been created on the original 6.4, and recreated them again in 7.0, but still same problem - a crash - more than once per day. I tried various combinations, such as only running a select few VMs, but the moment a VM had any extra requirement for memory it...

Just an update: I changed the CPU type to "host" for the VMs. VMs seemed to run fine. Only container running was my pihole (container 201). I did not start the 105 Container (which is large 8 Tb). No crashes overnight. At 11:30 today I then started the 105 container - this is running...

Hi Thomas, I am unsure on easiest way to provide this info so hope this okay. I had built this box using the proxmox-ve_6.4-1.iso and done standard updates (apt update/upgrade). Nothing more. For upgrade just changed apt sources file and did apt-update/dist-upgrade. I did do pve6to7 --full...

I deleted the MAC address for the VMs and Containters in the Proxmox GUI which then reset them to auto. After logging back in they worked fine, without needing to hard-code the MAC in the network file.

Just got a 2nd kernel panic on Proxmox 7. After running for around 4 hours. SHIFT+PG_UP not working. Completely frozen. Was working fine in 6.4.

I had same issue with Ryzen 5 5600X last night. Kernel Panic. Board is Asrock B550 Tachi, 64g mem. Also have separate 4 NIC Intel 350 nic PCI, but otherwise standard setup. Was working great on 6.4.

Ubuntu-20.04 server Container allocated 16g memory, and I have a single job running in the container which I have only allowed 8g max memory. Chia Farming. Using htop in the Ubuntu OS shows 3.2g being used. What I would expect. BUT Proxmox 7 summary of the Container is showing 100% mem usage...