Search results

Update: Stable again with the old kernel (no blue screen during the night). Is there anything on my side I can do to track down the issue? another question: how can I modify grub to start 4.10? currently 4.13 is starting which isn't useful at the moment. I tried GRUB_DEFAULT=saved...

Did memory testing today, seems fine. SMART values from the harddisks OK -> I'm now trying the old kernel (Linux host04 4.10.17-3-pve #1 SMP PVE 4.10.17-23 (Tue, 19 Sep 2017 09:43:50 +0200) x86_64 GNU/Linux) again via advanced GRUB startup. Let's see if it is stable again

And there is a solution, thank you Proxmox team! https://forum.proxmox.com/threads/pve-5-1-kvm-broken-on-old-cpus.37666/#post-185463

HP DL380 G5 (really old ;-)) with 5.1 and new kernel -> working!! Thanks to the Proxmox team for this quick solution

maybe it is related to the CPU? my error msg Oct 25 11:48:52 host02 pvedaemon[3371]: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios...

one of my hosts is currently empty. I'll setup it from scratch and report back

I didn't find anything in the journalctl log, my dmesg is attached, I'm not really sure if there is a problem visible. Maybe you can take a look at it. If this doesn't help I'll revert back to the old kernel to see if the system is stable again

I did an inplace upgrade and my VMs are working fine right now. Did you do a fresh install or an upgrade?

I did apply updates regularly, I was on 4.10 before the upgrade. It was stable with 4.10. Is there probably a log file which helps to track down the issue?

Hi, I'm running a small lab at home (old PC hardware, no special server hardware). Until yesterday I used version 5.0, today I did an inplace upgrade to version 5.1. Since version 5.1 my server 2016 VMs are getting blue screens (server 2016 core and 2016 with GUI). With 5.0 everything ran...

Update: Proxmox VE 5.1 installed and now all is working again (with MPS Table Mode enabled) with the new Linux kernel... Thank you Proxmox Team for upgrading!

Update: I got my hand on a dedicated NIC (Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)). I use the virtio drivers and now copying files and streaming works. WOL is back to life too. So my issue was caused by the onboard NIC (maybe driver related).

Skaffen: Thank you for your input and you are right. I've two processors and now only one is working. I didn't noticed this because there are only low CPU performance VMs running. So this is an issue :-( I searched within BIOS options but it seems that there is no option for hyperthreading with...

I'm afraid currently not... but I used the onboard nic with esxi for the last year without a problem...

I would not call that a storage ;-), currently it's only a single old SATA disk (home lab), so the transfer rate is within expected parameters. It's an onboard NIC ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) Another downside I noticed moments ago...

I set up a new server 2016 installation and installed all virtio drivers (net, ballon, scsi, guest agent). Same outcome, video and audio stutters with different files, even simple connection with Media player, no KODI. PC is wired connected, no QoS rules. 1GB switch with hardly any other...

I'm playing around with proxmox in my lab. I migrated a Windows server 2016 from vmware to proxmox. During migration I removed all VMWare drivers and installed all virtual drivers from fedorapeople.org. Everything worked but then I noticed a strange behavior with the virtio network driver (tried...

Yeah it happens even after a complete power off and hard reboot. Replacing CMOS battery won't help, it happens with all 3 of my test lab servers. Changing grub won't help either because serial wasn't included in my config. But as I stated in post #4, everything is working with the altered...

I tried the kernel.watchdog line but it didn't work for me, still same error...

Update from my side: I found a solution but I'm not able to link to the Debian forum entry since I'm new here. Conclusio: BIOS -> MPS Table Mode -> Disabled (not the default value). Then PVE5 works without ACPI=OFF