weehooey-bh's latest activity
-
Hi Thomas, Yes, done. -
We are pleased to announce the first beta release of Proxmox Virtual Environment 9.0! The 9.x family is based on the great Debian 13 "Trixie" and comes with a 6.14.8-1 kernel, QEMU 10.0.2, LXC 6.0.4, OpenZFS 2.3.3. Note: The current release of...
-
weehooey-bh reacted to spirit's post in the thread [TUTORIAL] Proxmox VE 7.2 Benchmark: aio native, io_uring, and iothreads with
Like.
Yes, I known this can increase latency. I need to look to add an option to pin iothread on specific cpu, like for the vm cpu cores. (ideally iothread have dedicated cores and vm cpus other cores, on same numa node than nvme drive)... -
weehooey-bh reacted to readyspace's post in the thread Proxmox server hardening document for compliance with Like.
Hi Everyone, I've created a basic compliance checklist, not specific to any benchmark at the moment. Hope this will help someone else here. Any feedback are welcomed. ReadySpace
-
weehooey-bh reacted to tom's post in the thread Mobile web and Android App: how to log in with Google Oauth2 OpenID? with Like.
Proxmox does not sell any licenses, all Proxmox products are open source and licensed under AGPLv3. (We sell support and services for these open source products).
-
weehooey-bh reacted to tom's post in the thread Mobile web and Android App: how to log in with Google Oauth2 OpenID? with Like.
Yes, welcome. But please do not write wrong facts, no one "sold" you a feature complete mobile app.
-
weehooey-bh reacted to Neobin's post in the thread Mobile web and Android App: how to log in with Google Oauth2 OpenID? with Like.
Please elaborate where exactly and for which Proxmox product(s) you/one has to pay.
-
weehooey-bh reacted to spirit's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
please test with pve8 && recent qemu, I remember than some iothreads crash has been fixed since. (and pve7 is EOL anyway)
-
weehooey-bh reacted to complexplaster27's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
Hey All, Here are some of my testings that I hope help. I have upgraded the drivers to v271 on one of my production servers (non critical) to do testing with, here's the verification of said drivers: I ran that same crystal disk benchmark...
-
weehooey-bh reacted to benyamin's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
Furthermore: viostor is for Proxmox VirtIO Block hard disk devices. vioscsi is for Proxmox Virtio SCSI and VirtIO SCSI single devices.