VMWare and HyperV Drivers not available

[hspencer77]

Looking under the following directory:

https://github.com/eucalyptus/windows-integration/tree/master/Drivers

there are no drivers for VMware and HyperV as mentioned in EucaWindowsService/Program.cs:

string xenPVFile = _installLocation + "\\xenpv.zip";
                string virtioFile = _installLocation + "\\virtio.zip";
                string vmwareFile = _installLocation + "\\vmware";
                string hypervFile = _installLocation + "\\hyperv";

                if (!(File.Exists(xenPVFile) || File.Exists(virtioFile) || File.Exists(vmwareFile) || File.Exists(hypervFile)))
                    throw new InstallException("No hypervisor is chosen!");
                int retCode = 0;

This will cause issues for Windows images that are created to run on VMware.

[sangmin]

it won't cause issues. The files will be created when the package is
installed.

On Thu, Aug 8, 2013 at 12:53 PM, Harold Spencer Jr. <
notifications@github.com> wrote:

Looking under the following directory:

https://github.com/eucalyptus/windows-integration/tree/master/Drivers

there are no drivers for VMware and HyperV as mentioned in
EucaWindowsService/Program.cs:

string xenPVFile = _installLocation + "\xenpv.zip";
string virtioFile = _installLocation + "\virtio.zip";
string vmwareFile = _installLocation + "\vmware";
string hypervFile = _installLocation + "\hyperv";

            if (!(File.Exists(xenPVFile) || File.Exists(virtioFile) || File.Exists(vmwareFile) || File.Exists(hypervFile)))
                throw new InstallException("No hypervisor is chosen!");
            int retCode = 0;

This will cause issues for Windows images that are created to run on
VMware.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9
.

[hspencer77]

@sangmin Where do we pull in the VMware drivers (in the code) during package install? Do we pull in the latest version, or the versions we are currently supporting (i.e. VMware 5.0/5.1)? Thanks for your help with this.

[sangmin]

@hspencer77 oh.. they are not the actual drivers. they are just place holder to indicate on which hypervisor the tool is installed.