Re: Windows 2019 server

2019-04-13 Thread Victor Sudakov
Victor Sudakov wrote:
> 
> I've just installed "Windows Server 2016" on 11.2-RELEASE-p9 and it is very
> slow.  Windows 2012 R2 ran much faster AFAIR.
> 
> I don't think this is the ahci-hd issue because the Novabench Windows
> benchmark in the guest VM shows read and write speeds over 1 GB/s, isn't
> it more than enough?

And an attempt to install Windows Server 2016 to a virtio-blk device (guest
driver taken from virtio-win-0.1.141.iso) still craches the guest as soon
as the guest tries to access the disk: "bhyve exited with status 134".

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Re: Windows 2019 server

2019-04-12 Thread Dustin Marquess
Indeed!

As for the other two... the virtio-rnd I pass through to all of my
capable VMs, as VMs usually have a tougher time to collect entropy, so
I figure it can't hurt.  The PCI passthrough I just forgot to remove
from my example before I sent it.  I have a dual-port 16C950 PCIe card
that I passthrough to Windows to run u-blox u-center :).

-Dustin

On Fri, Apr 12, 2019 at 9:57 AM Rodney W. Grimes
 wrote:
>
> > On Thu, Apr 11, 2019 at 10:10:03PM -0500, Dustin Marquess wrote:
> > > It's worth a shot at least to see if it works!
> > >
> > > But ya, basically the same as mine:
> > >
> > > bhyve -A -H -P -w -S -u -c sockets=1,cores=4,threads=2 -m ${RAM} \
> > > -s 0,hostbridge \
> > > -s 3,nvme,/dev/zvol/tank/vm/win2019 \
> > > -s 4,ahci-cd,${VMROOT}/win2019/empty.iso,nocache,ro \
> > > -s 5,passthru,130/0/0 \
> > > -s 10,virtio-net,tap2 \
> > > -s 20,virtio-rnd \
> > > -s 31,lpc \
> > > -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd 
> > > ${VM}
> > >
> > > -Dustin
> >
> > I will try a bit of a mix.  Also  Do the same for the Linux emulations
> > such as Scientific, Fedora, Centos, Debian and Ubuntu and ORacle?
> >
> > BTW  rational for the -w , your -c content your passthru and the virtio-rnd?
>
> The -c context is done most likely for license reasons,
> without specifying topology the default for -c 8 would
> be 8 sockets of 1 core of 1 thread, that would require
> a high end server win2019 license.  By building this
> as a 8 threads in a single socket you get to use a
> single socket windows license.  This is one of the major
> reasons that I added the complex topology specification
> to the -c option.
>
> > > On Thu, Apr 11, 2019 at 5:54 PM The Doctor  
> > > wrote:
> > > >
> > > > On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> > > > > I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
> > > > > to run MUCH faster when using nvme compared to ahci-hd.
> > > > >
> > > > > -Dustin
> > > > >
> > > >
> > > > Here is the script I use to start the Windows server
> > > >
> > > >
> > > > #!/bin/sh
> > > > bhyve -c 4 -s 0,hostbridge -s 3,ahci-hd,/usr/vm/images/windows2019st  
> > > > -s 10,virtio-net,tap3 -s 31,lpc -l com1,/dev/nmdm9A -l 
> > > > com2,/dev/nmdm10A -s 29,fbuf,tcp=0.0.0.0:5958,w=1024,h=768,wait -l 
> > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 4G -H -w 
> > > > windows2019st &
> > > >
> > > > So I should change ahci-cd to nvme?
> > > >
> > > >
> > > > > On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
> > > > >  wrote:
> > > > > >
> > > > > > Seems to be running slow on FreeBSD 12.0 p3.
> > > > > >
> > > > > > Just wondering if there are known issues.
> > > > > > --
> > > > > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > > > > doctor@@nl2k.ab.ca
> > > > > > Yahweh, Queen & country!Never Satan President Republic!Beware 
> > > > > > AntiChrist rising!
> > > > > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 
> > > > > > on Atheism
> > > > > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > > > > > ___
> > > > > > freebsd-virtualization@freebsd.org mailing list
> > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > > > > > To unsubscribe, send any mail to 
> > > > > > "freebsd-virtualization-unsubscr...@freebsd.org"
> > > >
> > > > --
> > > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > > doctor@@nl2k.ab.ca
> > > > Yahweh, Queen & country!Never Satan President Republic!Beware 
> > > > AntiChrist rising!
> > > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > > > Atheism
> > > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> >
> > --
> > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > doctor@@nl2k.ab.ca
> > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> > rising!
> > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > Atheism
> > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > ___
> > freebsd-virtualization@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to 
> > "freebsd-virtualization-unsubscr...@freebsd.org"
> >
>
> --
> Rod Grimes rgri...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-12 Thread Rodney W. Grimes
> On Thu, Apr 11, 2019 at 10:10:03PM -0500, Dustin Marquess wrote:
> > It's worth a shot at least to see if it works!
> > 
> > But ya, basically the same as mine:
> > 
> > bhyve -A -H -P -w -S -u -c sockets=1,cores=4,threads=2 -m ${RAM} \
> > -s 0,hostbridge \
> > -s 3,nvme,/dev/zvol/tank/vm/win2019 \
> > -s 4,ahci-cd,${VMROOT}/win2019/empty.iso,nocache,ro \
> > -s 5,passthru,130/0/0 \
> > -s 10,virtio-net,tap2 \
> > -s 20,virtio-rnd \
> > -s 31,lpc \
> > -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd ${VM}
> > 
> > -Dustin
> 
> I will try a bit of a mix.  Also  Do the same for the Linux emulations 
> such as Scientific, Fedora, Centos, Debian and Ubuntu and ORacle?
> 
> BTW  rational for the -w , your -c content your passthru and the virtio-rnd?

