Hi Jason,
I'd recommend giving a try with 118.
Thanks for the tip ! (and the testing). Worked fine with Win10:
Just a FYI, I've tested 118 solid on Win 10, 2012R2 and 2016 and haven't
had an issue with testing workloads.
Thanks for the report - good to know 2k12r2 is ok with
On 17 November 2016 at 06:49, Peter Grehan wrote:
> I'd recommend giving a try with 118.
>>
>
> Thanks for the tip ! (and the testing). Worked fine with Win10:
>
>
Just a FYI, I've tested 118 solid on Win 10, 2012R2 and 2016 and haven't
had an issue with testing workloads.
Cheers!
> https://f
I'd recommend giving a try with 118.
Thanks for the tip ! (and the testing). Worked fine with Win10:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-2/virtio-win-0.1.118.iso
later,
Peter.
___
f
Hi Peter,
Thanks for suggesting that! I re-installed the VM, this time using 0.1.96
instead of 0.1.126 and it worked as soon as I gave it static addressing. As
0.1.96 doesn't contain a driver specifically for Server 2016 I just used the
2012R2 one and I don't appear to have any issues.
Unfortu
On 11/15/2016 03:51 PM, Dustin Marquess wrote:
> If it's a bug, I don't believe it's in the virtio stack.
>
> I'm using Chelsio NICs on my bhyve servers, and I don't have to
> disable anything for my guests to work, I even have TOE enabled.
>
> -Dustin
>
>
Following is the bug i was referring to:
h
Peter,
I'd recommend giving a try with 118. I had a lot of trouble getting a Win16
image running. Ultimately, it was 118 and a lot of tries with deleting the
driver software and reinstalling from the virtio iso to get it to work.
I sent a a few emails last month as I was working through the issue
virtio-win-0.1.102.iso was the last version I've had any success with.
(I haven't tried with bhyve, only VirtualBox Windows VMs).
On 16 November 2016 at 08:43, Peter Grehan wrote:
> Hi Jonathan,
>
> In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows
>> 2k16/amd64 for my att
Hi Jonathan,
In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows
2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver
for Server 2012 R2.
I've not had any success with 0.1.126 - it installs, but doesn't
appear to pass packets. I'd recommend going with 0
If it's a bug, I don't believe it's in the virtio stack.
I'm using Chelsio NICs on my bhyve servers, and I don't have to
disable anything for my guests to work, I even have TOE enabled.
-Dustin
On Tue, Nov 15, 2016 at 6:07 AM, Rajil Saraswat wrote:
> On Nov 15, 2016 5:58 AM, wrote:
>>
>> Hello
Hi,
A good spot, my launch command doesn't include the virtio-win ISO that
contains the RedHat net-kvm driver. However, this is mostly just due to
a limitation in iohyve (or my understanding of it at least) in that it
can only mount a single CD at once.
I did in fact install the driver, by runnin
On Tue, Nov 15, 2016 at 11:58:29AM +, free...@jonathanprice.org wrote:
> Hello,
>
> I am trying to get a windows server VM running under bhyve. So far I can use
> VNC to install Windows, but I've been unable to get the networking working. I
> will provide details below, and include a summary
Hello, and thanks for the suggestion.
I ran the following:
sudo ifconfig em0 -rxcsum -txcsum -vlanmtu -vlanhwcsum -vlanhwtso -tso4
which resulted in ifconfig showing:
em0: flags=8843 metric 0 mtu 1500
options=2098
It looks like it removed rxcsum, txcsum, vlanhwtso and tso, but vlanhwcsum and
v
On Nov 15, 2016 5:58 AM, wrote:
>
> Hello,
>
> I am trying to get a windows server VM running under bhyve. So far I can
use VNC to install Windows, but I've been unable to get the networking
working. I will provide details below, and include a summary up here. On
the guest, I have installed the la
13 matches
Mail list logo