-kernel vmlinuz loads the kernel from the local "./vmlinuz" file.
Qemu system i386 hardware serial#
-append "root=/dev/sda console=ttyS0": console=ttyS0 forces the guest kernel to send output to the first UART serial port ttyS0, which is redirected to the host by the -serial stdio option, and root=/dev/sda points the kernel to use a /dev/sda device to load the wheezy.img.-serial stdio or -nographic redirects input/output to the current terminal.Qemu-system-x86_64 -serial stdio -kernel vmlinuz -hda wheezy.img -append "root=/dev/sda console=ttyS0": Or qemu-system-x86_64 -serial stdio wheezy.qcow2 Or qemu-system-x86_64 -serial stdio -kernel vmlinuz -hda wheezy.img -append "root=/dev/sda console=ttyS0" If you want to see early boot logs, you should pass console=ttyS0 parameter to a Linux kernel command line: qemu-system-x86_64 -nographic -kernel vmlinuz -hda wheezy.img -append "root=/dev/sda console=ttyS0" Early boot messages in the host terminal console=ttyS0 To exit the guest system without GUI, using stdio redirected to the terminal, login as a root (user: root, password: root) and shutdown the system (wait after that for a while): # GuestĢ.To get them, see Early boot messages in the host terminal below. You will not see any early boot logs in the host's console.nographic does the same as "-serial stdio" and also hides a QEMU's graphical window. nographic qemu-system-x86_64 -nographic wheezy.qcow2 You will see a welcome string after a successful boot. serial stdio redirects the virtual serial port to the host's terminal input/output. Input/output to the host terminal -serial stdio qemu-system-x86_64 -serial stdio wheezy.qcow2 Input/output through a named pipe (file)ġ.Early boot messages in the host terminal.Each scenario has been tested on the binaries, links on which I put below in the annex: Binaries used in examples, so you could check it out on your own.
Now I've got a pretty decent collection of working recipes to tune up a QEMU guest, so I decided to organize all that stuff here, and it could be definitely useful for anyone else. While struggling to automate QEMU guest (communicate and control with the shell scripts), I faced with a lot of incomplete, partially working solutions around the internet.
0 kommentar(er)
