BobhWasatch's latest activity

  • B
    BobhWasatch replied to the thread making mp's migratable (virtiofs on pve managed paths only).
    Not really. Traditional NFS trusts the client to provide correct information about things like the user ID (UID). One obvious attack @Johannes S slides point out is someone with root on their device creating an account with the same UID as...
  • B
    BobhWasatch replied to the thread How to make a linux Xorg based os recognize or use multiple screens without a graphic card?.
    You seem to be stuck on trying to set up an emulated display for X to use, presumably because the remote access software you've chosen basically does "screen scraping" on an existing desktop. It grabs the current screen and encodes it for remote...
  • B
    BobhWasatch replied to the thread lxc not really "protected" by oom.
    First, the restoration of stability after the OOM-kill kills something is very much not guaranteed. It is more of a hope. We are out of memory, maybe killing something will help. Often it works. Sometimes things just get worse. I don't know why...
  • B
    BobhWasatch replied to the thread lxc not really "protected" by oom.
    What does "frozen" mean? Can you log in to the container with SSH or pct enter? In any case, the behavior when something is killed by out of memory is not defined. It depends entirely on what kind of system is in the container, what the dead...
  • B
    BobhWasatch replied to the thread lxc not really "protected" by oom.
    There are theoretical efficiencies, yes. But if it doesn't work efficiency is zero, right? Do you have something to do with a little bit of extra memory? Do you restart the machine a lot? In other words, does this slight gain in efficiency...
  • B
    BobhWasatch replied to the thread lxc not really "protected" by oom.
    The OOM-killer is killing a PHP process in the container. You either running low on system memory or your container processes are exceeding the limit you set. Unlike a VM, the host does not view a container as a single process. It is a...
  • B
    BobhWasatch replied to the thread Unable to disable simple-framebuffer on the host.
    The only idea I have is to try the optional 6.11 kernel and see if that detects your GPU.
  • B
    BobhWasatch replied to the thread Unable to disable simple-framebuffer on the host.
    Some questions: I guess this is an N100/150? Perhaps you could provide more HW details? Have you tried just doing 'modprobe i915? Any errors? For comparison's sake, I have a Beelink N100 mini-pc. It has this GPU: 00:02.0 VGA compatible...
  • B
    BobhWasatch replied to the thread cfg80211: failed to load regulatory.db.
    It isn't needed and nothing is broken if you aren't using wifi. The kernel has a generic wifi layer that is separate from the card drivers and that's where the regulatory checks happen. If wifi is enabled in the kernel the generic layer gets...
  • B
    BobhWasatch replied to the thread how to enable a BE202NGW device.
    Besides firmware, wifi 7 is very, very, new. As in only a few months old. It could be that the iwlwifi driver in the PVE kernel doesn't support it yet. I have a Framework laptop and someone on their forum got a Qualcom card working with kernel...
  • B
    BobhWasatch replied to the thread how to enable a BE202NGW device.
    I was not able to log in to my PVE earlier. Now I can it it appears that the pve-firmware package is installed by default and conflicts with the Debian ones. I didn't realize that. In looking at your initial post, it looks like it is loading...
  • B
    BobhWasatch replied to the thread how to enable a BE202NGW device.
    I should also add that the recommendation from Proxmox is to not use wifi as your primary interface. The reason is that you generally can't bridge wifi. See the relevant chapter in the PVE manual, which is linked at the top right of the PVE main...
  • B
    BobhWasatch replied to the thread how to enable a BE202NGW device.
    Have you installed firmware-iwlwifi package? ETA: On the other hand, this card must be very new as it claims to be wifi 7. You might have to get the firmware from kernel.org or Intel. It almost certainly isn't in the Debian stable packages.
  • B
    BobhWasatch replied to the thread Proxmox and Eaton IPP (shutdown VM before server is shutdown).
    PVE should do that automatically if you just use the regular shutdown command.
  • B
    BobhWasatch replied to the thread Excessive amount of DNS queries to domainname of metric server.
    Not by default, no. There are DNS caching daemons you can install via apt if it really bothers you. Then you will find out the subtleties of that. It isn't as obvious as you clearly think. And the queries will still be made, they just won't go...
  • B
    BobhWasatch replied to the thread After reboot machine can't access to web interface.
    The problem is in your VMware configuration. I don't use VMware and so can't help you. Perhaps asking in a VMware forum "how to enable network access from the host to a VM" would be a way to get help.
  • B
    BobhWasatch replied to the thread Proxmox VE 8.3.1 Installation with no RTL8125 Drivers.
    Debian (and Ubuntu) have a thing called DKMS to semi-automate the process, including upgrades. Vendors need to support it though, it can't work with random vendor-provided scripts. Also, there are still occasional issues that you have with any...
  • B
    BobhWasatch replied to the thread Proxmox VE time issue.
    So DNS is working and routing is working. Which leaves a firewall somewhere that blocks UDP port 123 either inbound or outbound. ETA: Sometimes, especially on corporate networks, the firewall is set up to be an NTP server and blocks use of...
  • B
    BobhWasatch replied to the thread How to create RAID array with existing drive without losing existing data?.
    Make a backup and then restore it to the new array.
  • B
    BobhWasatch replied to the thread Proxmox UI keeps logging me out - time in sync.
    The next thing I'd try is to clear all site cookies and cache for the PVE host in your browser.
Show older items
Top Bottom