weehooey-bh's latest activity
-
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.
-
weehooey-bh replied to the thread Request for Best Practices and Guidance on Adding New Disks/OSDs to Our Ceph Cluster.The general guidelines apply to adding new disks to Ceph. As you add disks, keep these in mind. Ideally, all hosts and all disks (in a pool) will be the same. For hosts, this means similar CPU, RAM and networking. For disks, this will mean size...
-
weehooey-bh replied to the thread feat req: add "global blacklist" button in Quarantine.Hi @niziak You can file a feature request at Proxmox's Bugzilla: https://bugzilla.proxmox.com/enter_bug.cgi
-
weehooey-bh reacted to t.lamprecht's post in the thread The Reasons for poor performance of Windows when the CPU type is host with Like.
Please note that Proxmox VE already defaults to the x86-64-v2-AES for any VM created through the web UI's "Create VM" wizard since Proxmox VE 8.0 released two years ago. Exposing the relevant flags for nested virtualization in the UI might be...
-
weehooey-bh replied to the thread Loggen out of Web-Interface.You need to provide more information for someone to be able to help you. Please provide: The subnet you would like to access your web GUI via. For example 192.168.1.0/24 The IP address that you would like your PVE host to have. For example...
-
weehooey-bh replied to the thread Intermittent/broken networking.Thank you for sharing the guest configurations. I do not see any issues with the configurations. Do you have a DHCP server on your 192.168.1.0/24 network? If you do, what is the range? The ping behaviour you describe could be duplicate IP...
-
weehooey-bh replied to the thread SMTP Notifications.Because you successfully sent the first email, your configuration in PVE is likely correct. This means the issue is not in PVE. You might get more information from /var/log/mail.log You should also examine the logs on the Exchange Server. It...
-
weehooey-bh replied to the thread Firewall not working.What is the output from pve-firewall status ? Please provide the output from (replace XXXX with the VMID): cat /etc/pve/qemu-server/XXXX.conf And your interfaces file: cat /etc/network/interfaces
-
weehooey-bh replied to the thread VLAN Issue with 1 VM.Please provide: The interfaces file contents for each host A configuration of a guest that works as expected that is on the same host as a guest whose networking does not work as expected. The configuration of the guest that does not work. cat...
-
weehooey-bh replied to the thread Intermittent/broken networking.Please post your guests' configurations (replace XXXX with the VMID). cat /etc/pve/qemu-server/XXXX.conf
-
This suggests you might have a bottleneck somewhere else, e.g. with your CPU or some other hardware.
-
weehooey-bh reacted to luckman212's post in the thread Supported parameters in subnets.cfg? with Like.
@floh8 I found a very similar request already, so I added this suggestion to it: https://bugzilla.proxmox.com/show_bug.cgi?id=6014#c1
-
Open an enhancement in bugzilla. Proxmox. Com!
-
weehooey-bh replied to the thread ZFS replication DB consistency.Hi @TSAN I was looking for something related to ZFS replication and VSS when I came across your post. Just in case you have not found the answer to your question... Yes, ZFS replication triggers a freeze-thaw with VSS if you have the QEMU...
-
weehooey-bh reacted to shanreich's post in the thread vnet - "isolate ports" does not work cluster-wide with Like.
Bridge port isolation uses the feature of the native Linux bridge for isolating ports. That means it only works locally on that node, but not for VNets that are defined on multiple nodes (e.g. VLAN zone). There's also no way of only allowing...
-
weehooey-bh replied to the thread Backup not possible.@brnogu a few questions: Is VM1 (VMID 105) that is failing to backup to /mnt/pve/NAS on the same node as the other VM that successfully backed up to that share? If they are on the same PVE node, please provide the following: pvesm status cat...
-
weehooey-bh reacted to LnxBil's post in the thread Feature request: an option to restart the system without starting containers and VMs with Like.
What situation would that be? Nevertheless, have a look at this.
-
weehooey-bh reacted to DurzoBlint123's post in the thread How to delete a drive that failed with Like.
Wow, that was so simple it was stupid (of me). Thank you very much for your help!