Displaying 10 results from an estimated 10 matches for "get_block_driver_priority".
Did you mean:
set_block_driver_priority
2023 Mar 10
1
[COMMON PATCH v3 3/4] mlcustomize: Add accessors for block driver priority list
...ersion; i_osinfo;
i_product_variant; i_windows_current_control_set; i_windows_systemroot;
- virtio_win = ""; was_set = false }
+ virtio_win = ""; was_set = false;
+ block_driver_priority = ["virtio_blk"; "vrtioblk"; "viostor"] }
+
+let get_block_driver_priority t = t.block_driver_priority
+let set_block_driver_priority t v = t.block_driver_priority <- v
let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}"
let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&REV_00"
@@ -176,14 +183,13 @@ let rec inject_virtio_win_dri...
2023 Mar 06
1
[PATCH common] mlcustomize: Add accessors for block driver priority list
...ersion; i_osinfo;
i_product_variant; i_windows_current_control_set; i_windows_systemroot;
- virtio_win = ""; was_set = false }
+ virtio_win = ""; was_set = false;
+ block_driver_priority = ["virtio_blk"; "vrtioblk"; "viostor"] }
+
+let get_block_driver_priority t = t.block_driver_priority
+let set_block_driver_priority t v = t.block_driver_priority <- v
let scsi_class_guid = "{4D36E97B-E325-11CE-BFC1-08002BE10318}"
let viostor_legacy_pciid = "VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00"
@@ -176,14 +183,13 @@ let rec i...
2023 Mar 07
1
[PATCH v2v] convert: Allow preferred block driver to be specified on the command line
...Inject_virtio_win.from_environment g inspect.i_root Config.datadir in
>>> + (match block_driver with
>>> + | Virtio_blk -> () (* the default, no need to do anything *)
>>> +(*
>>> + | Virtio_scsi ->
>>> + let drivers = Inject_virtio_win.get_block_driver_priority virtio_win in
>>> + let drivers = "vioscsi" :: drivers in
>>> + Inject_virtio_win.set_block_driver_priority virtio_win drivers
>>> +*)
>>> + | IDE -> assert false (* not possible - but maybe ...? *)
>>> + );
>>>
>&...
2023 Mar 07
1
[V2V PATCH v2 4/5] convert_windows: set block driver priority according to block_driver option
...i_firmware block_driver _ static_ips =
*)
let virtio_win =
Inject_virtio_win.from_environment g inspect.i_root Config.datadir in
+ (match block_driver with
+ | Virtio_blk -> () (* the default, no need to do anything *)
+ | Virtio_SCSI ->
+ let drivers = Inject_virtio_win.get_block_driver_priority virtio_win in
+ let drivers = "vioscsi" :: drivers in
+ Inject_virtio_win.set_block_driver_priority virtio_win drivers
+ | IDE -> assert false (* not possible - but maybe ...? *)
+ );
(* If the Windows guest appears to be using group policy.
*
--
2.31.1
2023 Mar 10
1
[V2V PATCH v3 4/6] convert_windows: set block driver priority according to block_driver option
...i_firmware block_driver _ static_ips =
*)
let virtio_win =
Inject_virtio_win.from_environment g inspect.i_root Config.datadir in
+ (match block_driver with
+ | Virtio_blk -> () (* the default, no need to do anything *)
+ | Virtio_SCSI ->
+ let drivers = Inject_virtio_win.get_block_driver_priority virtio_win in
+ let drivers = "vioscsi" :: drivers in
+ Inject_virtio_win.set_block_driver_priority virtio_win drivers
+ | IDE -> assert false (* not possible - but maybe ...? *)
+ );
(* If the Windows guest appears to be using group policy.
*
--
2.31.1
2023 Mar 07
4
[COMMON PATCH v2 0/4] Bring support for virtio-scsi back to Windows
Discussion on v1
https://listman.redhat.com/archives/libguestfs/2023-February/030849.html
https://listman.redhat.com/archives/libguestfs/2023-March/030917.html
v1 -> v2:
* Drop the logic where default is switched to "vioscsi". Keep
virtio-blk as default.
* Adapt the patch suggested by Richard:
https://listman.redhat.com/archives/libguestfs/2023-March/030974.html
This
2023 Mar 10
4
[COMMON PATCH v3 0/4] Bring support for virtio-scsi back to Windows
Discussion on v2:
https://listman.redhat.com/archives/libguestfs/2023-March/030989.html
v2 -> v3:
* Patch 1/4 ("inject_virtio_win: match only vendor/device/revision"):
do not omit PCI Revision ID. Adjust commit message accordingly;
* Patch 2/4 ("inject_virtio_win: add Virtio_SCSI to block_type"):
add non-empty commit message body.
* Patch 4/4
2023 Mar 06
2
[PATCH v2v] convert: Allow preferred block driver to be specified on the command line
This is just an outline patch, only compile tested.
It doesn't make changes to virt-v2v-in-place, but those would be the
same as made in v2v/v2v.ml.
It reuses the existing Types.guestcaps_block_type which is a bit ugly
but fairly practical.
I've made the change to the documentation, but it needs a test.
Rich.
2023 Mar 07
6
[V2V PATCH v2 0/5] Bring support for virtio-scsi back to Windows
Discussion on v1:
https://listman.redhat.com/archives/libguestfs/2023-February/030849.html
https://listman.redhat.com/archives/libguestfs/2023-March/030917.html
v1 -> v2:
* Adapt the patch suggested by Richard, splitting it up into 3:
https://listman.redhat.com/archives/libguestfs/2023-March/030975.html
Now we have "--block-driver" command line option which regulates the
2023 Mar 10
7
[V2V PATCH v3 0/6] Bring support for virtio-scsi back to Windows
Discussion on v2:
https://listman.redhat.com/archives/libguestfs/2023-March/030987.html
v2 -> v3:
* Patch 2/6 ("convert_windows: add Inject_virtio_win.Virtio_SCSI as a
possible block type"): omit "Inject_virtio_win." prefix in favor of type
inference. Add a short commit message body;
* Add tests/test-v2v-block-driver.sh testing the new "--block-driver"