Search results

I agree status of hardware is important information Temperature of hardware rates not far behind Ram usage and Disk usage in terms of node stability. Showing devices with failed SMART status is similar. Ideally this information would be shown together in the GUI summary page for each server...

Imo that would be a bad idea. I often have different VM which would use the same resource, but don't simultaneously as I do not run both VM at the same time. If your idea was implemented consistently a VM with pass through could not be copied. In summary showing resources currently in use is a...

The advantage of copy on write (CoW) is resilience to file system corruption on abrupt power loss. When a file is modified: a new updated copy is created then pointers updated and the old file storage added to the recycling pool. This approach ensures a file is never partly updated. The...

So keyboards don't use ascii coding, the key mapping is keyboard dependent. What a weird choice of standard. So noVNC would need a "Keyboard" setting to do the ascii to key code mapping reliably. Some browsers expose keyboard layout information but unfortunately not all. Interestingly the...

You confuse me. I also find the threads on this subject confusing as two completely different functions are mixed together. noVNC in Proxmox console already has buttons for Send tab Send escape Send ctrl-alt-delete I thought these worked in a VM without a guest agent. Essentially functioning...

Does that really need to be the case? When installing and maintaining a VM I often need to type command lines into the VM console. This procedure would be faster and less error prone with paste text from clipboard support. Some of the VMs are images from other suppliers and while installing...

A "Send clipboard text" button next to the Send Tab / Escape / Ctrl-Alt-Del buttons would be a very valuable enhancement

Clock frequency x Cores -> approximate relative performance Provided the cores are about the same, your software uses all the cores, and performance is processor limited (not Disk, ram or thermal limited). By the way When comparing performance for it to be relevant you actually need to be...

Not sure I would recommend a USB NIC. If you can't add more NIC cards I would use an external managed switch with VLANs to pfsense

Why not pass the graphics card through to a VM running Frigate?

As performance wise it is mostly a router I would Reserve 1 NIC for Proxmox and the other virtual machines Pass through the other NICs to pfsense so it can optimise network throughput and use hardware offloading where it helps

Start with Proxmox virtualisation in Netgate manual and Netgate virtualisation forum Configure two bridge in Proxmox to connect to pfsense WAN Lan Or use VLAN in pfsense to separate the WAN and LAN interfaces (router on a stick), and use VLAN controls in Proxmox to separate the interfaces

Added @tristank discovered option from the Select default Boot Kernel thread to OP

I suspect what you would like is this bugzilla feature to be implemented. Not sure if this Revert to prior Kernel thread helps

Some background information would help Is this a new install? Has it ever worked? Is this a single server running Proxmox or part of a cluster If it has worked in the past, what general tasks were you doing prior to it stopping working

What does these commands show cat /etc/network/interfaces ip a systemctl status networking.service Have you tried systemctl restart networking As that helped me Host network access lost after Proxmox upgrade 7.0 to 7.1

Sounds like a good idea to me. That way if either your test bed server or DIY router server go down, you can readily fire up a VM on the other, ensuring minimum down time You can re-use your understanding gained from experimenting with your main sever a relatively small server should be enough...

Pass through works by passing through an IO group (PCE Device at a particular address). To see what is in each IO group run the following in a Proxmox shell / command prompt for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"...

During Proxmox boot up it changes the screen resolution to what it thinks your screen supports. Perhaps this is going wrong. Can you try a different monitor?

You should edit the thread title to mark it "Solved"