Search results

This is my CPU: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Vendor ID: AuthenticAMD BIOS Vendor...

Added amd64-microcode Changed CPU type to host Testing now...

Virtio-Win-0.1.240 I'll monitor logs and post here if something remarkable shows up. It will reboot okay after installation, but after that it becomes really unstable.

proxmox-ve: 8.0.2 (running kernel: 6.2.16-19-pve) pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390) proxmox-kernel-helper: 8.0.3 pve-kernel-5.15: 7.4-6 pve-kernel-5.11: 7.0-10 proxmox-kernel-6.2.16-19-pve: 6.2.16-19 proxmox-kernel-6.2: 6.2.16-19 proxmox-kernel-6.2.16-15-pve: 6.2.16-15...

bios: ovmf boot: order=virtio0;net0 cores: 6 cpu: x86-64-v2-AES efidisk0: local-lvm:vm-102-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M machine: pc-q35-8.0 memory: 8192 meta: creation-qemu=8.0.2,ctime=1699376846 name: Windows11 net0: virtio=3A:0B:D2:AC:4E:1F,bridge=vmbr0,firewall=1 numa: 0...

I have installed both Windows 10 and Windows 11 and each of them are having lockups. It will reboot and go to the "Starting boot option" screen and hang.

All were processed without errors. Thank you!

This solved it... Hope it helps someone else: dpkg --purge pve-kernel-helper ➕

root@nah-prox:/usr/local/mesh# apt update Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Hit:2 http://repo.netdata.cloud/repos/edge/debian bookworm/ InRelease Hit:3 http://repo.netdata.cloud/repos/repoconfig/debian bookworm/ InRelease Hit:4...

Linux nah-prox 6.2.16-6-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-7 (2023-08-01T11:23Z) x86_64 GNU/Linux I have tried all of these and get the same results.

Everything is running okay, just getting these errors. It seems as if it's trying to process OLD dependencies. I could be wrong...

I decided to make the leap from Debian 11 to 12 and Proxmox 7 to 8 to see if it would clear things up... Still issues: root@nah-prox:/etc/apt/sources.list.d# apt --fix-broken install Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 164834 (apt-get)...

That didn't help for me. I posted a thread here. Any help is appreciated. https://forum.proxmox.com/threads/problems-after-6-to-7.131754/

What did you do to solve this? I am having the same (or similar) problem.

Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.140) ... update-initramfs: deferring update...

They are all at different locations across the world. I think you are missing what I am asking. Sounds like it's just not possible right now.

Right, but if the email stops working there isn't a CENTRALIZED place to log into to see the status of all of the servers.

I am not wanting to store the data in the cloud. I have multiple proxmox ve servers and would like a central place to monitor the status of the backups. Having to log into 200 servers vs just one for example.

When you say pull the backups are you talking about the storage too or just the status? We don't want to store ANYTHING on the cloud server. We are essentially just looking for a centralized management and monitoring.

We are an MSP. We would like to be able to: Run Proxmox VE on local physical servers and backup to LOCAL storage Run Proxmox Backup Server in the cloud (like on VULTR or competetor) Is this possible?