In case someone is having similar issue, this is a BIOS (likely an issue with EC firmware). After a full BIOS flash + reset, everything is back to normal.
Thank for the reply @bbgeek17,
I too was thinking is was likely a Virtio driver issue, but your post made me check the network link stats on the PVE host (which I failed to do yet), and I noticed that the multicast packet count was 0 on the VMs...
I tried another Chromium-based browser(Vivaldi), there was no problem there. So I figured it might be a caching issue. I rebooted my PC and voila now when opening Proxmox web-interface in Chromium I see "Valid" and "Secure" Really odd issue, as...
Reading the forum more, it seems to be affecting newer platforms as well. Issue appears to be introduced with 6.17.4-1 series. 6.17.2-xxx is good (post 10 of this thread)? That was not the case in my case (z97 board). The pve 9.1 iso includes...
Thanks again @dylanw, that did the trick!
For future reference, here are all the commands I used:
fdisk /dev/sda
p
n
<enter> x 3
p
w
pvcreate /dev/sda4
vgextend pve /dev/sda4
lvcreate -L 30G --name iso-storage pve
mkfs -t ext4...
Happy to help :)
What I would suggest is following steps 1-3 above, to extend the volume group with a new partition, then create a new iso-storage volume in the pool by:
1. Create a new logical volume for the ISO storage: lvcreate -L 30G --name...
If you need automatic migration, i.e. HA functionality - the storage must be named the same. There is, currently, no storage mappings with HA.
If you are doing manual migration, you can specify target storage in CLI/API (not in PVE UI). I believe...
Hi @Hemi ,
Since you’ve confirmed that multicast traffic is being received on both the hypervisor and inside the VM, this is most likely a statistics-reporting discrepancy between the Virtio driver and the Linux kernel.
I don’t have guidance on...
Sorry to Reply to such an old thread, but as a follow up question: Does this mean that for a success migration from a heterogeneous node to node, the storage should be named the same for a successful transfer? or do you need to set the mappings...
You are correct regarding WWID. I will see myself off to get more coffee. In the meantime, I have updated my reply in #3 and deleted subsequent one.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
You could move your vm/lxcs storage data to the empty zfs disc:
Then you would save your existing config in /etc/pve with tar or rsync and restore it after reinstall.
In any case:
- First test this with a VM with PVE first. So install a VM with...
May I ask why you do only weekly backups? I would want to avoid the loss of one week of work. I myself do this:
I have one cluster and one single-node PVE install which together holds my vms and lxcs (one is my testing environment, the other...
and my reply was to @AceBandge who asked
OPs question has already been answered afaict. if its not clear- use clonezilla. in the list of priorities for the devs to follow I'd much rather them add useful features or squash bugs then add a tool...
Hello,
I have a new PVE 9.1.4 cluster set up with a number of RHEL9.7 (AlmaLinux) guests, which were previously bare-metal hosts. I noticed that once the hosts were converted to VMs, received multicast packet counts stopped being reported, i.e...
You wrote: "All backup clients are configured to run their backups once per week at around 11am of sunday".
So you need not to add WOL to backup functionality nor backup clients. It would be enough to issue WOL from a cron in one of the machines...
Hi,
I guess you have a HA with 2 nodes and no QDevice, if yes, it's normal by design because you lose the quorum.
See: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_cluster_requirements
Best regards,
Updates so far. I got a new power supply and installed it but system is still locking up. I attempted to tell the kernal to use a different clock but I think it ignored me and locked up again with the old one. I am now trying again with c-states...
In my own efforts I've found that CLI cloning works. Proxmox GUI clone feature zeros a disk before cloning occurs, this is causing the issue. I'm going to see if I can find any config files to modify this feature out.