Search results

https://www.phoronix.com/scan.php?page=news_item&px=KVM-L1TF-Whoops Maybe some Proxmox dev can take care of this issue.

As far as I know, edubuntu is a dead project, last release was in 2014.... I don't think is the right decision. I just use Kubuntu, remove "akonadi" package (consumes too much resources and is useless for schools), install a ton of didactic software (I've 2 different sets, one for elementary...

I've also found something about BIOS settings that could worth a shot (not specific to Proxmox but seems important) https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/?tab=comments and probably googling around you can find even more. In my old MB I've always disabled...

Just a shot in the dark, are you sure the ISO is ok and not corrupted (sha256sum -c ...)? I'm going to build a Ryzen 5 3600 soon, really hope there are no issues (and/or RAM compatibility problems)! My current homelab Proxmox server has worked for years flawlessy on AMD FX-6300 Six-Core Processor

Be honest... how often plugging a hard disk from your VM is a good idea against a bad nightmare? Default behavior (and so related default option) is that no one removes disks on running PC/Servers/VM, doing so should be just a nice feature that you can enable if really needed.

Yes, I've used to test ZFS with "hot unplug" event. In "Options" there is a HotPlug setting, maybe disk hotplug should be set to FALSE by default instead of true! If someone is willing to file a feature request... is welcomed :)

KEEP THE VM RUNNING AND search the forum, I remember that as long as the VM is still running, the OS does not *really* (yet) delete the file qcow2! Keep the VM alive and find the post about it, there is some sort of trick AFAIR to "resurrect" it. FOUND the thread...

Without HA, you can manually move the vm (I've asked many times for a GUI solution for small 2 node setups when you can phisically see the server that is turned off and want to start with easy the survived one). Have a look at "Migrating a guest in case of Error" inside...

Ah, if you mean the "internal" usage of the virtual disks by the VM ("how free space do I have in C: of the 101 Windows VM?"), you can't AFAIK, maybe with some qemu-agent/monitor command, nothing exposed in the Web interface right now, in any case

If you on the left side have "Server View", go down in the tree until you reach the storage you want to know about and then select it. (i.e. you can select "local"). Then in the dashboard you will have some information included "usage" (i.e. 26.34% (219.95 GiB of 834.95 GiB)) and a graph...

Your vm "disk" format is raw, can't be anything different in ZFS pool volume. Since possible formats depend upon the type of storage you have, in your screenshot the "Target Storage" is not shown, so the "Format" is the default, but has no meaning until you choose the "Target storage". Once you...

Just for curiosity and forgive my ignorance, what do you mean with "directly connected"? What cables / slots / whatever are you using to put 14 of those drivers in Dell R7515? Does Dell R7515 have 14 U.2 connectors?

Seems there is already one there, since 2013... "postponed", any hope in the next 7 years :)? https://bugzilla.proxmox.com/show_bug.cgi?id=208

I would be interested too! Some month ago I was plagued with a lot of "strange" VM behaviours, broken boots, clones unable to boot, whatever. After a lot of struggling I've found that the CPU fan was melted and so as soon as CPU temperature raised, all evil thing happened. If I only had a CPU...

Wolfgang in his last but one post (comment 7) said that new features have solved the issue and no one replied that it was not the case, so he closed the issue. Maybe if you add comments there about this it could help to reopen and solve the problem?

Hi, I've a vm (Kubuntu 19.04) that I use to test Freecad and that I turn on when needed. I've no need of "mitigations" about CPU flaws or whatever, I just need more performance I can. In the vm I've disabled all CPU flags (-md-clear;-pcid;-spec-ctrl;-ssbd;-ibpb;-virt-ssbd;-amd-ssbd;-amd-no-ssb)...

I had some issues too, and some strange behaviour (new VM corrupted or clones that could not boot or they crashed)... then I've found that the fan of the CPU was not working and so CPU overheated under a lot of situations, and inside the case the temperature was higher too (CPU fan, when...

Do you think that this is the problem and has been fixed with this commit? https://github.com/virtio-win/kvm-guest-drivers-windows/commit/62e452b94b5277775f7bee7a0ec1f6148f8a1811

They are in /etc/pve/nodes/[NAMEOFTHENODE]/qemu-server/ like in my node (hostname) that is named "proxmox", vm 114 is in the file /etc/pve/nodes/proxmox/qemu-server/114.conf

With Kubuntu 18.04 I'm sure it worked fine (up to resolution 1920x1200 or something like that), but after upgrading Proxmox some time ago, it does not work anymore even in VM I don't upgrade at all. I don't mean "dynamic resolution", but simply changing resolution with the screen setup panel...