Displaying 5 results from an estimated 5 matches for "enable_kernel_module".
2010 Feb 18
2
[PATCH 1/2] ESX: Look harder for potential transfer failures
Although I can't reproduce, I seem to have had an incomplete transfer which
wasn't picked up by the existing error handling. This change adds some more
sanity checks:
* Check for error on close() (should have been doing this anyway)
* Check that the bytes received == reported content length
---
lib/Sys/VirtV2V/Transfer/ESX.pm | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1
2010 Mar 31
1
[PATCH] Default to IDE when VirtIO isn't available
...}
- $scsi_hostadapter = 1;
+ # IDE doesn't need scsi_hostadapter
+ else {
+ $guestos->disable_kernel_module($module);
+ }
}
}
# Add an explicit scsi_hostadapter if it wasn't there before
- $guestos->enable_kernel_module('scsi_hostadapter',
- $virtio ? "virtio_blk" : "sym53c8xx")
- unless($scsi_hostadapter);
+ if ($virtio && !$scsi_hostadapter) {
+ $guestos->enable_kernel_module('scsi_hostadapter', 'virtio_blk');...
2010 May 13
1
[PATCH] Improve augeas error reporting
...die(user_message($msg)) if (length($msg) > 0);
+ die($err);
+}
+
# Handle SELinux for the guest
sub _init_selinux
{
@@ -185,7 +238,7 @@ sub _init_augeas
};
# The augeas calls will die() on any error.
- die($@) if($@);
+ $self->_augeas_error($@) if ($@);
}
=item enable_kernel_module(device, module)
@@ -209,7 +262,7 @@ sub enable_kernel_module
};
# Propagate augeas errors
- die($@) if($@);
+ $self->_augeas_error($@) if ($@);
}
=item update_kernel_module(device, module)
@@ -242,7 +295,7 @@ sub update_kernel_module
};
# Propagate augeas errors...
2010 Jul 28
3
Create new Sys::VirtV2V::Util
These 2 patches are mostly code motion. They were prompted by an apparent augeas
error in BZ 613967 which didn't display useful error message. The error seems to
happen in Converter::Linux. GuestOS::RedHat had a handy function which displayed
verbose augeas error messages. This function moves into the new module where it
can be used by both modules.
The second patch is an consequential tidy
2010 Feb 19
2
[PATCH 1/2] Fix remapping of block devices
We were assuming that guests wouldn't use multiple interfaces, or if they did,
drive letters wouldn't clash between the interfaces. An ESX guest with a CDROM
device breaks this because hard disks will be presented a SCSI, starting at sda,
and CDROM devices are presented as IDE, starting at hda. This is in contrast to
QEMU, which starts at hdc by default.
Firstly, this change causes disks