Displaying 4 results from an estimated 4 matches for "_v2v_volfh".
Did you mean:
_v2v_vol
2010 Feb 18
2
[PATCH 1/2] ESX: Look harder for potential transfer failures
...':content_cb' => sub { $self->handle_data(@_); },
':read_size_hint' => 64 * 1024);
@@ -150,10 +151,18 @@ sub get_volume
die($died) if (defined($died));
# Close the volume file descriptor
- close($self->{_v2v_volfh});
+ close($self->{_v2v_volfh})
+ or die(user_message(__x("Error closing volume handle: {error}",
+ error => $!)));
return $self->{_v2v_vol};
}
+ die(user_message(__x("Didn't receive full volume. Rec...
2010 Mar 30
3
[PATCH 1/2] Refactor guest and volume creation into Sys::VirtV2V::Target::LibVirt
...);
+ return $target->get_volume($volname);
}
$self->{_v2v_received} = 0;
@@ -150,11 +138,9 @@ sub get_volume
my $died = $r->header('X-Died');
die($died) if (defined($died));
- # Close the volume file descriptor
- close($self->{_v2v_volfh})
- or die(user_message(__x("Error closing volume handle: {error}",
- error => $!)));
- return $self->{_v2v_vol};
+ my $vol = $self->{_v2v_vol};
+ $vol->close();
+ return $vol;
}
die(user_mes...
2010 Jan 29
4
[FOR REVIEW ONLY] ESX work in progress
The following patches are where I'm currently at with ESX support. I can now
import a domain from ESX along with its storage. Note that I'm not yet doing any
conversion. In fact, I've never even tested past the import stage (I just had an
exit in there).
The meat is really in the 4th patch. The rename of MetadataReader->Connection
was because the Connection is now really providing
2010 Feb 01
9
[ESX support] Working ESX conversion for RHEL 5
With this patchset I have successfully[1] imported a RHEL 5 guest directly from
ESX with the following command line:
virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64
Login details are stored in ~/.netrc
Note that this is the only guest I've tested against. I haven't for example,
checked that I haven't broken Xen imports.
Matt
[1] With the exception of