Recent content by jebbam

I have seen this in Debian bullseye, bookworm, trixie, and sid. It has been around for a lot of different kernel versions.

Ya, Proxmox doesn't have it there. In the Proxmox GUI, there is a setting, but it won't start if you set memory= over 128. So I have had it maxed at 128 on all the machines, all along, but that still gets the error. There is config settings per machine in...

Which XML file? I wasn't able to find one that had that setting. I do have this set: "vga: qxl,memory=128" Thanks!

Have you found a way to disable the "Display output is not active" that comes on after a few minutes? I haven't poked at it to see why it is coming up. It isn't the worst, but it is kind of annoying. Not as bad as crashing! :)

@ramius1984 The VirtIO-GPU workaround hasn't crashed, which is a big plus. One big drawback is it is very blocky when playing videos. I tried the various SPICE Enhancements Video Streaming options, but it didn't help. I do this on a few VMs, so it won't work for those. One minor...

Thanks! I'll give this a test run on some VMs for the next week or so. -Jeff

This is killing me. It's happening a bunch of times today. $5,000.00 USD bounty reward from me for whoever delivers a working fix for this. Payable via PayPal or credit card, if you accept credit cards. Sincerely, -Jeff Moe Loveland, Colorado, USA

Here's a crufty scriptlet to automatically generate these files. It outputs them to /tmp, then you can copy to /etc/systemd/network if they look correct. I tested it on a few different systems, running Debian and Proxmox and it worked fine. #!/bin/bash OUTDIR=/tmp for ETH in `ls -1...

It just happened today to me. This is what I thought the first time it happened. "Oh, I'll just adapt to the new way, guess I just gotta learn!" Then they changed again. And again. And again. This morning, upgrading from Proxmox 8.1 to Proxmox 8.2... Not even a major upgrade. The difference...

Once upon a time Linux network interface names followed the unpredictable pattern: eth0, eth1, eth2, eth3, eth4, eth5. With the advent of the miraculous systemd and "Predictable Network Interface Names" they have a variety of names. On one cluster I have, with six+ interfaces on each node, the...

Yes, I see it most often with Firefox too, especially when creating a new window or switching windows. It also seems to happen more when I'm "going fast", bouncing between windows, etc. I just had it happen with Thunderbird when creating a new task (which creates a new window). In the past, I...

I have seen a similar error occassionally for years... My setup and how I see it: The KVMs are running X with the qxl driver: "SPICE (qxl, memory=128)" is selected under the "Hardware" tab. I'll also note that the max "memory=" I can get it to boot with is 128. Anything larger than that and it...

For the KVMs on the down node, I was able to get them working. You can just go in to "HA" (high availability) and add the KVMs from the down node, and it just migrates them. It doesn't need to be set up when the node is functioning. So I'm able to recover the nodes, thankfully! Later: I wasn't...

Hi, I have three similar proxmox clusters, ~10 nodes running Ceph with encrypted root partitions. I enable remote ssh for unlocking the encrypted root drives when it boots. This has worked swell for years. This morning, one of the nodes had rebooted and was waiting for the password to decrypt...

From what I can see, Proxmox isn't going to work until you get your upgrade/packages fixed. And it may be that the packages can't get fixed until your disks get fixed. I do note your multipathd.service has been running for 1 year 1 month. I'm not familiar with your iscsi setup, but it may be...