[Info-vax] clock problems with OpenVMS x86 on VirtualBox

gah4 gah4 at u.washington.edu
Wed May 17 04:46:24 EDT 2023


On Monday, May 15, 2023 at 7:14:08 AM UTC-7, Dan Cross wrote:

(snip)

> And separately there are issues of IO: in a type-1 scenario, IO 
> is offloaded to another VM (or even a separate system) on behalf 
> of a guest; that introduces non-determinate latency and 
> noisy-neighbor problems without careful construction. Even with 
> SR-IOV and passthru techniques for hypervisor-bypass, there are 
> classes of IO that must go through the host, and these can take 
> arbitrarily long. What do you do when the `outb` to your 
> virtualized console UART blocks? There are some techniques to 
> amortize the overhead of these events (posted IOs, for example) 
> but they are not perfect. 
 
(snip)

and then there is NFS, where I/O can take arbitrarily long, even
without a hypervisor.  

I once sold a machine that clients had NFS mounts from. 
That is, hard mounts.



More information about the Info-vax mailing list