search for: get_display_driver

...linux.ml b/v2v/convert_linux.ml --- a/v2v/convert_linux.ml    2019-02-28 16:30:58.668800431 -0700 +++ b/v2v/convert_linux.ml    2019-02-28 16:33:14.729907825 -0700 @@ -104,7 +104,7 @@ let convert (g : G.guestfs) inspect sour        let video =        match rcaps.rcaps_video with -      | None -> get_display_driver () +      | None -> QLX        | Some video -> video in        let block_type = @@ -771,9 +771,6 @@ let convert (g : G.guestfs) inspect sour      else        true   -  and get_display_driver () = -    if family = `SUSE_family then Cirrus else QXL -    and configure_display_driver video =     ...

Hi Mike, in 2013 you added the support for SUSE guests in the old virt-v2v (the one written in Perl); the commit doing it is attached, since the old virt-v2v was hosted on fedorahosted.org, which is no more. As part of that change, the default graphics driver was changed to be cirrus for SUSE guests, and qxl (as before) for any other. When Rich Jones rewrote virt-v2v in 2014 in OCaml, he kept

...ck_prefix in + match block_type with + | Virtio_blk -> "vd" + | IDE -> ide_block_prefix in let map = mapi ( @@ -1411,15 +1420,29 @@ let rec convert ~keep_serial_console (g : G.guestfs) inspect source = let acpi = supports_acpi () in - let video = get_display_driver () in + let video = + match rcaps.rcaps_video with + | None -> get_display_driver () + | Some video -> video in + + let block_type = + match rcaps.rcaps_block_bus with + | None -> if virtio then Virtio_blk else IDE + | Some block_type -> block_type in + + let net_ty...

...ck_prefix in + match block_type with + | Virtio_blk -> "vd" + | IDE -> ide_block_prefix in let map = mapi ( @@ -1411,15 +1420,29 @@ let rec convert ~keep_serial_console (g : G.guestfs) inspect source = let acpi = supports_acpi () in - let video = get_display_driver () in + let video = + match rcaps.rcaps_video with + | None -> get_display_driver () + | Some video -> video in + + let block_type = + match rcaps.rcaps_block_bus with + | None -> if virtio then Virtio_blk else IDE + | Some block_type -> block_type in + + let net_ty...

The decision on which device type to use for disks, network and video cards on output used to be taken deep inside the converting functions. This is not always desirable. In particular, there are scenarios when this decision is made before the convertion takes place. E.g. in in-place mode, the decisions are taken and the output VM configuration is created outside of v2v tool. This patchset

The decision on which device type to use for disks, network and video cards on output used to be taken deep inside the converting functions. This is not always desirable. In particular, there are scenarios when this decision is made before the convertion takes place. E.g. in in-place mode, the decisions are taken and the output VM configuration is created outside of v2v tool. This patchset

The decision on which device type to use for disks, network and video cards on output used to be taken deep inside the converting functions. This is not always desirable. In particular, there are scenarios when this decision is made before the convertion takes place. E.g. in in-place mode, the decisions are taken and the output VM configuration is created outside of v2v tool. This patchset

The decision on which device type to use for disks, network and video cards on output used to be taken deep inside the converting functions. This is not always desirable. In particular, there are scenarios when this decision is made before the convertion takes place. E.g. in in-place mode, the decisions are taken and the output VM configuration is created outside of v2v tool. This patchset