The -c context is done most likely for license reasons,
without specifying topology the default for -c 8 would
be 8 sockets of 1 core of 1 thread, that would require
a high end server win2019 license.  By building this
as a 8 threads in a single socket you get to use a
single socket windows license.  This is one of the major
reasons that I added the complex topology specification
to the -c option.

> > On Thu, Apr 11, 2019 at 5:54 PM The Doctor  wrote:
> > >
> > > On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> > > > I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
> > > > to run MUCH faster when using nvme compared to ahci-hd.
> > > >
> > > > -Dustin
> > > >
> > >
> > > Here is the script I use to start the Windows server
> > >
> > >
> > > #!/bin/sh
> > > bhyve -c 4 -s 0,hostbridge -s 3,ahci-hd,/usr/vm/images/windows2019st  -s 
> > > 10,virtio-net,tap3 -s 31,lpc -l com1,/dev/nmdm9A -l com2,/dev/nmdm10A -s 
> > > 29,fbuf,tcp=0.0.0.0:5958,w=1024,h=768,wait -l 
> > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 4G -H -w 
> > > windows2019st &
> > >
> > > So I should change ahci-cd to nvme?
> > >
> > >
> > > > On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
> > > >  wrote:
> > > > >
> > > > > Seems to be running slow on FreeBSD 12.0 p3.
> > > > >
> > > > > Just wondering if there are known issues.
> > > > > --
> > > > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > > > doctor@@nl2k.ab.ca
> > > > > Yahweh, Queen & country!Never Satan President Republic!Beware 
> > > > > AntiChrist rising!
> > > > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 
> > > > > on Atheism
> > > > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > > > > ___
> > > > > freebsd-virtualization@freebsd.org mailing list
> > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > > > > To unsubscribe, send any mail to 
> > > > > "freebsd-virtualization-unsubscr...@freebsd.org"
> > >
> > > --
> > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > doctor@@nl2k.ab.ca
> > > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> > > rising!
> > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > > Atheism
> > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> 
> -- 
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> doctor@@nl2k.ab.ca
> Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> rising!
> https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
> Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
> 

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-12 Thread The Doctor via freebsd-virtualization
On Thu, Apr 11, 2019 at 10:10:03PM -0500, Dustin Marquess wrote:
> It's worth a shot at least to see if it works!
> 
> But ya, basically the same as mine:
> 
> bhyve -A -H -P -w -S -u -c sockets=1,cores=4,threads=2 -m ${RAM} \
> -s 0,hostbridge \
> -s 3,nvme,/dev/zvol/tank/vm/win2019 \
> -s 4,ahci-cd,${VMROOT}/win2019/empty.iso,nocache,ro \
> -s 5,passthru,130/0/0 \
> -s 10,virtio-net,tap2 \
> -s 20,virtio-rnd \
> -s 31,lpc \
> -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd ${VM}
> 
> -Dustin

