Search results

I could be a combination of chipset + nvidia (nouveau driver) but this is 99,9% fix it.

@tom @martin maybe you should make a sticky about this?? I have seen so many people with nvidia GPU's have this problem now.

https://forum.proxmox.com/threads/pve-5-0-locks-not-responding.35930/#post-176096 the problem is the nvidia GPU.

Do you use the non-subscription repo? Seems like an old kernel, and if you never updated, then it makes sense.

I think it makes sense that Proxmox uses som ram for what all it does. It is really not intended for small devices, but for servers with enough ram. I have 64 GB RAM is my server, so I don't really care if Proxmox uses 1,2 or 2.5 GB ram.. I would rather have it use some ram and have a lot of...

You are very welcome :) Don't feel bad, debugging this was a bitch for me as well. I ended up in a forum thread with someone recommending to install nvidia-driver (which is bad! will pull a bunch for X11 depencies) and figured it would try this. Mostly it was 50% luck on my part :P

I don't think my comment is useless :P I know there was a new .iso, that does not mean that packages that are not already in regular pve-no-subscription repo are included in the .iso, they build the .iso with stable packages.. Also, a new feature/version is not a "fix" .. a fix is if something...

There is nothing to "fix" .. If you have not gotten 0.7.0 in regular pve-test or pve-no-subscription, then it's not in the .iso. just wait!

I don't think you can increase the size of a .raw, you should have use qcow2 I think? Also after you increase the size, you want to increase the partition inside your debian vm (is probably easier if using LVM) - Google how to do this. Here is a starting point...

Vendor does not matter, the nouveau driver is the problem. Just blacklist it and problem gone. Now we can go back to not blaming Ryzen and AMD :)

You are running a Nvidia card.. Did you read what I wrote to OP? Anyway, that is your problem :) See: https://forum.proxmox.com/threads/pve-5-0-locks-not-responding.35930/#post-176107

Do you know how the commands would be different if using AMD CPU? just kmv_amd or ?

Hi I'm a poor-ish student, and I would actually love to pay for the smallest subscription, since I want to support your work! But to pay for 1 year is advance is.. bad Why not accept payment for smaller time frames? I can understand corporations just paying for 3 years with 6 cores in advance...

You can't run virtual machines inside virtual machines.. Since your ESXi virtual machines does not have Intel VT etc.

I get it, it sucks.. But you are using a function Nvidia does not want you to use, which mean you will get problems in the future as well.. maybe you solve this, but until next time they do something and you have to start over.. That said.. Look at unraid forums for nvidia-solutions..

The segfault issue is related to what Rhinox wrote. It's a same thing. It will ONLY happen on some early ryzen chips when compiling on all 16 cores etc... Do you compile your own kernel/packages on Proxmox? If not, don't worry about it! First of, I seem to remember you having an asus board? I...

Wait for VEGA. I have setup 2 VDI machines for work, they both use 3 x AMD cards.. If NVIDIA don't want me to use passthrough fine.. I'm just giving AMD my money then.

I really don't think that is was OP is experiencing. That bug will (as far as I can see) only occur when compiling etc.

For what it's worth, it works perfecly on my Ryzen 7 1700 (OC to 3.5) with Proxmox 5.0 I think something else is at play here, maybe it depends on the motherboard (mine is AsRock)

Just purchased it today after recent features added. It does cost alot, but I can sort of understand, since the market is limited for such an app, and you need money for your time... Good thing I got those google survey money ;)