On Fri, 21 Dec 2018 at 22:05, Cherry G. Mathew wrote:
>
> On December 22, 2018 2:24:44 AM GMT+05:30, Chavdar Ivanov
> wrote:
> ...
> >
> >It is interesting also that when NetBSD is ran under XenServer (XCP-NG
> >actually) in PV mode, benchmarked against the same 8.99.28 version
> >running on a
On December 22, 2018 2:24:44 AM GMT+05:30, Chavdar Ivanov
wrote:
...
>
>It is interesting also that when NetBSD is ran under XenServer (XCP-NG
>actually) in PV mode, benchmarked against the same 8.99.28 version
>running on a physical machine, everything on a 1GB interface and
>switch, I get
I managed to build the VBox v6.0 additions under 8.99.28, now when
using vioif interface I get reasonable results:
...
PS C:\bin\iperf-3.1.3-win64> .\iperf3.exe -c marge
Connecting to host marge, port 5201
[ 4] local 192.168.0.35 port 10152 connected to 192.168.0.6 port 5201
[ ID] Interval
The workaround is fine. In the mean time I upgraded my VirtualBox
installation to 6.0 (released yesterday) and will check again.
While here I did some, admittedly not very scientific, benchmarks on
network performance under VirtualBox. I started a single guest of a
different type, had iperf3
On 2018/12/18 20:13, Masanobu SAITOH wrote:
Hi!
On 2018/12/17 19:38, Chavdar Ivanov wrote:
I went through a series of tests. It is indeed that point the panic
takes place, the two parts of the screendump are in
http://ci4ic4.tx0.org/nb-panic-wm-03.png and
Hi!
On 2018/12/17 19:38, Chavdar Ivanov wrote:
I went through a series of tests. It is indeed that point the panic
takes place, the two parts of the screendump are in
http://ci4ic4.tx0.org/nb-panic-wm-03.png and
http://ci4ic4.tx0.org/nb-panic-wm-04.png .
Thanks. This is the workaround code
I went through a series of tests. It is indeed that point the panic
takes place, the two parts of the screendump are in
http://ci4ic4.tx0.org/nb-panic-wm-03.png and
http://ci4ic4.tx0.org/nb-panic-wm-04.png .
VirtualBox gives three Intel NIC options:
Intel PRO/1000 MT Desktop (82540EM)
Intel
On 2018/12/17 1:09, Chavdar Ivanov wrote:
I have no idea. As I said, it is running under VirtualBox on a Windows
10 host; I put the host in hibernation whilst the NetBSD guest is
running.
I tested today's -current on VirtualBox 5.2.22 on Windows 7 64bit
(on Core i7-2600). I tried
I have no idea. As I said, it is running under VirtualBox on a Windows
10 host; I put the host in hibernation whilst the NetBSD guest is
running. Previously it survived this, using the Intel Desktop NIC
emulation within VirtualBox, even my ssh connections (from the host to
the guest) remained
Hi.
On 2018/12/16 18:09, Chavdar Ivanov wrote:
> Repeated this morning. Happens when the host hibernates when the
> machine is running. The initial trace is slightly different, but the
> lines with wm_gmii are the same, so for now I will switch to a
> different NIC emulator.
>
In your .png:
Repeated this morning. Happens when the host hibernates when the
machine is running. The initial trace is slightly different, but the
lines with wm_gmii are the same, so for now I will switch to a
different NIC emulator.
And yes, it used to survive many hibernations of the hosts before. I
only
On Sat, 15 Dec 2018, Chavdar Ivanov wrote:
Hi,
On 8.99.27 AMD64 running under VirtualBox I got this morning the panic
in http://ci4ic4.tx0.org/ci4ic4-panic-01.png
I have the coredump, if it is of interest. I thought it might be
useful, as it is apparently in the wm driver.
Oh, dear.
I
Hi,
On 8.99.27 AMD64 running under VirtualBox I got this morning the panic
in http://ci4ic4.tx0.org/ci4ic4-panic-01.png
I have the coredump, if it is of interest. I thought it might be
useful, as it is apparently in the wm driver.
Chavdar
--
13 matches
Mail list logo