I will try a bit of a mix.  Also  Do the same for the Linux emulations 
such as Scientific, Fedora, Centos, Debian and Ubuntu and ORacle?

BTW  rational for the -w , your -c content your passthru and the virtio-rnd?

> 
> On Thu, Apr 11, 2019 at 5:54 PM The Doctor  wrote:
> >
> > On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> > > I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
> > > to run MUCH faster when using nvme compared to ahci-hd.
> > >
> > > -Dustin
> > >
> >
> > Here is the script I use to start the Windows server
> >
> >
> > #!/bin/sh
> > bhyve -c 4 -s 0,hostbridge -s 3,ahci-hd,/usr/vm/images/windows2019st  -s 
> > 10,virtio-net,tap3 -s 31,lpc -l com1,/dev/nmdm9A -l com2,/dev/nmdm10A -s 
> > 29,fbuf,tcp=0.0.0.0:5958,w=1024,h=768,wait -l 
> > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 4G -H -w 
> > windows2019st &
> >
> > So I should change ahci-cd to nvme?
> >
> >
> > > On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
> > >  wrote:
> > > >
> > > > Seems to be running slow on FreeBSD 12.0 p3.
> > > >
> > > > Just wondering if there are known issues.
> > > > --
> > > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > > doctor@@nl2k.ab.ca
> > > > Yahweh, Queen & country!Never Satan President Republic!Beware 
> > > > AntiChrist rising!
> > > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > > > Atheism
> > > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > > > ___
> > > > freebsd-virtualization@freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > > > To unsubscribe, send any mail to 
> > > > "freebsd-virtualization-unsubscr...@freebsd.org"
> >
> > --
> > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > doctor@@nl2k.ab.ca
> > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> > rising!
> > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > Atheism
> > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-12 Thread Victor Sudakov
The Doctor via freebsd-virtualization wrote:
> Seems to be running slow on FreeBSD 12.0 p3.
> 
> Just wondering if there are known issues.

I've just installed "Windows Server 2016" on 11.2-RELEASE-p9 and it is very
slow.  Windows 2012 R2 ran much faster AFAIR.

I don't think this is the ahci-hd issue because the Novabench Windows
benchmark in the guest VM shows read and write speeds over 1 GB/s, isn't
it more than enough?


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Re: Windows 2019 server

2019-04-11 Thread Dustin Marquess
It's worth a shot at least to see if it works!

But ya, basically the same as mine:

bhyve -A -H -P -w -S -u -c sockets=1,cores=4,threads=2 -m ${RAM} \
-s 0,hostbridge \
-s 3,nvme,/dev/zvol/tank/vm/win2019 \
-s 4,ahci-cd,${VMROOT}/win2019/empty.iso,nocache,ro \
-s 5,passthru,130/0/0 \
-s 10,virtio-net,tap2 \
-s 20,virtio-rnd \
-s 31,lpc \
-l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd ${VM}

-Dustin

On Thu, Apr 11, 2019 at 5:54 PM The Doctor  wrote:
>
> On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> > I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
> > to run MUCH faster when using nvme compared to ahci-hd.
> >
> > -Dustin
> >
>
> Here is the script I use to start the Windows server
>
>
> #!/bin/sh
> bhyve -c 4 -s 0,hostbridge -s 3,ahci-hd,/usr/vm/images/windows2019st  -s 
> 10,virtio-net,tap3 -s 31,lpc -l com1,/dev/nmdm9A -l com2,/dev/nmdm10A -s 
> 29,fbuf,tcp=0.0.0.0:5958,w=1024,h=768,wait -l 
> bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 4G -H -w 
> windows2019st &
>
> So I should change ahci-cd to nvme?
>
>
> > On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
> >  wrote:
> > >
> > > Seems to be running slow on FreeBSD 12.0 p3.
> > >
> > > Just wondering if there are known issues.
> > > --
> > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > > doctor@@nl2k.ab.ca
> > > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> > > rising!
> > > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > > Atheism
> > > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > > ___
> > > freebsd-virtualization@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > > To unsubscribe, send any mail to 
> > > "freebsd-virtualization-unsubscr...@freebsd.org"
>
> --
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> doctor@@nl2k.ab.ca
> Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> rising!
> https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
> Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-11 Thread The Doctor via freebsd-virtualization
On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
> to run MUCH faster when using nvme compared to ahci-hd.
> 
> -Dustin
>

