On δΈ‰, 2005-11-09 at 12:46 +0100, Martin Koniczek wrote: > > "sudo qemu -hda testaa.img -boot c -localtime -serial stdio -pidfile > > pidfile1.txt && sleep 300 && root && 123456 && ifconfig" > > > > you intend to queue commands to be executed within the qemu guest? Yes! > > && is not suitable for "entering commands", it is a sh/bash control > operator (which executes whatever comes after && if the previous command > returned true, read "man bash" to learn more about this) I know it now, I make a mistake about it, thank you! > > furthermore, what you intent to do seems to rely on a linux guest kernel > where kernel console (and login shell like agetty) is redirected to > ttyS0, so make sure your guests kernel configuration and /etc/inittab > are set up properly. Yes, I have make the line: #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 in guests kernel available, and it work success in terminal. > > but even if you "correctly" pipe commands to your linux guest, i doubt > you get the results you want - agetty clears any stdinput before the > password prompt etc, so you'd need an "interactive" script to parse > stdin and generate stdout (from remote controls script view), for > example "expect", see "man expect" This is the substance of the problem should solved. So I use a nonBlockingIO script to do it. (If anyone interested in it, I can send she/her the script) Thank you for you suggest. > > and if you expect to interact on the serial console after your "startup > commands", you would be lost with classical piping anyway. perhaps > screen helps you there? see "man screen" I have try it, but it's no help to me. Beause I must use program. > > if what you showed in your example is really what you want to to, how > about a simple script within the guest executed in the end of the > startup process, which shows you the current ifconfig? (see your guests > /etc/rc* scripts for that) This way I also bethink of, But the problem is the guest don't know the host IP. and the host IP is no static. > > running sshd in the guest and queing commans via ssh is of course the > most stable (and not-qemu-specific) solution, but required correctly > set-up networking between guest and qemu. My net work is work. I use TUN/TAP, bridge-util, DHCP. and it work ok. > > sincerly, > martin koniczek
Thank you very muck Best regards Zheng SW _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
