My old Proxmox installation had HDDs for Data and two 850 Pro in a mirror for two Windows 10 VMs, these SSD wearout quiete quickly, on died after just 10 month due to wearout and had no more spare blocks to compensate.
My new Proxmox hosts is based on 4x Intel D3-S4510 3.84TB in a ZFS Strip...
Hi,
good idea, but i tried a different approach, i installed a debian bullseye container and tried to use the approach from the proxmox developer docs, i failed because there are a lots of dependencies that are not native debian packages and only exist for amd64...
Hello,
today i got one of the Oracles always free Ampere A1 ARM instance and thought it would be a good idea to backup content to my proxmox backup server, sadly it looks like there is no arm64 build of the Proxmox backup client.
Skipping acquire of configured file 'main/binary-arm64/Packages'...
Windows Server 2022 requires Secure Boot with TPM 2.0. VMware has TPM for quite some time. oVirt added TPM 2.0 with Version 4.4.6 and so does RHEV. I hope we see TPM support soon. Customers Buying Windows Server 2022 without Assurance has no way to run it on Proxmox because they have no...
Oracle ist ja schon seit 2006 dabei und lxc container gab es irgendwann mit version 7, eigentlich wundert es mich da so wenige die Dist auf dem Schirm haben. Schnellere point releases im Vergleich zu CentOS, vollen Errata Support im Repo. Ok manche mögen evtl. die Company dahinter nicht...
Wegen der CentOS Thematik sind die ganzen RHEL clones sehr beliebt. Ich hab da schon länger nicht mehr reingeschaut was aktuell eigentlich von Proxmox unterstützt wird. Ich schau mir mal die verfügbaren Clone an und prüfe für welche es LXC Container gibt, teste dann bisschen durch händisches...
Neben den Templates braucht man leider auch Support in einer der Perl Dateien von Proxmox. Es gibt z.B. lxc images von Oracle Linux, leider konnte ich es nie benutzen weil Proxmox das OS nicht erkennt, es fehlte einfach die OS Detection für das System. Natürlich kann man die Datei verändern aber...
46% Wearout on your sdp drive? that looks really bad, afaik consumer SSD have only a reserve for around 15% until they die.
In the past i run a small Proxmox Server with four Samsung 850 and they wearout in about 4 month with just a few containers running. I changed SSD to Intel D3-S4510 and...
I have the same issue. I always get stuck "dev" folders in container directorys after a reboot. I think this dev folders comes from tun device passtrough not getting cleaned up after restarting Proxmox host. I give your solution i try.
Little update, all zfs volumes for containers are unmounted. I mounted all by hand and i am able to start the container afterwards. One of the containers got an lock item and tells me it is mounted?
# pct list
VMID Status Lock Name
203 running mounted minio01...
Same issue on my side. VMs from ZFS works find but containers fails with:
Jul 18 19:17:54 x lxc-start[5374]: lxc-start: 212: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container state
Jul 18 19:17:54 x lxc-start[5374]: lxc-start: 212...
Host expose the whole CPU type and features to your VM. kvm64 is limited in feature flags and always show the same type to the VM. kvm64 is nice if you live migrate between hosts with different CPU types, it also helps not loosing windows activation because CPU Type, SMBIOS and stuff stays the same.
Yep, for me the new drivers solved my problems. All VMs with updated drivers still running. I startet some other unused VMs with older VirtIO and all of them crashes after some time. I think something changed in the Hypervisor and this change is not compatible with older VirtIO drivers, which...
Here is the output of pnputil.
Microsoft PnP Utility
Published name : oem3.inf
Driver package provider : Red Hat, Inc.
Class : System devices
Driver date and version : 02/12/2017 100.74.104.13200
Signer name : Red Hat, Inc.
Published name ...
I updated virtio drivers on two Windows 10 VMs and had no crashes so far. If this is really the solution i wonder what changed in qemu. I used 0.1.126 for a long time with Windows 2016 and Windows 10 without any issues.
So far it looks good.
Today the same issue with Windows 10 16299.19
Start VM > wait a little bit > boom > reboot > OVMF Bios stuck with Proxmox logo and freeze with KVM sitting there at 100% CPU load. The only way to get rid of the VM is by killing KVM.
VM is running virtio drivers 0.1.126
VM Config:
agent: 1...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.