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 impr
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 to
Dave Cottlehuber wrote:
> 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:
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 back
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 back
> 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"
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
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 VirtI
> Am 15.02.2019 um 05:41 schrieb Victor Sudakov :
>
> Jason Tubnor wrote:
>>
>>> If you have Nvme devices or you want store disks in ram yes, otherwise no.
>>>
Is it worth it? I mean upgrading from 11.2-RELEASE to 12.0-RELEASE for
the sake of nvme, is it useful for running Fre
Jason Tubnor wrote:
>
> > If you have Nvme devices or you want store disks in ram yes, otherwise no.
> >
> > >
> > > Is it worth it? I mean upgrading 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?
> >
On Wed, Feb 13, 2019 at 07:50:32AM +1100, Jason Tubnor wrote:
> On Wed, 13 Feb 2019 at 00:57, Marcelo Araujo
> wrote:
>
> > If you have Nvme devices or you want store disks in ram yes, otherwise no.
> >
> > >
> > > Is it worth it? I mean upgrading from 11.2-RELEASE to 12.0-RELEASE for
> > > the s
On Wed, 13 Feb 2019 at 00:57, Marcelo Araujo
wrote:
> If you have Nvme devices or you want store disks in ram yes, otherwise no.
>
> >
> > Is it worth it? I mean upgrading from 11.2-RELEASE to 12.0-RELEASE for
> > the sake of nvme, is it useful for running FreeBSD, Linux (Mint,
> > Centos) and Wi
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 nothing about nvme in bhyve(8).
> > > Should I be runni
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 newer.
Is it worth it? I mean upgrading from 11.2-RELEASE to 12
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 on hosts 12.0-RELEASE and newer.
__
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"
> d
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"
> d
23 matches
Mail list logo