NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port-amd64/57266: Poor disk performance on VirtualBox vioscsi0 and NetBSD 10.0_BETA



The following reply was made to PR port-amd64/57266; it has been noted by GNATS.

From: Bartek Krawczyk <bbartlomiej.mail%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, port-amd64-maintainer%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-amd64/57266: Poor disk performance on VirtualBox vioscsi0
 and NetBSD 10.0_BETA
Date: Tue, 14 Mar 2023 00:13:26 +0100

 On 13/03/2023 20:40, Michael van Elst wrote:
 > The following reply was made to PR port-amd64/57266; it has been noted by GNATS.
 > 
 > From: mlelstv%serpens.de@localhost (Michael van Elst)
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: port-amd64/57266: Poor disk performance on VirtualBox vioscsi0 and NetBSD 10.0_BETA
 > Date: Mon, 13 Mar 2023 19:34:14 -0000 (UTC)
 > 
 >   bbartlomiej.mail%gmail.com@localhost (Bartek Krawczyk) writes:
 >   
 >   >Also even downloading (virtio net driver) is much faster: 7MB/s vs
 >   >0,5MB/s on NetBSD but that is aprobably again constrained by slow disk I/O.
 >   
 >   I get about 7MB/s download, 25MB/s write to disk and finishing the untar
 >   task in 960 seconds. That's not virtualbox but qemu emulating
 >   an aarch64 CPU and which is completely CPU bound on the host (a 8 years
 >   old Xeon with SSD).
 >   
 >   N.B. the guest filesystem is mounted only with noatime option.
 >   
 >   So there must be something special with virtualbox.
 >   
 
 Indeed there was, but not with VirtualBox but with Windows 11.
 Windows has Hyper-V tightly integrated nowadays and a lot of security 
 features are based on that.
 
 For others trying to run a NetBSD VM in Windows 10/11:
 1. Remove WSL2
 2. If you're using Pro or Enterprise edition, remove Hyper-V (Home 
 edition doesn't have it as a separate feature).
 3. In system Settings > Device Security > Core Isolation disable Memory 
 Integrity.
 These steps should disable or limit Hyper-V influence.
 
 This will allow VirtualBox and other hypervisors to fully utilize your 
 hardware. With Hyper-V running in the background, your other hypervisor 
 will fallback to slower mode (for instance a turtle icon in VirtualBox).
 
 Now unpacking pkgsrc takes 3,5 minutes instead of 25-30 and "iostat dk0" 
 shows more than 1.5MB/s while doing that.
 
 Thanks all for help!
 -- 
 Regards
 Bartek Krawczyk
 


Home | Main Index | Thread Index | Old Index