Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
So I have some custom kernels I need to build and such, and QEMU is the preferred method of testing them.
When using QEMU though, there is no scroll back to the "dmesg" output. And obviously I cant grab the dmesg file after. Also, none of the redirection methods, including TCP, telnet, file, or anything actually put this output into a file.
So. How do I get ALL of the text output from QEMU into a file to debug? OR, how do you kernel experts debug things like this in QEMU?
normally, you would ssh into the VM and pipe dmesg into less
Im not following.
If I compile a new kernel and intramfs and boot them up in QEMU, and the kernel crashes halfway through the bootup,.. how am i supposed to SSH to the instance?
I was hoping to find a way to catch all of the kernel text output from start to crash from QEMU. How do kernel/qemu people go about doing that? Because I cannot find the documentation to explain how to do that!