Not sure what you had in mind there. Maybe
* name & MACAddress match -> proceed without user intervention
* name or MACAddress match -> user confirmation required to update non matching item noting total requiring user confirmation
* neither name or MACAddress match but outstanding interface...
Ouch
That sound stressful. No doubt different decisions would be chosen for your 6TB data in hind sight. An off site disk is good to have going forwards.
Have you tried setting Sockets:1 and cores to your total core count for that VM.
If it achieves throughput and reliability goals, the reasons could be investigated later.
So why does the Proxmox update GUI not include them by default? Or is it planned to include relevant components after they have been tested in the Proxmox environment?
Interested in this also.
Similar application. Use custom built "all in one router" consisting of Proxmox, pfsense, 3cx, Unifi application. Similar at 2 sites. Have spare unit for lab & recovery from failure. Like to make more active use of the "spares" as HTPC. So need HDMI out from a VM on...
pfsense runs on FreeBSD just as Proxmox runs on Debain.
In both there is nothing stopping you adding upstream packages and user specific modifications.
pfsense has a GUI utility to backup the norml pfsense configuration, the extra user specific additions then must be separately handled by those...
Imo, ignore wear and just use the SSD. If it wears out then replace it.
7% per year means it will reach 100% in 14 years & I suspect you will throw it out before then.
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.