Displaying 3 results from an estimated 3 matches for "562f055".
Did you mean:
5621055
2023 Mar 02
1
[V2V PATCH 0/5] Bring support for virtio-scsi back to Windows
...The parameter can be one of:
ISO The path to the ISO image containing the virtio-win drivers
(eg. /usr/share/virtio-win/virtio-win.iso).
[etc]
> > diff --git a/mlcustomize/inject_virtio_win.ml b/mlcustomize/inject_virtio_win.ml
> > index 62f7710..562f055 100644
> > --- a/mlcustomize/inject_virtio_win.ml
> > +++ b/mlcustomize/inject_virtio_win.ml
> > @@ -177,6 +177,11 @@ let rec inject_virtio_win_drivers ({ g } as t) reg =
> > (* Can we install the block driver? *)
> > let block : block_type =
> >...
2023 Mar 02
1
[V2V PATCH 0/5] Bring support for virtio-scsi back to Windows
...eing used by
v2v as well (for instance, for setting the tools ISO location). So what
if we introduce an env variable here instead? I presume it would be
much easier to implement. Smth like:
> diff --git a/mlcustomize/inject_virtio_win.ml b/mlcustomize/inject_virtio_win.ml
> index 62f7710..562f055 100644
> --- a/mlcustomize/inject_virtio_win.ml
> +++ b/mlcustomize/inject_virtio_win.ml
> @@ -177,6 +177,11 @@ let rec inject_virtio_win_drivers ({ g } as t) reg =
> (* Can we install the block driver? *)
> let block : block_type =
> let filenames = ["virtio...
2023 Mar 02
1
[V2V PATCH 0/5] Bring support for virtio-scsi back to Windows
On Thu, Mar 02, 2023 at 08:15:37PM +0200, Andrey Drobyshev wrote:
> On 2/28/23 16:39, Richard W.M. Jones wrote:
> > On Tue, Feb 28, 2023 at 03:24:46PM +0100, Laszlo Ersek wrote:
> >> On 2/28/23 14:01, Richard W.M. Jones wrote:
> >>> On Wed, Feb 22, 2023 at 08:20:43PM +0200, Andrey Drobyshev wrote:
> >>>> Since commits b28cd1dc ("Remove