hi Lucas,
First of all thanks a lot for your help and detailed introduction of
vnc！I believe it was useful very much! This question is caused by the failed
result of running kvm-autotest script. Now, I will tell about the test result
of steps as following: (btw: these steps followed Amos's points)
1. get autotest code from git repo
# git clone git://github.com/autotest/autotest.git -----ok
2. change to kvm sub-directory
# cd autotest/client/tests/kvm -----ok
3. prepare env by 'get_started.py'
# ./get_started.py -----ok
4. execute autotest ( default tests: 'installation','boot','shutdown')
# /home/tzx/autotest/client/bin/autotest --verbose
/home/tzx/autotest/client/tests/kvm/control -----failed (btw: the
installation is ok, the boot and shutdown is failed, detail as following)
the result of step 4 as following:
1) 18:00:15 INFO | Running qemu command:
/usr/bin/qemu-kvm -name 'vm1' -monitor
unix:'/tmp/monitor-humanmonitor1-20110316-001510-1dDv',server,nowait -serial
unix:'/tmp/serial-20110316-001510-1dDv',server,nowait -drive
file='/tmp/kvm_autotest_root/images/f14-64.qcow2',index=0,if=virtio,cache=none
-device virtio-net-pci,netdev=idR6I5zi,mac='9a:6f:0c:eb:91:6c',id='idLaIa7A'
-netdev user,id=idR6I5zi,hostfwd=tcp::5000-:22,hostfwd=tcp::5001-:12323 -m 512
-smp 2 -drive
file='/tmp/kvm_autotest_root/isos/linux/Fedora-14-x86_64-DVD.iso',media=cdrom,index=2
-drive file='/tmp/kvm_autotest_root/images/f14-64/ks.iso',media=cdrom,index=1
-kernel '/tmp/kvm_autotest_root/images/f14-64/vmlinuz' -initrd
'/tmp/kvm_autotest_root/images/f14-64/initrd.img' -vnc :0 -boot d --append
'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0'
2) when the above steps finished execution, I running the scan_results.py
script, the result as following:
[root@localhost kvm]# ./scan_results.py
Test Status
Seconds Info
---- ------
------- ----
(Result file: ../../results/default/status)
virtio_blk.smp2.Fedora.14.64.virtio_net.unattended_install.cdrom GOOD
840 completed successfully
virtio_blk.smp2.Fedora.14.64.virtio_net.boot FAIL
296 Unhandled LoginTimeoutError: Login timeout expired (output: '')
[context: logging into 'vm1']
virtio_blk.smp2.Fedora.14.64.virtio_net.shutdown FAIL
406 Unhandled LoginTimeoutError: Login timeout expired (output: '')
[context: logging into 'vm1']
---- GOOD
1556
so, the kvm autotest running failed finally, I check the qemu command, then
suspect the vnc is wrong or not. Until now, the problem still persists.
Thank you again!
ps: the attachment is the complete log.
Best Regards,
wuyu8242
发件人： Lucas Meneghel Rodrigues
发送时间： 2011-03-23 00:35:35
收件人： wuyu8242
抄送： Amos Kong; autotest
主题： Re: [Autotest] About using kvm-autotest
On Tue, 2011-03-22 at 11:54 +0800, wuyu8242 wrote:
Guys, I must say I didn't understand the conversation.
I tried to infer something from the context, I hope I got it right -
wuyu8242 wants to follow the VM during KVM autotest execution to see
what is going on, but can't find the tools to check the VNC display.
Assuming I inferred correctly, here goes the step by step instructions:
1) If you execute kvm autotest on a machine where you have vnc access
to, to follow what's going on with the VM, it is easy. on Fedora 13,
there is vinagre, a VNC client:
Applications -> Internet -> Remote Desktop Viewer
On the toolbar, there's a 'Connect' button, if you click on it you'll
get a dialog that says:
"Which machine do you want to connect to?" and a series of options
Select protocol VNC, and on host, type:
localhost:5900
(5900 if kvm autotest says the vnc port is 0, 5901 if it is vnc port 1,
so on and so forth)
Then click on the 'Connect' button.
If for some reason the machine running kvm autotest is not the local
machine, just change localhost with the machine hostname, such as:
fudge.bakery.com:5900
Make sure port 5900 is accessible on either your local machine or the
remote machine. Then everything should work.
VNC is a protocol to transmit remote display of a generic machine over
the network. qemu has a built in VNC server, that will broadcast the
remote display to a given client. In this case, for Fedora 13, the
client is the vinagre application I am talking about. The VNC server can
be always accessed by the port 5900 of the remote machine (assuming vnc
port 0, and assuming 5900 is accessible, ie, not firewall blocked).
I hope this was useful,
Lucas
>
>
> wuyu8242
>
> ______________________________________________________________________
> 发件人： Amos Kong
> 发送时间： 2011-03-22 11:34:50
> 收件人： wuyu8242
> 抄送： autotest
> 主题： Re: Re: Re: About using kvm-autotest
>
> On Tue, Mar 22, 2011 at 11:20:46AM +0800, wuyu8242 wrote:
> > hi Amos，bother you again！
> pls look for the following question, thx very much!
> >
> > wuyu8242
> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> > 发件人： Amos Kong
> > 发送时间： 2011-03-17 15:49:59
> > 收件人： wuyu8242
> > 抄送： autotest
> > 主题： Re: Re: About using kvm-autotest
> > On Thu, Mar 17, 2011 at 03:41:28PM +0800, wuyu8242 wrote:
> > > hi Amos,
> > > Thanks a lot! the kvm autotest framework work well with your help!
> > >
> > > The attachment is the debug info, would you help me again to check it?
> > unattended_install.cdrom has completed ?
> > you need check guest status by # vncviewer :$vncport
> >
> > hi Amos，bother you again！
> What is the role of vnc? the optional vnc in the
> > qemu-kvm command of the autotest script. so, I suspect the problem lies in
> > this
> > option.
>
> http://en.wikipedia.org/wiki/Virtual_Network_Computing
>
> ok，I know about vnc. I want to ask you about the role must be exist?
> If I remove the option, what is the effect of the running?
> Because my vnc don't work. The tools need to be installed manually in
> fedora13, but I have install it several times, but it still don't
> work, so I want to remove the -vnc option.
>
> > You reference (http://www.linux-kvm.org/page/KVM-Autotest/Test_Config_File)
> > to change tests.cfg
> >
> > I have read the doc of Test_Config_File, but I still don't know how to
> > change
> > the tests.cfg.
> >
> .
> _______________________________________________
> Autotest mailing list
> [email protected]
> http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
debug_info.tar.gz
Description: Binary data
_______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
