Search results

However, it's running

not the same issue but under the should under the same thread, PVE doesn't show me correct RAM usage , the real usage is 1.4GB, but PVE show me 3.19GB. I already make qemu-ga running inside my VM , and already enable Use QEMU Guest Agent in the VM configuration. see bellow screenshot.

I found it, under current version: In OVMF(UEFI) mode , if I enable hotplug for cpu and memory , then the booting will fail. In SeaBIOS mode, if I enable hotplug for cpu and memory , then the booting will success.

Please see bellow: > pveversion -v root@pve1:~# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.78-1-pve: 5.4.78-1...

If I use the default BIOS , then it did not have this problem .

Currently, my PVE is under bellow version: pve-qemu-kvm 5.2.0-5 amd64 Full virtualization on x86 hardware pve-manager/6.3-6/2184247e (running kernel: 5.4.106-1-pve) I tried to Install windows 10 v20H2 , and tried to boot the new created VM that configure with OVMF(UEFI). But...

I believe it's related. before I update to latest version , my VM will not been lock (it's freeze in my words)

Update: In the Bios of Hardware page, if I choose to use OVMF(UEFI) , when I start a new created VM ,the cursor will be freeze at the screen -- see the screenshot. If I choose Default(SeaBIOS), then the cursor will be freeze for a few second , then the VM will be boot into OS. bug ?

I update to latest today, and then issue comes, please help , I can't boot new VM after I create it. This is my pve info: pve-qemu-kvm 5.2.0-5 amd64 Full virtualization on x86 hardware pve-manager/6.3-6/2184247e (running kernel: 5.4.106-1-pve) And bellow is the error info: (PS: I...

thank you so much , love you !!

In FreeNAS , we can change the sync interval by change the value of vfs.zfs.txg.timeout. That is relative to sysctl.conf or sysctl tool . But in PVE , I can not find the way to change the sync interval of ZFS in PVE from the internet. By default , it sync every 5 seconds, I don't like that...

Adding filter to syslog-ng on FreeNAS work for we. but I hope proxmox devs fix it from the source. env: PVE 6.2-12; FreeNAS-11.3-U5

https://forum.proxmox.com/threads/freenas-vm-reboots-after-shutdown.27276/ -- it solves my problem. But： 1. the issue of Smart Functionality is not available in FreeNAS remains 2. why the KVM64 cpu doesn't work with FreeNAS VM, I think the performance of KMV64 is better than QEMU64...

Thank you,you save me a lot of time. I even post another thread for the same issue.

I can create a FreeNAS VM by using FreeNAS Image (FreeNAS-11.3-U5.iso) in proxmox. The VM installation is successfull without problem. 1. When I shutdown this VM from its console option list which is 11) shut down. the vm was been reboot rather than completely shutdown. 2. I also tried to shut...