Here is the script I use to start the Windows server


#!/bin/sh
bhyve -c 4 -s 0,hostbridge -s 3,ahci-hd,/usr/vm/images/windows2019st  -s 
10,virtio-net,tap3 -s 31,lpc -l com1,/dev/nmdm9A -l com2,/dev/nmdm10A -s 
29,fbuf,tcp=0.0.0.0:5958,w=1024,h=768,wait -l 
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 4G -H -w windows2019st &

So I should change ahci-cd to nvme?


> On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
>  wrote:
> >
> > Seems to be running slow on FreeBSD 12.0 p3.
> >
> > Just wondering if there are known issues.
> > --
> > Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> > doctor@@nl2k.ab.ca
> > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> > rising!
> > https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
> > Atheism
> > Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> > ___
> > freebsd-virtualization@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to 
> > "freebsd-virtualization-unsubscr...@freebsd.org"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-11 Thread Dustin Marquess
I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
to run MUCH faster when using nvme compared to ahci-hd.

-Dustin

On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
 wrote:
>
> Seems to be running slow on FreeBSD 12.0 p3.
>
> Just wondering if there are known issues.
> --
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> doctor@@nl2k.ab.ca
> Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> rising!
> https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
> Alberta on 16 April 2019, do not vote UCP, FCP nor NDP!
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-03 Thread Jason Tubnor
On Wed, 3 Apr 2019 at 19:57, Michael Reifenberger 
wrote:

> Hi,
> do you mean:
> https://reviews.freebsd.org/D19695
> if yes I can confirm that with the patch I get ltsc-2019 installed and
> running.


Yes, that is the patch.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-03 Thread Michael Reifenberger

Hi,
do you mean:
https://reviews.freebsd.org/D19695
if yes I can confirm that with the patch I get ltsc-2019 installed and  
running.


Greetings
---
mike

Zitat von Jason Tubnor :


On Wed, 3 Apr 2019 at 01:56, Nick Wolff  wrote:



specific virt-io drivers for windows I'm not sure if that is fixed now. I
think nvme paravirtual might also just work with windows but haven't
confirmed that lately.



Initial testing with some out of tree patches has fixed issues with NVMe
and Windows, current snaps/stable don't work with Windows and NVMe.

They should be imported shortly.

Cheers



On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov  wrote:

> Jason Tubnor wrote:
> >
> > > Which kind of storage did you present to the Windows 2019 guest,
> > > paravirtualized or ahcd-hd ?
> >
> > ahci-hd is what you want with bhyve and uefi
>
> Still no paravirtualized disks support for Windows guests, even in
> FreeBSD 12? How sad.
>
> --
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> 2:5005/49@fidonet http://vas.tomsk.ru/
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to "
freebsd-virtualization-unsubscr...@freebsd.org"




--
"If my calculations are correct, when this baby hits 88MPH, you're gonna to
see some serious shit" - Emmett "Doc" Brown
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to  
"freebsd-virtualization-unsubscr...@freebsd.org"




Gruß
---
Michael Reifenberger

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-03 Thread Michael Reifenberger

Hi,

Zitat von Nick Wolff :


Micheal,

Would you mind trying with
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-1/


That is the iso I've used in the past with newer drivers failing(I don't
think it caused a panic though when I dealt with it)



Trying to use this ISO for loading the driver during the installation  
doesn't lead to a panic

but aborts the guest while the driver gets loaded:

