cargo: Bump the kvm and vmm-sys-util crates

Since the kvm crates now depend on vmm-sys-util, the bump must be
atomic.
The kvm-bindings and ioctls 0.2.0 and 0.4.0 crates come with a few API
changes, one of them being the use of a kvm_ioctls specific error type.
Porting our code to that type makes for a fairly large diff stat.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>

devices/Cargo.toml

@@ -6,12 +6,12 @@ authors = ["The Chromium OS Authors"]
 [dependencies]
 byteorder = "1.3.2"
 epoll = ">=4.0.1"
-kvm-bindings = "0.1.1"
-kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
+kvm-bindings = "0.2.0"
+kvm-ioctls = "0.4.0"
 libc = "0.2.60"
 log = "0.4.8"
 vm-memory = { git = "https://github.com/rust-vmm/vm-memory" }
-vmm-sys-util = ">=0.1.1"
+vmm-sys-util = ">=0.2.1"
 
 [dev-dependencies]
 tempfile = "3.1.0"

devices/src/ioapic.rs

@@ -13,14 +13,14 @@ use crate::BusDevice;
 use byteorder::{ByteOrder, LittleEndian};
 use kvm_bindings::kvm_msi;
 use kvm_ioctls::VmFd;
+use std::result;
 use std::sync::Arc;
-use std::{io, result};
 use vm_memory::GuestAddress;
 
 #[derive(Debug)]
 pub enum Error {
     /// Failed to send an interrupt.
-    InterruptFailed(io::Error),
+    InterruptFailed(kvm_ioctls::Error),
     /// Invalid destination mode.
     InvalidDestinationMode,
     /// Invalid trigger mode.