24:33 I remember in the early days of VMware virtualisation, VMware had some timer challenges, where you could see Windows VM clocks literally frozen, or ticking slowly, ticking only in big jumps and even ticking *_backwards!!!_* Oh and ticking really slowly with no mouse movement in RDP/console session and then suddenly ticking super fast when moving the mouse around fast in the RDP/console session! LOL Scheduled tasks would even fail to run, if the VM did not receive any sort of interrupts, like from mouse, keyboard or network traffic. It was crazy. Eventually VMware overcame these virtualised timer challenges and put out a white paper about it and the challenges of high quality virtualised timers. Those were some crazy times. It was a case of friends don't let friends virtualise NTP servers. LOL Virtualised NTP servers would literally oscillate erratically around realtime and their drift compensation would then amplify the problem, rather than reduce it, because the cause was not consistent.
Long story short: vmm/vmd are very hacky at the moment. A lot of work still need to be done so we can all have virtual machines running without problems on OpenBSD.
@@pasdenom.9062Rust can be written almost isomorphically to C with the default ownership rules which are more secure than C. Try learning a bit of Rust.
24:33 I remember in the early days of VMware virtualisation, VMware had some timer challenges, where you could see Windows VM clocks literally frozen, or ticking slowly, ticking only in big jumps and even ticking *_backwards!!!_* Oh and ticking really slowly with no mouse movement in RDP/console session and then suddenly ticking super fast when moving the mouse around fast in the RDP/console session! LOL
Scheduled tasks would even fail to run, if the VM did not receive any sort of interrupts, like from mouse, keyboard or network traffic. It was crazy.
Eventually VMware overcame these virtualised timer challenges and put out a white paper about it and the challenges of high quality virtualised timers. Those were some crazy times.
It was a case of friends don't let friends virtualise NTP servers. LOL Virtualised NTP servers would literally oscillate erratically around realtime and their drift compensation would then amplify the problem, rather than reduce it, because the cause was not consistent.
Long story short: vmm/vmd are very hacky at the moment. A lot of work still need to be done so we can all have virtual machines running without problems on OpenBSD.
Does BSD support vfio / gpu passthrough for Windows 10 in virtual machine?
@@brandonphilander661 I don't know, but you can easily read the source code.
The donations will help with the work that still needs to be done.
thanks for the talk Mischa!
any updates?
here ua-cam.com/video/OQCIy8INJig/v-deo.html
but you better know Dutch or use the autotranslator
Will openbsd ever be written in rust, haskell?
No.
Rust isn't as simple as C, and will lead to possible unknown security breaches.
Haskell has a garbage collector, forget it for system programming.
Certainly not!
@@pasdenom.9062Rust can be written almost isomorphically to C with the default ownership rules which are more secure than C. Try learning a bit of Rust.
Please fix that pkill stuff. "pkill -9 -f vm1" will kill far more vm:s than intended. -x comes to mind.
Left the talk after 30
Seconds because of This arrogant announcement in the beginning by the speaker
You gotta give it another try because he meant the guy who introduced him had written all the code he talked about.