Search results

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...

I have lots of trouble with Windows 10 KVMs since 5.1 upgrade. Random lookup, bluescreens and reboots with hanging uefi bootscreen. Currently KVM is unsuable. Tried it with kvm64 and host cpu (sandy bridge xeon). Containers running fine. Downgrade is no option because zfs pool is already upgraded.

Updated to 5.1. So far no issues except qm start on kvm's complain about unknown disk format, it uses raw and lock sector 0 or something.

Is your controller battery/flash backed? if not, your controller waits on sync writes until all data is written to disk.

Hi, maybe container content got corrupted?, i get this a lot with Proxmox 5.x. First i thought this is some fiberchannel issue with my cluster. Last week i saw this issue on a standalone system with local lvm storage. Container stopped to start or complain that files got missing/corrupted.

I am the only one with this issue?

Hi, yesterday i upgraded my Proxmox Cluster from 4.4 to 5.0. My Backend is an IBM Storvize Fiberchannel SAN with LVM for shared access. At first everything looks good, containers and VM starting except i had to build SSH Key trust again in my cluster. Trouble starts after creating new...

My upgraded Cluster starts making trouble. LXC Containers failed to start, some start but fails about missing filesystem or ELF headers missing in pam.so and stuff like that. For me this looks like some sort of storage corruption with lxc? Proxmox is running on shared SAN with LVM. I am unable...

I upgraded my 4 Node Cluster today. Live Migration and updating node by node did the job. Thanks for this great Release!

Did you try wget one of the files to see if your machine has proper internet connectivity?

60G Log is way to much. The Log is kept for 5 seconds and then it get flushed to disk. You can monitor this with "zpool iostat -v 1" Avoid using Consumer SSD's. I recommend using Intel Datacenter SSD for your Log.

You have really low fsyncs. Windows use sync writes all over the place and get a big hit if it has to wait for data to be written. Samsung Consumer SSDs are a really bad choice for Virtualization and Servers in general. Here is one of my private (old) Server. ZFS Raid10 4x8TB Seagate Enterprise...

Thank you. I try to update my Cluster tomorrow.

In 4.10 there is essential support for booting Linux on Ryzen CPU's, later versions supports more features and got more optimization.

Hi, i have a small Proxmox Cluster with 3 Nodes and enabled HA for this Cluster. With enabled HA i have trouble updating the nodes, at some point apt restarts the updated Proxmox Services and rebuilds the initrd for the Kernel, at this step Proxmox (watchdog?) restarts the node because it is...

Make a new disk with 750g, transfer the disk/data, remove old disk.I would recommend to do a block copy not avoid touching anything in your customers vm. This involve some downtime.