grub2-filemanager
grub2-filemanager copied to clipboard
High CPU Usage in VM
Hi , Thank you for this great tool , I tried latest development release in Qemu with OVMF EFI mode , and realized the CPU usage of a core is always 100 % , after turn vm off , it will be ok.
Host OS : Arch Linux
Qemu Arguments : qemu-system-x86_64 -enable-kvm -device intel-iommu -cpu host -smp 2 -machine q35 -m 4G -vga virtio -display gtk,gl=on -bios /usr/share/edk2-ovmf/x64/OVMF.fd -usb -device usb-tablet -cdrom grubfm_multiarch.iso
can't reproduce.
Host OS: Manjaro
Kernel: 5.4
I'm on Arch linux , XFCE , Kernel : 5.9.14. Tested with OVMF x64 and still persists :
qemu-system-x86_64 -enable-kvm -device intel-iommu -cpu host -smp 2 -machine q35 -m 4G -vga virtio -display gtk,gl=on -bios /usr/share/edk2-ovmf/x64/OVMF_CODE.fd -usb -device usb-tablet -cdrom grubfm_multiarch.iso
Tested without OVMF and extra features and still persists :
qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -machine q35 -m 4G -cdrom grubfm_multiarch.iso
I will test it on more real and virtual machines and report , thanks.
Tested on another machine , and still issue exist :
Spec :
Lenovo Laptop
Arch linux , KDE , Kernel 5.9.14
Argument : qemu-system-x86_64 -enable-kvm -device intel-iommu -cpu host -smp 2 -machine q35 -m 4G -vga virtio -display gtk,gl=on -bios /usr/share/edk2-ovmf/x64/OVMF_CODE.fd -usb -device usb-tablet -cdrom grubfm_multiarch.iso
I tried manjaro-kde-19.0.2-200311-linux54.iso and got high CPU usage, so I think this should be a problem with the official upstream grub2 project.
https://bugzilla.redhat.com/show_bug.cgi?id=966416
لقد جربت manjaro-kde-19.0.2-200311-linux54.iso وحصلت على استخدام عالي لوحدة المعالجة المركزية ، لذلك أعتقد أن هذا يجب أن يكون مشكلة في مشروع grub2 الرسمي المنبع.
Change the BIOS settings
Step 2. BIOS Step 2. Click <Advanced>-> <Processor> (CPU)-> Virtual or Virtualization. Once booted in BIOS, it will show the main screen.
Step 3. Set the VT option to Enabled
Step 4. Press Save (usually F10) to save and exit (Save & Exit). Then reboot your computer to take effect of the setting.
@thamermousa This bug is not related to AMD-v/Intel VT-x/AMD-Vi/Intel VT-d , as they be on or off , the issue persists , it's a upstream bug , reported long ago.