Apr. 03 10:11:11: initialising
Apr. 03 10:11:11:  [loader: uefi]
Apr. 03 10:11:11:  [cpu: 2]
Apr. 03 10:11:11:  [memory: 6G]
Apr. 03 10:11:11:  [hostbridge: standard]
Apr. 03 10:11:11:  [com ports: com1]
Apr. 03 10:11:11:  [uuid: a9656f03-7f7a-11e7-983e-98e7f4868540]
Apr. 03 10:11:11:  [utctime: yes]
Apr. 03 10:11:11:  [debug mode: no]
Apr. 03 10:11:11:  [primary disk: disk0]
Apr. 03 10:11:11:  [primary disk dev: zvol]
Apr. 03 10:11:11: initialising network device tap0
Apr. 03 10:11:11: adding tap0 -> bridge1 (private addm)
Apr. 03 10:11:11: bring up tap0 -> bridge1 (private addm)
Apr. 03 10:11:11: booting
Apr. 03 10:11:11:  [bhyve options: -c 2 -m 6G -Hwl  
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U  
a9656f03-7f7a-11e7-983e-98e7f4868540 -u]
Apr. 03 10:11:11:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s  
4:0,virtio-blk,/dev/zvol/zdata/VM/w10e-ltsb-2/disk0 -s  
5:0,nvme,/dev/zvol/zdata/VM/w10e-ltsb-2/disk1 -s  
6:0,ahci-cd,/VM2/w10e-ltsb-2/disk2.img -s  
7:0,virtio-net,tap0,mac=58:9c:fc:04:eb:ed -s  
8:0,fbuf,tcp=0.0.0.0:5900,w=1600,h=900 -s 9:0,xhci,tablet]

Apr. 03 10:11:11:  [bhyve console: -l com1,/dev/nmdm-w10e-ltsb-2.1A]
Apr. 03 10:11:11:  [bhyve iso device: -s  
3:0,ahci-cd,/VM/.iso/en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso,ro]

Apr. 03 10:11:11: starting bhyve (run 1)
Apr. 03 10:13:10: bhyve exited with status 134
Apr. 03 10:13:10: destroying network device tap0
Apr. 03 10:13:10: stopped

The relevant entries of the config file are:

...
cpu=2
memory=6G
network0_type="virtio-net"
network0_switch="private"
disk0_type="virtio-blk"
disk0_dev="zvol"
disk0_name="disk0"
disk1_type="nvme"
disk1_dev="zvol"
disk1_name="disk1"
disk2_type="ahci-cd"
disk2_name="disk2.img"
...

(disk0 is the one I'm trying to use here, disk2 is the ISO)

Greetings
---
mike

Gruß
---
Michael Reifenberger

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-02 Thread Jason Tubnor
On Wed, 3 Apr 2019 at 01:56, Nick Wolff  wrote:

>
> specific virt-io drivers for windows I'm not sure if that is fixed now. I
> think nvme paravirtual might also just work with windows but haven't
> confirmed that lately.
>
>
Initial testing with some out of tree patches has fixed issues with NVMe
and Windows, current snaps/stable don't work with Windows and NVMe.

They should be imported shortly.

Cheers


> On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov  wrote:
>
> > Jason Tubnor wrote:
> > >
> > > > Which kind of storage did you present to the Windows 2019 guest,
> > > > paravirtualized or ahcd-hd ?
> > >
> > > ahci-hd is what you want with bhyve and uefi
> >
> > Still no paravirtualized disks support for Windows guests, even in
> > FreeBSD 12? How sad.
> >
> > --
> > Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> > 2:5005/49@fidonet http://vas.tomsk.ru/
> >
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>


-- 
"If my calculations are correct, when this baby hits 88MPH, you're gonna to
see some serious shit" - Emmett "Doc" Brown
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-02 Thread Nick Wolff
Micheal,

Would you mind trying with
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-1/


That is the iso I've used in the past with newer drivers failing(I don't
think it caused a panic though when I dealt with it)

Thanks,

Nick Wolff

On Tue, Apr 2, 2019 at 12:24 PM Jason Barbier  wrote:

