Bug 597175
| Summary: | Stop/continue Windows guest caused large timedrift | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Amos Kong <akong> | |
| Component: | qemu-kvm | Assignee: | Gleb Natapov <gleb> | |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 6.0 | CC: | ailan, amit.shah, gyue, knoel, tburke, virt-maint | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 707939 (view as bug list) | Environment: | ||
| Last Closed: | 2010-06-20 06:24:47 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 580953, 707939 | |||
|
Description
Amos Kong
2010-05-28 10:10:50 UTC
I just tried it and it did work for me. Once you 'cont' time runs pretty fast until it catch up. Note that it is a weird check, not sure it worth testing This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Works for me too. It takes time for clock to catch up so verifying time to fast after continue may lead to incorrect result. Adjust steps to include "sleep 30" after continue and before verifying guest time and retest. After added the step of sleep 30s before verifying guest time, the drift time is too short(about 0.22s), it can be ignore. According to comment #5 closing the BZ. Hi gleb, Test with the following steps, timedrift exists, it's about 60 seconds. 1. boot up a win2003.64 guest 2. get the original time of guest ($orig_time) guest)#echo %TIME% 3. stop guest by monitor command #qemu)stop 4. wait for 60 seconds 5. make guest continue running #qemu)cont 6. wait for 30 seconds 7. get the new time of guest ($new_time) guest)#echo %TIME% guest uses acpi_pm clock source (as http://cleo.tlv.redhat.com/qumrawiki/KVM/TimeKeeping) qemu-kvm -name 'vm1' -monitor unix:'/tmp/monitor-humanmonitor1-20101202-154320-E2b8',server,nowait -serial unix:'/tmp/serial-20101202-154320-E2b8',server,nowait -drive file='/home/devel/autotest-devel/client/tests/kvm/images/win2003-64-virtio.qcow2',index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 -net nic,vlan=0,model=virtio,macaddr='9a:72:41:20:79:f5' -net tap,vlan=0,ifname='t0-154320-E2b8',script='/home/devel/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch',downscript='no' -m 2048 -smp 2,cores=1,threads=1,sockets=2 -drive file='/home/devel/autotest-devel/client/tests/kvm/isos/windows/winutils.iso',media=cdrom,index=1 -cpu qemu64,+sse2 -soundhw ac97 -redir tcp:5000::10023 -vnc :0 -spice port=8000,disable-ticketing -qxl 1 -rtc-td-hack -M rhel5.5.0 -usbdevice tablet # uname -a Linux t173 2.6.18-231.el5 #1 SMP Mon Nov 8 18:36:02 EST 2010 x86_64 x86_64 x86_64 GNU/Linux [root@t173 kvm]# rpm -qa |grep kvm kvm-debuginfo-83-215.el5 etherboot-zroms-kvm-5.4.4-13.el5 kmod-kvm-83-215.el5 kvm-83-215.el5 etherboot-roms-kvm-5.4.4-13.el5 kmod-kvm-debug-83-215.el5 kvm-qemu-img-83-215.el5 kvm-tools-83-215.el5 |