> On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote:
>
> >
> > Or at least please tell me how I can attach another iso image (with
> > drivers) when running "vm install myhost windows.iso"
>
>
> Technically, you should be able to define something like:
>
> disk1_type="ahci-cd"
> disk1_name="v
On Mon, 18 Feb 2019 at 12:09, Victor Sudakov wrote:
>
> Well, disk0 will be the guest HDD to install to, disk1 will be the ISO with
> drivers, and which disk will be the ISO attached by the "vm install"
> command?
>
>
From a user perspective, this is not of any value to know. vm-bhyve
manages t
Jason Tubnor wrote:
> On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote:
>
> >
> > Or at least please tell me how I can attach another iso image (with
> > drivers) when running "vm install myhost windows.iso"
>
>
> Technically, you should be able to define something like:
>
> disk1_type="ahci
On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote:
>
> Or at least please tell me how I can attach another iso image (with
> drivers) when running "vm install myhost windows.iso"
Technically, you should be able to define something like:
disk1_type="ahci-cd"
disk1_name="virtio-win-0.1.164.iso"
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 bhy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212782
Rodney W. Grimes changed:
What|Removed |Added
Flags||mfc-stable11+,
Victor Sudakov wrote:
>
> If anyone has been successful with viostor(?), please share your experience.
Or at least please tell me how I can attach another iso image (with
drivers) when running "vm install myhost windows.iso"
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://va
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215077
--- Comment #4 from Rodney W. Grimes ---
(In reply to Tsaukpaetra from comment #1)
I have WIP to fix that very issue, but first I had to fix several issues that
do not even allow us to go above 21 or 24 CPU's, corrections for that which
all
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 lik
Hi,
Does vtnet require iflib in the kernel?
thanks,
--
J.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebs
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
11 matches
Mail list logo