Recent content by ZKallo

I tried kvm64, x86-64-v2-AES, x86-64-v3 with Machine i440fx and Balloon=1 and none of them worked well. What is working now: Balloon=0, Cpu=host, Machine=pc-q35-8.2. Maybe blind chicken did find seed.

Thanks for your answer. It seems that the upgrades were processed at different repository settings. I think we'll wait for the enterprise repository update. Best regards, Zoltan

All nodes have a subscription and all nodes use the same suite (bookworm) and components (main contrib, enterprise, pve-enterprise). The fourth node (with version 8.2.3) doesn't find any updates and all others already has upgradable updates at this moment. There are no enabled no-subscription...

Hi, we have 4 nodes and they were upgraded to PVE8. There were 3 nodes with clean install and one was upgraded from 7 to 8. The final versions are now 2 clean installed nodes have version 8.2.4 and the other nodes have 8.2.3. (The main problem with this that vms with default hardware version...

I've read this here in the forum but I don't know the author. If you can't wipe the previously used OSD disk therefore you can't readd the disk in PVE8 do the following: list the disk with lsblk You can see that the required disk was used for ceph because it has a ceph ID beginning with...

Hi, FYI: we had to do a new PVE8 install because of a boot disk error and making to run the script (it doesn't make too much sense at this stage) here also comes the warning : WARN: unexpected running and installed kernel '6.8.8-1-pve'. with regards, Zoltan

What worked: stopping vms, renaming conf files and copying to a network share, copying to the new node, renaming back. What didn't work: remounting pve-root as rw ( it said: "write protected")

It is a 32GB SSD as the machine came from the factory. There is no backup from it. We would see what's wrong with it when we will have moved all of the vms from that node.

Try to rename the conf file, move it and rename back on the new place. (I've done this so that I copyed the renamed file to a network share and copyed to the new node then renamed it back on the new node.)

Thanks for your answer. It gave me a hope. I'll try these suggestions soon.

Thx for your answer, - I launched fsck in read-only mode on root filesystem and there were lots of errors. - We haven't implemented HA.

We have four nodes, on one of them the root filesystem became readonly and there are running more virtual machines on it. We have enough resources to move them on an other node but what could we do successfully because lots of things cannot be done. (e.g. we cannot move, make backup, didn't try...

Hi, I upgraded PVE from version 7.4.x to 8.2.2 in a test environment. After the installation the pve7to8 gave a warning: unexpected running and installed kernel '6.8.4-3-pve'. I think this version of kernel should be running. Why does this warning come up? I realized later that the file...

pve-qemu-kvm:amd64 - from 6.1.1-1 to 7.1.0-4. This upgrade solved the Windows Update restart hanging problem. USB device warning. It was interesting that after a disabling-enabling operation the warning sign was not there at the USB device and the disk appeared as drive in the operating...

Hi, I have had the same problem. I upgraded the nodes from version 7.1 to 7.3 because the Windows updates were stuck every time. Almost all of the Windows vm-s' type of machines is pci-i440fx-5.1. (I don't know when and why should I change the version number of the machine.) The vm didn't...