Search results

I usually associate code 43 error with Nvidia not liking PCI passthrough on consumer GPUs. The fix for this being patched ROM. (Though I got the impression this is no longer needed- can anyone comment on this/prove me wrong? I'd love to know.) The last time I had an issue with GPU passthrough...

And if you implemented my workaround to manually set the kernel version in GRUB, you removed that too, correct?

Has this always been an issue, is this a new VM, or is this new since a Proxmox update? There are currently ongoing kernel issues in Proxmox for both PCI passthrough and USB (though I'm only aware of USB storage devices, but maybe it's all USB?). But let's pretend this isn't a kernel issue...

Hmm, I wonder if Windows does some kind of install specific to the machine it finds itself in...would make sense to me that it would. You might be stuck having to do a clean Windows install. Oh well, probably for the best since I assume at some point you'd probably like to attempt to passthrough...

@xcj Thanks for the follow-up, even if it didn't end up turning out like you wanted. Personally, I don't like working on an engine while the car is running.:D

It's never like this. You're just seeing an unfortunate series of events as you're onboarding. I've been using Proxmox for 2+ years without issue. Major VE changes might occasionally have an issue (I do seem to recall an issue with PCI passthrough back during one of the major or minor PVE 6.x...

"VMs are slow and laggy" - How? Accessed from where? From direct video output from the server? Accessed over SSH? Accessed over the console? Some general suggestions: - Change your machine to q35. i440 is ancient. - For CPU, use host, unless you have a specific reason.

That's a different error. Looks like you're trying to use the enterprise repo which is only available if you have a license. It's been a while, but here's how I remember fixing that: Use nano /etc/apt/sources.list.d/pve-enterprise.list and comment out the line there by adding a hashtag in...

You should be able to install an older kernel. This should work to install the last known working kernel (5.13.19-3-pve): apt update && apt install pve-kernel-5.13.19-3-pve Let me know how that works out for you.

If you're using ZFS, see @peteb comment (which it looks like you already have). If you're using the standard Proxmox install (not using ZFS), here's how to rollback a Proxmox kernel update with GRUB. It may or may not be easier to follow for someone new than @vale.maio2's post above. (Though I...

I also received these errors which disappeared after rolling back to 5.13.19-3. Question for you @depen, and I should probably split this off into a separate topic, were you actually able to reboot your Proxmox server after these errors? I was not. Telling the server to shutdown with reboot...

Thanks for the feedback, everyone. For those of you also running across issues with the 5.13.19-4 kernel update and you've never reverted a Linux kernel before, I've written up a quick guide: How To Rollbock a Proxmox Kernel Update in GRUB Note that this will not work if you're using ZFS, as I...

Same story here. Are you booting your VM off a USB device? That's my scenario; VM will no longer boot after most recent update. (Running 5.13.19-4-pve where it now fails; came from 5.13.19-3 where it worked.) Update: Reverting back to 5.13.19-3 for now which fixed the issue. USB device...

It's a problem many of us (maybe all of us?) ran into with Windows 10 guests and Nvidia GPUs. You need to boot into safe mode and enable MSI to fix it: Fixing GPU Passthrough On Windows 10 VM In Proxmox

That VM hasn't been spun up since Proxmox 6.1 and wasn't run since Disco Dingo (Ubuntu 19.04) was a thing, so that makes it at least a year old. When I booted it up, the GPU was nonfunctional (determined by running sudo nvidia-gmi), though I could at least see it with lspci. It was functional...

I take it back, the API shows some nice POST parameters that I hadn't noticed before: https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu Combined with your LXC wiki link demoing curl encoding the POST body: https://pve.proxmox.com/wiki/Proxmox_VE_API, he should be able...

He's creating a web application, I doubt he wants to abandon npm. Do you actually need to create the VM or do you just need to be able to start/stop it? If it's just being able to start/stop it, then the Proxmox API should be fine. One of the things that's always bothered me about Proxmox is...

I don't think it really matters, since ultimately cores*sockets (i.e. # of vCPUs) ends up as the number of threads on the host. Per the documentation: https://forum.proxmox.com/threads/cpu-sockets-vs-cores-socket.2299/post-12312 On a related note, if you really have two physical sockets on...

^This. I actually wrote an article a while back, LVM, Thin Provisioning, and Monitoring Storage Use: A Case Study, where I had managed to miss setting the discard option on all of my VMs and so I was really chewing through storage. You'll still need to run fstrim inside Linux VMs (or just...

That response was more toward Joris, since I think he is using an AMD GPU. I just spun up that Ubuntu VM from the grave. It was so old it was running 19.04 and I had to update Ubuntu to 19.10. Even though Ubuntu seemed to indicate it saw the GPU and had even updated the drivers, running sudo...