New answers tagged

0

According to fedoraproject.org/wiki you need "UefiShell.iso" to be able to boot into UEFI shell. Since OVMF doesn't ship with any SecureBoot keys installed, we need to install some to mimic what an MS certified UEFI machine will ship with. OVMF now ships with the binaries required to set up a default set of keys. The easiest way is to use UefiShell.iso ...


0

Edit: I joined a Linux discord server and asked about it, they said I should've wrote "/dev/sda" instead of "/dev/sda1"


1

It depends on exactly how the break-out is done. If you're talking about breaking out of a chroot() jail, the PID of the process won't change and something like strace should have no problem producing a trace of it. If the break-out happens by exploiting a kernel or hardware weakness, attempts to trace the jailed process across the exploit might produce ...


1

The way X programs work is that they look for a variable called DISPLAY, which contains the identity of the X server it should connect to, and then connect to this X server. There is no X server running on your VM. However, MacOS can run an X server (calls XQuartz), and you can make ssh forward X connections to this server (either with ssh -X or with the ...


1

We found a way to do it. On the guest: #dmidecode -s system-serial-number VMware-42 39 51 fb 85 54 7c 91-ac 25 e0 d5 f7 6b 13 b2 This serial number is vCenter's "BIOS UUID" for the guest VM, albeit in a slightly different format: Bios UUID : 423951fb-8554-7c91-ac25-e0d5f76b13b2


0

If you want something really light, I would surely recommend Alpine or ArchLinux. Gentoo is a good distro but it would take some time to compile with you current CPU (for my first installation, it took me around 2 weeks with download and compilation with a old core 2 duo).


0

Sorry, according to VirtualBox documentation the PCI passthrough functionality is only applicable when using Linux as the host OS. You would also need to have the optional VirtualBox Extension Pack installed.


0

It is in the firmware package # pkg install bhyve-firmware


2

It turns out the problem had to do with the location of the grub file, and the fact that I was using the wrong path for it. I orignially tried to use grub2-mkconfig -o /etc/grub2.cfg But I should have used /boot/efi/EFI/centos/grub.cfg. as the path to the grub file. So the actual command should be grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg This is ...


0

Identified this as an issue with the ISO itself. Downloaded latest ISO & tested for a month. So far no issues.


1

Edit your QEMU.xml to use the Intel HD audio adapter to work around bug #761031. Open Boxes, perform a full shut down of the virtual machine, and note the auto-assigned name given to the virtual machine. Open up the Terminal and type EDITOR=gedit virsh edit YOURBOXNAME. If you’ve modified the name after installing, you can find the file in ~/.config/...


Top 50 recent answers are included