Recent content by codejp3

I hate working blind, so I edited the config.plist to enable verbose debugging for Sonoma. Here's a screenshot of the debug messages: Here's a brief listing of errors/exceptions that may be the cause of the boot-loop: ACPI Error: Namespace lookup failure, AE_NOT_FOUND ACPI Exception...

I'm running into roadblocks with Ventura/Sonoma as well. Monterey works fine. I can install Ventrua/Sonoma from scratch, or upgrade Monterey, and the process completes. But first boot-up fails and it gets stuck in a boot loop with a generic "Your computer was restarted due to an error."...

I get this for pvecm: pvecm[1377]: got inotify poll request in wrong process - disabling inotify # journalctl -u pveproxy -u pvedaemon|wc -l 17378 # pveversion pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.5.13-3-pve)

Found a relevant link: https://www.suse.com/support/kb/doc/?id=000018235 ...and confirmed that this server suffers from the firmware issue: # lspci -nn | grep -qE '8086:(340[36].*rev 13|3405.*rev (12|13|22))' && echo "Interrupt remapping is broken" Interrupt remapping is broken I think this...

Possible culprit.... the dmesg dump above is misleading because it only shows the first line of DMAR-IR. Gave the impression that IR was enabled without any issues: [ 0.980710] DMAR-IR: This system BIOS has enabled interrupt remapping The full message shows a possible problem: # dmesg |...

I know this not a Proxmox issue and beyond the scope of Proxmox support, but I'm hoping to get some advice on this. I setup a Win11 QEMU VM and installed some music recording software. I have a direct-input box I use to plug microphones and instruments into to capture high quality audio. It is...

Primary English user here, but pinging this existing topic for this issue. My question: What's the best way to apply this patch before it's officially available? Reason/details: I just experienced the same thing. Backup created in PVE GUI 8.1.3, rsync'd to a different node, and then tried to...

Confirming the udev rules fixed this issue for me on a workstation. Only addition I'll add is the correct path/file: /etc/udev/rules.d/90-fixdm.rules NOT /etc/udev/rulesd/90-fixdm.rules

Checking back in a few years later.... WE GOT NOTES FOR BACKUPS!!!! :D:D:D Thanks Proxmox Team!

I ran across this as well. In my case, the udisks2 service was being used by Docker, Cockpit, and for mounting a USB external drive for manual backups. udisks2 was consuming an average of 30-40% of my CPU at idle! For now, I disabled Docker, Cockpit, and Udisks2, and my idle CPU is back down...

I'm getting a consistent error when manually unmounting .raw lxc disks. I have several containers that I wanted to setup mount points within them for users /home directories and other "core" directories, so to do it without borking a live system, I had to shutdown the containers, manually...

I figured it out. Turns out that specifying the correct directory makes a difference :rolleyes: I had to change /mnt/storage & /mnt/pvestorage to /mnt/storage/vzdump & /mnt/pvestorage/vzdump, which is where all of my files were actually located. Dumb mistake, but I'm leaving this thread here...

Title says it. I was running PMX 6.2.4 just fine, but had a HDD issue on the OS HDD. Replaced with a new one and a fresh install of PMX 6.2.4. I set all of my data drives back up. They show active, and the proper used/free space info, but zero files show up in the GUI. Files are there and...

It appears as though en01 is the only active plugged in and configured interface. It looks to be tied to vmbr0 with the IP of 10.0.0.23 with a class-c subnet (/24, 10.0.0.1-10.0.0.255) Assuming the PVE host has internet connection and is working fine, the network settings for the MineOS Guest...

Well, I guess I'll help get the ball rolling. Everything you need to know is probably already here: https://pve.proxmox.com/wiki/Network_Configuration In order to help you out, folks are going to need to know more info about your setup. In the PVE Host, do these commands and post the results...