Incorrect log level for failing to create driver when multiple cargo features are enabled.

[ludfjig]

When multiple hypervisors are enabled via features (example both mshv and kvm), and the host system has kvm, an log message of level ERROR will be reported because HypervLinuxDriver::new( will be called, which fails, but later KVMDriver::new will be called, which succeeds.

We should not log an error when this happens.

[ludfjig]

Looking closer on this, the confusion stems from that log messages of level INFO included the string "Error" when calling is_hypervisor_present and the given hypervisor is not present.