> happen to catch a stack trace for the crash?
>
> ---
> Jason Barbier | E: ja...@corrupted.io
> GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya)
>
> On Tue, Apr 2, 2019, at 9:05 AM, Michael wrote:
> > Hi,
> > I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the
> > virtstor driver.
> >
> >
> > Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff <
> darkfiber...@gmail.com>:
> > >There is paravirtulized support in FreeBSD 11.2 and 12 but you need to
> > >sideload the virtio drivers into windows. Sadly microsoft doesn't ship
> > >with
> > >them even with how "cloud" focused they are. Ahci-hd will allow you to
> > >get
> > >around this. I know we had some restrictions in the past on needing
> > >specific virt-io drivers for windows I'm not sure if that is fixed now.
> > >I
> > >think nvme paravirtual might also just work with windows but haven't
> > >confirmed that lately.
> > >
> > >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov 
> > >wrote:
> > >
> > >> Jason Tubnor wrote:
> > >> >
> > >> > > Which kind of storage did you present to the Windows 2019 guest,
> > >> > > paravirtualized or ahcd-hd ?
> > >> >
> > >> > ahci-hd is what you want with bhyve and uefi
> > >>
> > >> Still no paravirtualized disks support for Windows guests, even in
> > >> FreeBSD 12? How sad.
> > >>
> > >> --
> > >> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> > >> 2:5005/49@fidonet http://vas.tomsk.ru/
> > >>
> > >___
> > >freebsd-virtualization@freebsd.org mailing list
> > >https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > >To unsubscribe, send any mail to
> > >"freebsd-virtualization-unsubscr...@freebsd.org"
> >
> > Gruß
> > ---
> > Michael
> > ___
> > freebsd-virtualization@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to
> > "freebsd-virtualization-unsubscr...@freebsd.org"
> >
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org"
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-02 Thread Jason Barbier
happen to catch a stack trace for the crash?

---
Jason Barbier | E: ja...@corrupted.io 
GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya)

On Tue, Apr 2, 2019, at 9:05 AM, Michael wrote:
> Hi,
> I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the 
> virtstor driver.
> 
> 
> Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff :
> >There is paravirtulized support in FreeBSD 11.2 and 12 but you need to
> >sideload the virtio drivers into windows. Sadly microsoft doesn't ship
> >with
> >them even with how "cloud" focused they are. Ahci-hd will allow you to
> >get
> >around this. I know we had some restrictions in the past on needing
> >specific virt-io drivers for windows I'm not sure if that is fixed now.
> >I
> >think nvme paravirtual might also just work with windows but haven't
> >confirmed that lately.
> >
> >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov 
> >wrote:
> >
> >> Jason Tubnor wrote:
> >> >
> >> > > Which kind of storage did you present to the Windows 2019 guest,
> >> > > paravirtualized or ahcd-hd ?
> >> >
> >> > ahci-hd is what you want with bhyve and uefi
> >>
> >> Still no paravirtualized disks support for Windows guests, even in
> >> FreeBSD 12? How sad.
> >>
> >> --
> >> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> >> 2:5005/49@fidonet http://vas.tomsk.ru/
> >>
> >___
> >freebsd-virtualization@freebsd.org mailing list
> >https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> >To unsubscribe, send any mail to
> >"freebsd-virtualization-unsubscr...@freebsd.org"
> 
> Gruß
> --- 
> Michael
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-02 Thread Michael
Hi,
I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the 
virtstor driver.


Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff :
>There is paravirtulized support in FreeBSD 11.2 and 12 but you need to
>sideload the virtio drivers into windows. Sadly microsoft doesn't ship
>with
>them even with how "cloud" focused they are. Ahci-hd will allow you to
>get
>around this. I know we had some restrictions in the past on needing
>specific virt-io drivers for windows I'm not sure if that is fixed now.
>I
>think nvme paravirtual might also just work with windows but haven't
>confirmed that lately.
>
>On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov 
>wrote:
>
>> Jason Tubnor wrote:
>> >
>> > > Which kind of storage did you present to the Windows 2019 guest,
>> > > paravirtualized or ahcd-hd ?
>> >
>> > ahci-hd is what you want with bhyve and uefi
>>
>> Still no paravirtualized disks support for Windows guests, even in
>> FreeBSD 12? How sad.
>>
>> --
>> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
>> 2:5005/49@fidonet http://vas.tomsk.ru/
>>
>___
>freebsd-virtualization@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>To unsubscribe, send any mail to
>"freebsd-virtualization-unsubscr...@freebsd.org"

Gruß
--- 
Michael
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-04-02 Thread Nick Wolff
There is paravirtulized support in FreeBSD 11.2 and 12 but you need to
sideload the virtio drivers into windows. Sadly microsoft doesn't ship with
them even with how "cloud" focused they are. Ahci-hd will allow you to get
around this. I know we had some restrictions in the past on needing
specific virt-io drivers for windows I'm not sure if that is fixed now. I
think nvme paravirtual might also just work with windows but haven't
confirmed that lately.

