fixup! Remove existing hypervisor_handler thread and associated

Signed-off-by: Ludvig Liljenberg <[email protected]>

Author: ludfjig

src/hyperlight_host/src/error.rs

@@ -122,22 +122,6 @@ pub enum HyperlightError {
     #[error("HostFunction {0} was not found")]
     HostFunctionNotFound(String),
 
-    /// An attempt to communicate with or from the Hypervisor Handler thread failed
-    /// (i.e., usually a failure call to `.send()` or `.recv()` on a message passing
-    /// channel)
-    #[error("Communication failure with the Hypervisor Handler thread")]
-    HypervisorHandlerCommunicationFailure(),
-
-    /// An attempt to cancel a Hypervisor Handler execution failed.
-    /// See `terminate_hypervisor_handler_execution_and_reinitialise`
-    /// for more details.
-    #[error("Hypervisor Handler execution cancel attempt on a finished execution")]
-    HypervisorHandlerExecutionCancelAttemptOnFinishedExecution(),
-
-    /// A Receive for a Hypervisor Handler Message Timedout
-    #[error("Hypervisor Handler Message Receive Timedout")]
-    HypervisorHandlerMessageReceiveTimedout(),
-
     /// Reading Writing or Seeking data failed.
     #[error("Reading Writing or Seeking data failed {0:?}")]
     IOError(#[from] std::io::Error),

src/hyperlight_host/src/hypervisor/mod.rs

@@ -113,10 +113,6 @@ pub enum HyperlightExit {
 }
 
 /// A common set of hypervisor functionality
-///
-/// Note: a lot of these structures take in an `Option<HypervisorHandler>`.
-/// This is because, if we are coming from the C API, we don't have a HypervisorHandler and have
-/// to account for the fact the Hypervisor was set up beforehand.
 pub(crate) trait Hypervisor: Debug + Sync + Send {
     /// Initialise the internally stored vCPU with the given PEB address and
     /// random number seed, then run it until a HLT instruction.