On Thu, 2011-03-24 at 10:28 +0800, wuyu8242 wrote:
>  
> 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.

KVM autotest produces a lot more output than that, such as serial
console output and screenshots of the tests, provided that you have
installed python-imaging. It'd be useful to look at the entire results
dir (under the 'default' folder). Things I suspect might be happening:

1) Slow machine, not able to fully boot guest during the timeout
specified. Increasing the login_timeout on tests_base.cfg might help.

2) You have selected tap mode networking and don't have a dhcp server
accessible through your bridge. If you didn't change tests_base.cfg,
then it's not the case, nevermind.

If you have looked at the VNC console, you might have an idea of what is
going on.

Lucas


_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

Reply via email to