You are not logged in.

#1 2017-03-20 10:49:27

maldus
Member
Registered: 2017-03-20
Posts: 28

Virtual machine on qemu - unable to run with curses/nographic

Hello everyone,
I have created an Arch linux virtual machine running on qemu. I successfully followed the install tutorial everything works as intended.
Now, I'd like to run it with the qemu nographic or curses option (in terminal, not with SDL); however when I try to I either get to the login prompt for half a second before stopping to the message "1024 x 768 Graphic Mode" (with -curses option) or no output whatsoever (with -nographic option).

Details:
I installed GRUB and set /etc/default/grub to boot the first entry without waiting in command line mode:

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""

GRUB_TERMINAL_INPUT=console
GRUB_TERMINAL_OUTPUT=console


With the -curses option I can see grub and kernel messages scrolling before getting to the login prompt and losing it.
I have installed no Desktop environment or display manager, just the base group and grub.

The exact command I'm running is:
$ kvm -net nic -net user  -drive file=test.img,format=raw  -m 2048 -curses

I have tried the same thing with a couple of other linux images and it works, so I'm guessing that there is some kind of graphic option that kicks in at the login shell, and curses is not able to render it.
I hope this is the right place to ask (since it works with other distros I guess it's not a problem with qemu).

Offline

#2 2017-03-20 13:40:10

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,567

Re: Virtual machine on qemu - unable to run with curses/nographic

the -nographic options doesn't disable the a graphics mode but only the SDL display.
It's mostly used to allow a graphical connection to a headless system using the VNC protocol.

-curses option
systemd by default boots into graphical target, try booting with "systemd.unit=multi-user.target" (very similar to sysvinit runlevel 3) as kernel parameter.

see systemd wiki page, "Change default target to boot into" for details.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

#3 2017-03-21 08:24:34

maldus
Member
Registered: 2017-03-20
Posts: 28

Re: Virtual machine on qemu - unable to run with curses/nographic

Thanks for clarifying the -nographic option, I don't know how I missed that.

Unfortunately I've had no luck even with the  systemd target: I've tried to change it to multi-user both by kernel parameter and by switching it with systemctl, but I get the same results.

Offline

#4 2017-03-21 11:34:21

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,567

Re: Virtual machine on qemu - unable to run with curses/nographic

Try booting with "VGA=ASK"  , then select one of the text modes offered.

That should disable KMS completely and force linux to fallback on pure textmode .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

#5 2017-03-23 08:35:22

maldus
Member
Registered: 2017-03-20
Posts: 28

Re: Virtual machine on qemu - unable to run with curses/nographic

The vga=ask parameter is not supported anymore, and the image fails to boot. At the GRUB command line I found some vga modes with the vbeinfo command; I tried a couple of them marked as "text mode" (like vga=0x00, 0x01, 0x0a), but there was no difference beside a warning for using a deprecated parameter.
Still getting to the login shell and then blacking out.

Offline

#6 2017-03-23 15:10:18

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,567

Re: Virtual machine on qemu - unable to run with curses/nographic

Kernel documentation still does mention them, but states they're actually bootloader parameters.

Try with "nomodeset" .

Testing against different kernel versions could also help to narrow things down.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

Board footer

Powered by FluxBB