Am 16.02.2019 um 05:11 schrieb Victor Sudakov:
Stefan Bethke wrote:
I was just worried that using ahci-hd instead of paravirtualized disks
causes suboptimal performance of guests. Do you think there is a hope to get
paravirtualized disks support for Windows guests in bhyve?
I was under the
Victor Sudakov wrote:
> > > Therefore I ask again if someone has an actual success story of running
> > > a Windows guest on a virtio-blk device.
> >
> > Hi Viktor
> >
> > Looking through my notes I'm not using virtio-blk I think, but I had
> > no issues with the specific driver version linked
On Sun, 24 Feb 2019, at 21:43, Victor Sudakov wrote:
> The guest installer says that there are no disks to install to and no
> drivers, and suggests a driver to be loaded. It can be told to find the
> appropriate driver in my virtio-win-0.1.141.iso CD:
>
> http://admin.sibptus.ru/~vas/bhyve1.png
Jason Tubnor 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 that in the
Jason Tubnor 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 that in the
> 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"
>
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
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:
>
>
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"
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
Stefan Bethke wrote:
> >
> > I was just worried that using ahci-hd instead of paravirtualized disks
> > causes suboptimal performance of guests. Do you think there is a hope to get
> > paravirtualized disks support for Windows guests in bhyve?
>
> I was under the impression that the Windows
LEASE for
>>>> the sake of nvme, is it useful for running FreeBSD, Linux (Mint,
>>>> Centos) and Windows10 guests?
>>>>
>>
>>
>> Or if you are using good SLOG and ARC for your VM zvols.
>>
>> I'm still sorting out some Windows iss
(Mint,
> > > Centos) and Windows10 guests?
> > >
>
>
> Or if you are using good SLOG and ARC for your VM zvols.
>
> I'm still sorting out some Windows issues with the bhyve nvme presentation
> for a variety of guest (except freebsd, that works fine) at the momen
ading from 11.2-RELEASE to 12.0-RELEASE for
> > > the sake of nvme, is it useful for running FreeBSD, Linux (Mint,
> > > Centos) and Windows10 guests?
> > >
>
>
> Or if you are using good SLOG and ARC for your VM zvols.
>
> I'm still sorting out some Windows issues with
Linux (Mint,
> > Centos) and Windows10 guests?
> >
Or if you are using good SLOG and ARC for your VM zvols.
I'm still sorting out some Windows issues with the bhyve nvme presentation
for a variety of guest (except freebsd, that works fine) at the moment. I
would avoid 12.0-RELEASE as it
If you have Nvme devices or you want store disks in ram yes, otherwise no.
BR,
On Tue, Feb 12, 2019, 9:05 PM Victor Sudakov Jason Tubnor wrote:
> >
> > > What's that disk0_type="nvme" thing?
> > >
> > > I'm curious. In 11.2-RELEASE there is not
Jason Tubnor wrote:
>
> > What's that disk0_type="nvme" thing?
> >
> > I'm curious. In 11.2-RELEASE there is nothing about nvme in bhyve(8).
> > Should I be running CURRENT or what?
> >
> >
> >
> It is valid on hosts 12.0-RELEASE and
On Tue, 12 Feb 2019 at 19:43, Victor Sudakov wrote:
> What's that disk0_type="nvme" thing?
>
> I'm curious. In 11.2-RELEASE there is nothing about nvme in bhyve(8).
> Should I be running CURRENT or what?
>
>
>
It is valid
What's that disk0_type="nvme" thing?
I'm curious. In 11.2-RELEASE there is nothing about nvme in bhyve(8).
Should I be running CURRENT or what?
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
signature.asc
Description: PGP signature
Hi,
yes its a typo but not relevant for the mentioned problem.
It just leads to not adding disk2.
Disk0 and the nvme get added to bhyve.
Only windows is unwilling to use nvme.
Greetings
...
Mike
On February 7, 2019 9:08:53 PM GMT+01:00, Yuri Pankov wrote:
>Michael Reifenberger wrote:
>> Hi,
Michael Reifenberger wrote:
> Hi,
> first I tried to install windows10 ltsc 2019 onto a nvme disk.
> This failed, the windows installer did not find a disk to install.
>
> Then I tried the following setup:
> ...
> disk0_type="ahci-hd"
> disk0_dev="zvol"
> disk0_name="disk0"
> disk1_type="nvme"
>
Michael Reifenberger wrote:
> Hi,
> first I tried to install windows10 ltsc 2019 onto a nvme disk.
> This failed, the windows installer did not find a disk to install.
>
> Then I tried the following setup:
> ...
> disk0_type="ahci-hd"
> disk0_dev="zvol"
> disk0_name="disk0"
> disk1_type="nvme"
>
Hi,
first I tried to install windows10 ltsc 2019 onto a nvme disk.
This failed, the windows installer did not find a disk to install.
Then I tried the following setup:
...
disk0_type="ahci-hd"
disk0_dev="zvol"
disk0_name="disk0"
disk1_type="nvme"
disk1_dev="zvol"
disk1_name="disk1"
23 matches
Mail list logo