On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov  wrote:

> Jason Tubnor wrote:
> >
> > > Which kind of storage did you present to the Windows 2019 guest,
> > > paravirtualized or ahcd-hd ?
> >
> > ahci-hd is what you want with bhyve and uefi
>
> Still no paravirtualized disks support for Windows guests, even in
> FreeBSD 12? How sad.
>
> --
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> 2:5005/49@fidonet http://vas.tomsk.ru/
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-03-03 Thread Jason Tubnor
On Sat., 2 Mar. 2019, 8:48 pm Victor S


Which kind of storage did you present to the Windows 2019 guest,
paravirtualized or ahcd-hd ?




ahci-hd is what you want with bhyve and uefi

Cheers
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-03-03 Thread Victor Sudakov
Jason Tubnor wrote:
> 
> > Which kind of storage did you present to the Windows 2019 guest,
> > paravirtualized or ahcd-hd ?
> 
> ahci-hd is what you want with bhyve and uefi

Still no paravirtualized disks support for Windows guests, even in
FreeBSD 12? How sad.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Re: Windows 2019 server

2019-03-03 Thread Jason Tubnor
On Sun., 3 Mar. 2019, 12:06 pm The Doctor via freebsd-virtualization, <
freebsd-virtualization@freebsd.org> wrote:

>
>
> I was able to install in bhyve FreeBSD 11.2 hoever, the ethernet Driver
> is not picking up.
>
> hints please.
>

Once you are installed, boot again with the virtio cd on an ahci-cd device,
go to devices and you'll see the unknown adaptor, update the driver using
the virtio-net ones on the CD. You should be good after that. 2k16 drivers
work with 19.

Cheers

>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-03-02 Thread The Doctor via freebsd-virtualization
On Sat, Mar 02, 2019 at 04:48:29PM +0700, Victor Sudakov wrote:
> Florian Smeets via freebsd-virtualization wrote:
> > On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote:
> > > Anyone got Windows 2019 server running in bhyve ?
> > > 
> > 
> > Yes, on stable/12 (r343339) using
> > https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a
> > charm.
> 
> Which kind of storage did you present to the Windows 2019 guest,
> paravirtualized or ahcd-hd ?
> 

I was able to install in bhyve FreeBSD 11.2 hoever, the ethernet Driver 
is not picking up.

hints please.


-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Be charitable before wealth makes thee covetous.  -Sir Thomas Browne
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-03-02 Thread Victor Sudakov
Florian Smeets via freebsd-virtualization wrote:
> On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote:
> > Anyone got Windows 2019 server running in bhyve ?
> > 
> 
> Yes, on stable/12 (r343339) using
> https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a
> charm.

Which kind of storage did you present to the Windows 2019 guest,
paravirtualized or ahcd-hd ?




-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Re: Windows 2019 server

2019-02-17 Thread Jason Tubnor
On Sun, 17 Feb 2019 at 23:35, The Doctor via freebsd-virtualization <
freebsd-virtualization@freebsd.org> wrote:

> On Sun, Feb 17, 2019 at 08:31:58AM +0100, Florian Smeets wrote:
> > On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote:
> > > Anyone got Windows 2019 server running in bhyve ?
> > >
> >
> > Yes, on stable/12 (r343339) using
> > https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a
> > charm.
> >
>
> I am on FreeBSD 11.2 FYI
>
>
>
Yes, on 11.2 using ahci-hd storage presentation to the installer and UEFI
boot.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-02-17 Thread The Doctor via freebsd-virtualization
On Sun, Feb 17, 2019 at 08:31:58AM +0100, Florian Smeets wrote:
> On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote:
> > Anyone got Windows 2019 server running in bhyve ?
> > 
> 
> Yes, on stable/12 (r343339) using
> https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a
> charm.
>

I am on FreeBSD 11.2 FYI

> Florian
> 




-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Do not consider painful what is good for you.  -Euripides
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Windows 2019 server

2019-02-17 Thread Florian Smeets via freebsd-virtualization
On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote:
> Anyone got Windows 2019 server running in bhyve ?
> 

Yes, on stable/12 (r343339) using
https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a
charm.

Florian



signature.asc
Description: OpenPGP digital signature