Search results

I can observe a high IO pressure stall percentage after switching to this kernel—consistently above 90%—but without any noticeable side effects.... all my servers seem to be affected

runs fine on AMD EPYC 9015 ASRockRack TURIND8UD-2T/X550 zfs mirror intel E810 nic ------------------------- AMD EPYC 3151 4-Core Processor GIGABYTE MJ11-EC1-OT zfs mirror ------------------------- Intel(R) Pentium(R) CPU D1508 @ 2.20GHz Supermicro X10SDV-2C-TLN2F zfs mirror Intel Corporation...

The mentioned 32Bit workaround did the job .... win xp is running now on qemu 9 ... sorry for not doing the homework :-)

I also have problems upgrading from 8.1.5-6 to latest 9.0.0-6 ... I have three Windows (Win10, Win XP,..) vm's which run into a BSOD bootloop when starting with qemu 9. Everything is fine after reverting to 8.1.5-6. root@minimaster ~ # qm config 101 agent: 0 balloon: 0 boot: order=ide0;net0...

"dpkg-reconfigure openssh-server" should do the job

shell is ok ... but do it in a screen session :-)

pve-manager version 8.0.9 fixed it for me !

same here ... network does not start properly ... 2xIntel I210 2xIntel E810-XXV asrock X570D4U both were unavailable after booting into 6.5.11-3

root@micromaster ~ # lspci -k | grep -A3 -i ethernet 26:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) Subsystem: ASRock Incorporation I210 Gigabit Network Connection Kernel driver in use: igb Kernel modules: igb 27:00.0 Ethernet...

same here ... had to boot with init=/bin/bash and remove the whole network config to be able to boot afterwards I copied the network config back and did a "systemctl restart networking" to bring all bonding/bridges online again ... not sure why it hangs at boot time ... is there any way to get...

hi, updated the configs .... now they start flawlessly :) thx for your quick help! herm

btw ... the vm is a more or less minimal debian bullseye

it seems the vm stucks somewhere at the boot process ... but as i have no display i can't see where ;-) but i swear it worked before upgrading with the enterprise repository :-) root@micromaster ~ # qm status 102 status: running root@micromaster ~ # qm config 102 agent...

Hi, after activating my new licence key, update the system with apt upgrade followed by a reboot no vm was able to boot anymore. after some research i found out that i have to configure their "Display" option to "Default" in order to be able to start them again. Before upgrading the system...

Yes, mee too