On 04/07/2017 14:59, Mark Cave-Ayland wrote:
On 04/07/17 07:35, John Paul Adrian Glaubitz wrote:
On 07/04/2017 07:41 AM, Mohd Yunus Sharum wrote:
Then when i accessed the VM using minicom -p /dev/pts/2, it showed
the boot process stopped until '[ OK ] Found device
You need to pass "console=ttyS0" or similar to tell systemd to
activate a serial console. Console over serial is disabled by
I try (qemu) info status, and shows the vm is running.
I try to ssh localhost -p 5555 but can't login.
In this case, how can i determine if the system is successfully
booted and fully functional? Thanks.
We should maybe change that in debian-installer.
Looking at the dmesg output, it looks like you're hitting the issue
where the bochs_drm module panics on load meaning that you end up with
no framebuffer unless you explicitly set the serial console as above.
I actually managed to debug this over the weekend and sent the patch
so qemu-system-sparc64 should work fine with the bochs_drm framebuffer
when the 4.13 kernel comes out.
Adrian - next time you do a set of Debian images, would it be possible
to include this patch until it lands upstream?
I'm not sure if i really understand this.
Where should i put the option to enable console=ttyS0?
Is it the same if i change the -serial option on qemu-system-sparc64
command as the following?
(This require sudo, and nothing appear when i use minicom -D /dev/ttyS0
LC_ALL=C QEMU_AUDIO_DRV=none \
/usr/bin/qemu-system-sparc64 -name debian-unstable-sparc64
-machine sun4u,accel=tcg,usb=off -m 1024 \
-realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 \
-uuid ccd8b5c2-b8e4-4d5e-af19-9322cd8e55bf -rtc base=utc
-no-reboot -no-shutdown \
-boot strict=on \
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-1,id=ide0-0-1 \
-netdev user,id=hostnet0,hostfwd=tcp::5555-:22 \
-device e1000,netdev=hostnet0,id=net0,mac=52:54:00:ce:98:e8 \
-msg timestamp=on -serial /dev/ttyS0 -nographic