Difference between revisions of "Debugging"

From Linux-VServer

Jump to: navigation, search
(add qemu command line)
(+cats)
 
Line 11: Line 11:
 
  qemu -nographic -m 64 -hda TEST_32M_public2.img -kernel bzImage-2.6.22.16-vs2.2.0.6 -append "rw root=/dev/hda1 init=/bin/bash"
 
  qemu -nographic -m 64 -hda TEST_32M_public2.img -kernel bzImage-2.6.22.16-vs2.2.0.6 -append "rw root=/dev/hda1 init=/bin/bash"
 
* to get the above tar ball into the running Qemu, get networking to work. How to do that is to be done in another session.
 
* to get the above tar ball into the running Qemu, get networking to work. How to do that is to be done in another session.
 +
 +
[[Category:Documentation]]
 +
[[Category:Community]]

Latest revision as of 20:06, 21 October 2011

In the case that the core developers cannot reproduce a problem you're running into, it's recommended to use Qemu and known filesystem and kernel images and go from there, then providing the necessary changes (probably a tar file or maybe patch of the changed files).

NOTE: I (User:pflanze) couldn't get through all of this yet, this is just a start, this page needs to be completed.

<Bertl> the 32M_public2 img should suffice
qemu -nographic -m 64 -hda TEST_32M_public2.img -kernel bzImage-2.6.22.16-vs2.2.0.6 -append "rw root=/dev/hda1 init=/bin/bash"
  • to get the above tar ball into the running Qemu, get networking to work. How to do that is to be done in another session.
Personal tools