search for: nic_model

Displaying 9 results from an estimated 9 matches for "nic_model".

2010 Sep 21
1
[PATCH] Introduce ability to select any kind of nic model, not just default or virtio.
...:model => nic.model) if(nic.network.boot_type.proto == 'static') nnic.ip_addresses << IpAddress.new(:address => nic.ip_address) @@ -221,6 +221,8 @@ class VmController < ApplicationController @nics.push nnic } + @nic_models = Nic::NIC_MODELS + end # merges vm / network parameters as submitted on the vm form @@ -241,7 +243,7 @@ class VmController < ApplicationController nic = { :mac => params[:macs][i], :network_id => network_id, :bandwidth =&g...
2018 Mar 23
2
[PATCH] v2v: ova: convert E1000 network interfaces as such
...se_ovf_from_ova.ml +++ b/v2v/parse_ovf_from_ova.ml @@ -235,9 +235,14 @@ let parse_ovf_from_ova ovf_filename = | Some connection -> connection, Bridge | None -> sprintf "eth%d" i, Network in let mac = xpath_string "rasd:Address/text()" in + let nic_model = + match xpath_string "rasd:ResourceSubType/text()" with + | Some "E1000" -> Some Source_e1000 + | Some _ -> None (* Warn? *) + | None -> None in let nic = { s_mac = mac; - s_nic_model = None; + s_nic_model = ni...
2018 Mar 23
0
Re: [PATCH] v2v: ova: convert E1000 network interfaces as such
...v2v/parse_ovf_from_ova.ml > @@ -235,9 +235,14 @@ let parse_ovf_from_ova ovf_filename = > | Some connection -> connection, Bridge > | None -> sprintf "eth%d" i, Network in > let mac = xpath_string "rasd:Address/text()" in > + let nic_model = > + match xpath_string "rasd:ResourceSubType/text()" with > + | Some "E1000" -> Some Source_e1000 > + | Some _ -> None (* Warn? *) > + | None -> None in > let nic = { > s_mac = mac; > - s_nic_mode...
2019 Feb 25
0
[PATCH 3/3] v2v: add -o json output mode
..." "fd") target_buses.target_floppy_bus; + + !disks, !removables in + List.push_back doc ("disks", JSON.List disks); + List.push_back doc ("removables", JSON.List removables); + + let nics = + List.map ( + fun { s_mac = mac; s_vnet_type = vnet_type; s_nic_model = nic_model; + s_vnet = vnet; } -> + let vnet_type_str = + match vnet_type with + | Bridge -> "bridge" + | Network -> "network" in + + let nic = ref [ + "vnet", JSON.String vnet; + "vne...
2019 Mar 29
0
[PATCH v2 3/3] v2v: add -o json output mode
..." "fd") target_buses.target_floppy_bus; + + !disks, !removables in + List.push_back doc ("disks", JSON.List disks); + List.push_back doc ("removables", JSON.List removables); + + let nics = + List.map ( + fun { s_mac = mac; s_vnet_type = vnet_type; s_nic_model = nic_model; + s_vnet = vnet; } -> + let vnet_type_str = + match vnet_type with + | Bridge -> "bridge" + | Network -> "network" in + + let nic = ref [ + "vnet", JSON.String vnet; + "vne...
2018 Apr 25
9
[PATCH v2 0/9] v2v: -i ova: Handle OVAs containing snapshots.
https://bugzilla.redhat.com/show_bug.cgi?id=1570407 This turned into quite an in-depth refactoring of how we handle OVAs. It also fixes a potential security issue. Rich.
2019 Mar 29
5
[PATCH v2 0/3] v2v: add -o json output mode
This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with
2019 Feb 25
7
[PATCH 0/3] RFC: v2v: add -o json output mode
This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with
2018 Jul 04
4
[PATCH 0/3] v2v: Implement MAC address to network/bridge mapping.
Deep in the discussion of this bug, unfortunately mostly in private comments: https://bugzilla.redhat.com/show_bug.cgi?id=1594515 we decided it'd be more flexible for RHV if we had a way to map individual NICs to target networks and bridges. This can be done by adding a new --mac option so you can specify the exact mapping you need: $ virt-v2v [...] \ --mac