On 08/03/2011 02:46 AM, Sasha Levin wrote: > This patch adds 2 new flags: > > --rootfs [path] - Specifies a path to use as rootfs. The path will be mounted > using virtio-9p and booted from. > Easiest way to test it is to mount the sample image we recommend with kvm tool > (http://wiki.qemu.org/download/linux-0.2.img.bz2) and mounting it somewhere. > *PLEASE DO NOT TRY BOOTING FROM YOUR REAL ROOT AKA '/', EVEN WITH READ ONLY > SET* - Lets make sure the code is bulletproof before we delete your rootfs :) > > --binsh - This flag will boot into simple /bin/sh shell instead of going > through /sbin/init. This is usefull for more complex distribution rootfs > where we have to deal with /etc/fstab and such. > > Signed-off-by: Sasha Levin <levinsasha928@xxxxxxxxx> This is damn impressive! All I needed is: ./kvm run -k /home/asias/qemu-stuff/bzImage --rootfs /mnt/ I found that if I boot with ./kvm run -k /home/asias/qemu-stuff/bzImage --rootfs /mnt/ I will get: sh-2.05b# echo a > /root/a sh: /root/a: No such file or directory If I boot with sudo ./kvm run -k /home/asias/qemu-stuff/bzImage --rootfs /mnt/ sh-2.05b# echo a > /root/a works. It seems that it is a permission related problem, however, the warning message is "/root/a: No such file or directory", any ideas? -- Best Regards, Asias He -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
