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.
- install qemu (preferably >= 9.0 since that supposedly has (even) easier networking) on any machine (no need to run vserver). You don't need the qemu acceleration kernel module.
- get a kernel image (needs something (what?) configured to be able to run under Qemu?), for example, http://vserver.13thfloor.at/Stuff/QEMU/bzImage-188.8.131.52-vs184.108.40.206
- get a root image from http://vserver.13thfloor.at/Stuff/QEMU/?C=M&O=D
<Bertl> the 32M_public2 img should suffice
- since that image has outdated tools, get http://vserver.13thfloor.at/Stuff/QEMU/util-vserver-0.30.214_bin.tar.bz2 (to be unpacked under / in the root image)
- start qemu like this:
qemu -nographic -m 64 -hda TEST_32M_public2.img -kernel bzImage-220.127.116.11-vs18.104.22.168 -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.