Displaying 2 results from an estimated 2 matches for "viostor_nam".
Did you mean:
viostor_name
2023 Mar 10
1
[V2V PATCH v3 6/6] tests: add --block-driver option test
...+vioscsi_img="$d/vioscsi.qcow2"
+qemu-img create -f qcow2 -b $img_base -o compat=1.1,backing_fmt=raw $viostor_img
+qemu-img create -f qcow2 -b $img_base -o compat=1.1,backing_fmt=raw $vioscsi_img
+base_md5="$(do_md5 $img_base)"
+
+viostor_xml="$d/windows-viostor.xml"
+viostor_name=windows-viostor
+cat > $viostor_xml <<EOF
+<node>
+ <domain type='test'>
+ <name>$viostor_name</name>
+ <memory>1048576</memory>
+ <os>
+ <type>hvm</type>
+ <boot dev='hd'/>
+ </os>
+...
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"