mateussouzaweb / kvm-qemu-virtualization-guide Goto Github PK

Some folks (me included) don't use display managers like lightdm or gdm
I personally just execute good old xinit right after login (using .profile), other people use ly or tbsm

Point is not all use a graphical display manager.
I ended up editing stop_display_manager to

function stop_display_manager {
  pkill xinit
  while pgrep xinit > /dev/null; do
    sleep 1
  done
}

Which works fine (keep in mind this is x11, wayland people should do something else) however I couldn't get restore_display_manager to work
Simply executing xinit doesn't do anything, I believe because it's not executed in a tty

The end result is whenever I shutdown my vm, I face a really scaled down version of my tty to the point all text becomes blurred

I can execute xinit or startx - and get back to my window manager just fine (even the tty restores its original resolution) but I'd rather my window manager be automatically launched

I will test with ttyecho and see what I can do

Hello, I have an Asrock X570 Phantom Gaming 4 motherboard, a ryzen 5 3600 CPU and a Radeon 5500XT. My question is that do i also have to enable AER cap and ACS in the BIOS or just enabling IOMMU is enough to proceed with the guide.

Hi, i'm about to install macOS. But failed hanging at the TianoCore Bootscreen, that might be a problem of a messed up XML editing see Post #3

Here are some specs of my system:
Huananzhi X99-F8D
2x Xeon 2620V3
64 GB DDR4
GPRO 4300

Normally i run the system with an Samsung NVME. For testing purposes i use an old SSD.

Hello while I was studying the ubuntu.xml sample I came across these lines

    <hostdev mode='subsystem' type='pci' managed='yes'> 
       <source> 
         <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> 
       </source> 
       <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>

Could you please tell me what is this device on the host machine?