Search results

This might be the reason... root@pve01:~# apt-get update Hit:1 http://security.debian.org bullseye-security InRelease Hit:2 http://download.proxmox.com/debian/pve bullseye InRelease Hit:3 http://ftp.dk.debian.org/debian bullseye InRelease Hit:4 http://download.proxmox.com/debian/ceph-pacific...

Now I am getting this on one host: Ohh the joy! [ 1924.671429] RIP: 0033:0x7f48918d3b07 [ 1924.671432] RSP: 002b:00007fff033c71f8 EFLAGS: 00000246 ORIG_RAX: 00000000000...

Yeah, it's working. What I am pondering is the following on an un-upgraded host: root@pve05:~# uname -r 5.11.22-4-pve root@pve05:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following...

No, you were not unlucky. This is sadly still an issue.

rebooting the host yielded it not coming back up. I guess I know what happens if I reboot the other two hosts... Time to waste a few days fixing this mess! At least the network interfaces on the vm's have not gone missing like last time something exciting happened.

root@pve01:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/75.6 MB of archives...

So far so good, and (bad) root@pve01:~# apt-get dist-upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. root@pve01:~# dpkg --configure -a Setting up proxmox-backup-file-restore (2.0.10-1) ... Updating file-restore initramfs... 11516 blocks...

when the updater gets to pve-manager 7.0.11 there is a timeout, a brief dump and then apt hangs. After a reboot, system wont start vm's saying all sorts of nonsense, such as: () TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS...

Well, we will see how PowerBI treats a 10G network. 4 nodes 16 OSD's each

My question did not concern writes, it is about fetching data. which is fastest if done from local storage, obviously :)

You can move the disk in the vm's hardware settings, to a different proxmox-storage location and select RAW as output. Then you can move it back again and also select RAW. Maybe this MacGyvering will work for you?

Hi, I have a question about the path of the storage. If I create 3 nodes with CEPH. Node A,B and C. I have a VM running on node A and I have 3 replicas, and host as failure domain. Thusly A's vdisks will be placed on node A, B and C concurrently Will the VM grab data from storage that is local...

Indeed... "apt-get install covid-19"

Allright, I guess it is just a wierd coincidence where both the Debian and Proxmox repositories have no updates for a few days :D Thanks for the input.

root@pve03:~# apt-get update Hit:1 http://security.debian.org bullseye-security InRelease Hit:2 http://ftp.dk.debian.org/debian bullseye InRelease Hit:3 http://ftp.dk.debian.org/debian...

I use the nosub. I believe all 4 of nodes are the same version as I updated em simultaneously during the weekend. root@pve03:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-5.11: 7.0-6 pve-kernel-helper: 7.0-6...

Hi, is it just me(us) or is there a suspicious lack of updates for at least two days? Reddit post about topic: https://www.reddit.com/r/Proxmox/comments/p6uv7n/is_something_up_with_the_proxmox_bullseye_package/

First PM-HA decides to move a VM to a node on which the storage for the VM does not exist... Great idea! Think the vm would start? No. Think I could move it back to a node with the correct storage? No. It complains that storage..... does not exist (on the node it does not exist on) which is...

5.11.22-1pve