summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/performance/2551
blob: 6a58180f860f5e0e7d335fd6c90ef0df3b7ecf8b (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
performance: 0.993
graphic: 0.974
device: 0.854
boot: 0.784
semantic: 0.704
TCG: 0.603
risc-v: 0.596
debug: 0.586
vnc: 0.586
register: 0.511
network: 0.492
hypervisor: 0.477
PID: 0.465
user-level: 0.428
arm: 0.421
virtual: 0.384
architecture: 0.378
ppc: 0.371
kernel: 0.370
VMM: 0.350
KVM: 0.291
peripherals: 0.288
mistranslation: 0.278
assembly: 0.259
i386: 0.224
socket: 0.211
x86: 0.165
files: 0.163
permissions: 0.144

RTC time could run slow 3s than host time when clock=vm & base=UTC
Description of problem:
When start qemu with `-rtc base=utc,clock=vm`, sometime guest time can slower 3s than host. There's no problem (also didn't be noticed) as we often start ntp service, who will adjust our system time. But let's talk about if we havn't enable NTP service(for example system just booted)

After inspect into the code, i found that there are two problem we should think about:
#
Steps to reproduce:
1. start vm with `-rtc base=utc,clock=vm`
2. disable NTP (OS specific)`systemctl disable --now ntpd;systemctl disable --now ntpdate`
3. reboot in the guest
4. after guest started, compare guest time with host time(at the same time) `date +'%F %T.%3N'`
Additional information: