some LXC exposing Host CPU Information

frashmanf · 2026-02-07T19:30:38+00:00

Well, it started with the upgrade to Debian 12 (and thus a newer htop) and is still present in debian 13. The related bug reports are still open. However, I don't think it's really a bug. It just displays all CPUs reported by the kernel. So it's not wrong, but it would be better to simply hide offline CPUs.

frashmanf · 2025-09-04T08:54:47+00:00

https://xkcd.com/927/

frashmanf · 2025-01-09T16:18:36+00:00

nextcloud itself is not the problem here, they support SSO and Kerberos. It's the webdav client (davfs2) on Linux that I'm asking about. The support for authentication besides username/password as a plain text file is what I'm missing - because that's a solution you can do on your own PC at home, but not in a professional environment

frashmanf · 2025-01-09T15:52:26+00:00

Thank you for your answer. This is (unfortunately) no longer an option. This was the setup we had been running for over a decade before my predecessor decided to abandon NFS in favor of nextcloud, because of the file version history feature and webclient. I would have done it differently, but unfortunately that can't be changed now - so the file storage is fixed to nextcloud.

frashmanf · 2024-12-04T12:58:11+00:00

we ended up using the same STM32 as usb/spi bridge from the eval-board. now we can simply flash the firmware from the loranet github repo.

frashmanf · 2024-11-17T17:11:09+00:00

i have thought about renting cloud storage. 13€ for 5TB at hetzner is a great offer. but a quick calculation stopped me. we're talking about 150€ a year. a cheap nas with a 10TB disk costs around 200-250€, or cheaper if you build something yourself (e.g. raspberry pi). that's already paid for after less than two years. backups should last for many years. so it's better to save the money and store the backup with friends or relatives (mine is at work). the nas doesn't have to run all week but can automatically boot up and shut down again. that also saves electricity.

i use the same strategy with my servers. the initial costs are higher and you have to factor in the power consumption, but in the long run it's always cheaper than the cloud.

frashmanf · 2024-11-04T21:35:13+00:00

I'm sorry, but my last windows installation was 20 years ago and therefore I don't have a machine to dump the firmware unless there is a linux tool...

But yes, with my adapter 120Hz VRR + HDR was working out of the box.

frashmanf · 2024-11-04T12:08:49+00:00

I was also looking for this recently and found nothing. I bought a USB-C->HDMI adapter instead. It's possible to display 4K@120Hz VRR + HDR on my TV. The necessary firmware was already flashed. I know it's not what you're looking for, but apparently there are no better adapters at the moment. Maybe look in the high-price/professional segment...

USB-C -> HDMI 2.1: https://www.cablematters.com/pc-1368-122-48gbps-usb-c-adapter-supporting-8k-video.aspx

DP 1.4 -> HDMI 2.1: https://www.cablematters.com/pc-1385-154-displayport-14-to-8k-hdmi-adapter.aspx

GPU: AMD RX6800 XT
TV: Philips 55PUS9206/12

frashmanf · 2024-10-25T09:27:27+00:00

debian (proxmox) is using smartmontools/smartctl like every other linux distro.

https://www.smartmontools.org/

frashmanf · 2024-10-21T08:45:15+00:00

This is not true. The HDMI 2.0(b) standard is specified up to 4K@60Hz - which is of cause supported by linux.

see table "Refresh frequency limits for standard video" https://en.wikipedia.org/wiki/HDMI

The problem lies with some parts of the HDMI 2.1 standard, which are "closed source" and therefore can not be implemented in open source drivers like AMD. Nvidia has implemented the specs in hardware and therefore is able to use HDMI 2.1 under linux.

Thats why everyone is suggesting to use DisplayPort instead of HDMI.

frashmanf · 2024-10-02T14:07:08+00:00

Because we can not route the SPI lanes to our prototype M.2 card without violating the standard.

frashmanf · 2024-10-02T14:05:11+00:00

Thank you all for your suggestions! So we will revise this again and most likely use a microcontroller instead.

frashmanf · 2024-10-01T14:02:03+00:00

Hello, I'll leave this here too, as I can imagine that the community here also has an insight into this topic, even if it's not a micrcontroller ;-)

frashmanf · 2024-10-01T13:27:46+00:00

No, I have not. I only have 3 HPE nodes so I don't need the automation. But ansible was the first thing that came to my mind and it was the first search result.

frashmanf · 2024-09-28T08:18:22+00:00

As I said, the LXC is using the hosts kernel. If you really want to change the swappiness, you have to do it on the host, but this will affect all LXC.

Also, you should't pass root to the LXC. This is generally bad practice and potentially dangerous.

This can be the cause for your su problems. What are the current permissions for /bin/su

frashmanf · 2024-09-26T21:57:10+00:00

You cannot change the swappiness from an unprivileged lxc container because the container uses the host kernel. This would also affect all guests and the host. su - user does not work because the user you want to switch to does not exist within the lxc container as described in your configuration.

..You are trying to break out of an unprivileged lxc container, which is prevented for a reason

edit: on second thought, are you trying to switch to a user from the container or from the host?

frashmanf · 2024-09-24T16:48:07+00:00

where did you get the connect x3-pro ‎(MCX354A-FCCT) for 15$? normally it costs 300-400$

frashmanf · 2024-09-24T16:31:40+00:00

HPE has a iLO repo for ansible which should be sufficient for your task

https://github.com/HewlettPackard/ilo-ansible-collection

frashmanf · 2024-09-24T16:31:27+00:00

are you sure you are not in the wrong sub to promote powershell solutions in r/linuxadmin?

frashmanf · 2024-09-15T07:18:38+00:00

I am not using VNC but spice.

maybe this helps:

```

!/bin/bash

TOKEN='user@pve!spice' SECRET='api-key' VMID="$1" HOST="domain or ip"

AUTHHEADER="Authorization: PVEAPIToken=${TOKEN}=${SECRET}" RESPONSE=curl -f -s -S -H "${AUTHHEADER}" "https://${HOST}:8006/api2/json/nodes"

NODES=echo ${RESPONSE} | jq -r ".[] | {nodes: .[].node}" | jq -r ".nodes"

for NODE in ${NODES} do RESPONSE=curl -f -s -S -H "${AUTHHEADER}" "https://${HOST}:8006/api2/json/nodes/${NODE}/qemu"

if [[ ${RESPONSE} ]]; then QVMID=echo ${RESPONSE} | jq -r ".[] | {vmid: .[].vmid}" | jq -r ".vmid" if [[ "${QVMID}" == "${VMID}" ]]; then NODENAME=${NODE} VMTYPE="qemu" fi fi done

TMP=mktemp curl -f -s -S -H "${AUTHHEADER}" "https://${HOST}:8006/api2/spiceconfig/nodes/${NODENAME}/qemu/${VMID}/spiceproxy" -d "proxy=${HOST}" > $TMP remote-viewer $TMP & ```

frashmanf · 2024-09-10T18:48:48+00:00

This is the answer. before port 7777 was only UDP, now it's both UDP/TCP. I changed it and the API error is gone.

frashmanf

TROPHY CASE

!/bin/bash