Search results

In that case I don't believe netplan consults /etc/network/interfaces. Configure it in /etc/netplan/*.yaml or turn netplan off and use traditional ifupdown. https://netplan.io/reference/#examples

The reported interface IP differs from that specified in your interface config. It could be Debian is using /etc/network/interfaces where Ubuntu 20+ is not. Network Manager or netplan maybe? If Network Manager is active, try enabling ifupdown in /etc/NetworkManager/NetworkManager.conf.

It's managed by systemd. ~# systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Thu 2022-03-24 09:00:00 GMT 32min left Thu 2022-03-24 08:00:22 GMT 27min ago pmg-hourly.timer...

I'm also curious what determines which cpu frequency driver is selected. I have a desktop (ubnuntu 20.04 skylake) and server (proxmox 7 ivy bridge). The desktop selects intel_pstate and the server uses intel_cpufreq. AIUI the ivy bridge system could safely use intel_pstate too. Desktop (Ubuntu...

Ah good. I've done something useful for a change!

Under a default setup, in the 'Dangerous Content' object, x-ms-dos-executable content filter seems to appear twice. Is this by design and if so what does it achieve?

Pleased to say this one seems resolved with updated package pve-kernel-5.13.19-4-pve (version 5.13.19-9).

I posted in a separate thread, thinking my issue was unrelated. However, it seems it may be. The kernel messages in the bug report, refereced in post 10, are somewhat similar to mine. Mine occurs when attempting to disconnect sata hotplug drives on the host. I'm not currently passing any...

Thanks. I'm using the GRUB_DEFAULT="1>2" option, as suggested by @Struppie in the above thread, for the time being. I wondered if my suggestion would work or just break things, being the pve-kernel-5.13 metapackage depends on the last kernel. I take it it's not advisable to uninstall the latest...

Thanks @Dunuin I'd glanced at that thread and thought it was passthrough specific. I saw a number of suggestions on how to set the previous kernel as default. I was wondering what is the best practice. Could I say, purge pve-kernel-5.13.19-4-pve and mask that version in dpkg. Leaving grub...

I have Intel SATA ports configured as AHCI in BIOS with one port designated as hotplug. I use this, connected to an HDD caddy, for hotswap drives as a (non pve storage) backup destination. Despite some warnings due to incomplete ACPI implementation of this board: ACPI BIOS Error (bug): Could...

I also have a self signed CA installed under android 10 (user) trusted credentials. The proxmox app didn't appear to recognise this when I tried using it a while back. I use two other android apps that utilise the same certificate: OpenVPN for Android. However the CA is inline in the vpn...

I just got caught out by this CT restore behaviour. This post seems to be the only mention of it that I can find. I may be mistaken, but don't remember this happening before. Is it a change in PVE7? IMO it would be preferrable if the restore process did not delete and recreate those volumes...

I recently aquired a new switch that has various MIB counters (Zyxel GS1900). Everything looks good part from one metric, etherStatsOverSizePkts. This is only non-zero on the two VLAN trunk ports I have configured on the switch. For one of these ports in particular, it runs into the 10's of...

I don't know. Perhaps jvm is not seeing (or seeing a higher value) the memory allocated to the container. Maybe it's seeing total host memory? I did not attempt to debug log jvm further. In my ignorance, I put it down to running a container created using a 6.4 template under the new lxc...

OP, assuming you're using PVE 7 here. I had an existing ubuntu 18.04 container running an up to date elk stack where, after the upgrade, I had to set explicit jvm heap limits. For example: # /etc/elasticsearch/jvm.options.d/heap.options -Xms4g -Xmx4g Something changed with LXC between PVE-6.4...

I just did an in-place upgrade to 7.0.10 using the guide and it went very smoothly indeed. Great job! One change/anomaly I noticed after upgrading PVE: A container running a single instance of elastic stack worked fine under pve-6.4. After upgrading PVE, the elastic process (java) in that...

I took a chance and did the following: Commented out suspend related config (lock, runningcpu, runningmachine, vmstate) in /etc/pve/qemu-server/195.conf. Rolback to snapshot The web interface would not allow me to delete the suspend state volume. It claimed it was tied to an existing vm...

I hibernated a vm via the web UI for a few minutes and them attempted to resume it: ~# qm resume 195 Resuming suspended VM activating and using 'vmdisks:vm-195-state-suspend-2021-04-25' as vmstate id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0 id 1, group 1, virt...

RE CA certificate. I have added the relevant CA certificate to the Android user cert store. Should the Proxmox android app recognise this? I still seem to have to turn off SSL validation.