Search results

Thanks! I will definitely test.

I found out the problem... if you install the OS with UEFI mode, no virtio drivers are accepted on 2016... for some unknown reason.

Hi, As the title states, I tried installing virtio drivers from versions virtio-win-0.1.137 to virtio-win-0.1.185, each time on fresh install. They all report the same thing, "windows cannot verify digital signature"... Which leads me to believe that the virtio drivers were signed with a newer...

Hayia.... I never thought of adding this permission because I trust and follow the documentation. Once again I was wrong to do so. Next time when I see someone adding links and insisting on docs I will get frustrated.... Thanks for the solution.

I use the correct permissions as specified here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/storage/{storage}/content Pretty sure I know what I'm doing...

Hi, why would I create another separate thread for the same issue? I won't even mention the fact that most of them are not replied to. Nevertheless, to answer your question: proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4) pve-kernel-5.15...

I'm having the same issue, no errors in syslog however. Data returned is: { "data": [] } PVE 7.3-4.

Because using a single VM with pfSense for many VM's is not ideal, it cannot handle that much PPS when under attack. If it was a separate dedicated server only for pfSense, sure.

Well, considering nobody gave a crap to even try and reply... I will leave my answer here. Looking at https://github.com/proxmox/pve-firewall/blob/master/src/pvefw-logger.c and following the log format will indeed put your custom logs into the VM firewall log.

Just an update, I managed to do exactly what I needed. It is possible to add rules per guest and do whatever you need to do ;)

Update: It seems that you can manually add notes over the UI limit just fine into the vm.conf file. Not sure why the UI limits this.

I have a new thread opened about this, it seems the character limit is 8192 at the moment via the UI.

Hello, I'm trying to leverage Notes to fit my needs, however I'm unable to save a small JSON snippet; I get the following message via UI: The maximum length for this field is 8192 Is there a workaround? Many thanks

Bump - nobody have any clue about this? :confused:

Ah I see... so no then. Each VM has only one disk. So this won't make a difference then.

2 disks in soft raid, does this still apply?

So in essence, what you are saying is that it's better to use scsi single with IO thread?

Thanks, very helpful. Would be nice if the API viewer would be more detailed. I noticed quite some inconsistencies between PVEH and the HTTP API. What's the purpose to show only last 10 seconds of data? Can it be changed or something? If it was last 30 minutes or hour, it would make some sense...

Thanks, however as I mentioned extra CPU usage has been noticed on the host. Also, is this still necessary when you have NVMe SSD? I/O should not be an issue, so I suppose IO Thread is not really required?

Hi, Why is the default SCSI controller for Windows VM's single now? I have a previous Proxmox (below 7.3) and the default controller is just SCSI and not single. Any specific reason for this? From my testing they have the same performance, and on top of this the single controller with IO...