[DragonFlyBSD - Bug #3299] DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3299 has been updated by adrian.


Tuxillo @ the IRC channel asked for my KVM qemu libvirtd execution stanza.

It is automatically generated through using virt-manager on a Debian Linux host.

Here it is:

libvirt+    3497 21.7 12.0 6130296 1977972 ?     Sl   oct.22 997:16 /usr/bin/qemu-system-x86_64 -name guest=dragonflybsd,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-dragonflybsd/master-key.aes"} -machine pc-i440fx-5.2,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram -cpu Nehalem-IBRS,vme=on,vmx=on,pdcm=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,stibp=on,arch-capabilities=on,ssbd=on,rdtscp=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,skip-l1dfl-vmentry=on,pschange-mc-no=on -m 3584 -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":3758096384} -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 7b285e22-0468-4de3-834a-ee170e65b44b -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=31,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -device ide-cd,bus=ide.0,unit=1,id=ide0-0-1 -blockdev {"driver":"file","filename":"/client/libvirt/images/dragonflybsd.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null} -device virtio-blk-pci,bus=pci.0,addr=0x8,drive=libvirt-1-format,id=virtio-disk0,bootindex=1 -netdev tap,fd=33,id=hostnet0,vhost=on,vhostfd=34 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c2:24:94,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -audiodev id=audio1,driver=spice -spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0,audiodev=audio1 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on

Sincerely,

Adrian Kieß

----------------------------------------
Bug #3299: DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)
http://bugs.dragonflybsd.org/issues/3299#change-14178

* Author: adrian
* Status: New
* Priority: Normal
* Target version: 6.0
* Start date: 2021-10-25
----------------------------------------
System environment:

root at dragonflybsd /home/adrian
 # uname -a
DragonFly dragonflybsd.v-zone.lan.dac 6.0-RELEASE DragonFly v6.0.1-RELEASE #1: Thu Oct 14 18:25:27 CEST 2021     adrian at dragonflybsd.v-zone.lan.dac:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64


Running DragonFlyBSD inside a Debian KVM(qemu) virtualization as a guest with hardware acceleration,
the system reports a very wrong uptime, issuing "uptime".

Gkrellm even reports a negative, very strange uptime! Check by running gkrellm from the pkg system.

After ~2 days of uptime, I see this wrong uptime:

root at dragonflybsd /home/adrian
 # uptime
 6:35PM  up 42954 days, 10:01, 2 users, load averages: 0,00 0,00 0,00

The error also was present with Version 6.0.0. This is now Version 6.0.1 and the bug is still there.

Happens about three of four times, the bug is present right after booting into the system.

Thank you for taking the time reading this.

Sincerely,

Adrian Kieß





-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account