<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML><head><META content="text/html; charset=utf-8" http-equiv="Content-Type"> <STYLE></STYLE> <META content="text/html; charset=utf-8" HTTP-EQUIV="Content-Type"> <META CONTENT="MS Exchange Server version 6.5.7655.4" NAME="Generator"> <TITLE>RE: [Libguestfs] P2Vs seem to require a very robust Ethernet</TITLE> </head><BODY>  I like it, we have the space. alternatively i build a physical fedora 16 box with 500 gb of space... I can get on it tomorrow night -----Original Message----- From: Greg Scott [<A HREF="mailto:GregScott@Infrasupport.com">mailto:GregScott@Infrasupport.com</A>] Sent: Fri 12/2/2011 5:57 PM To: Greg Scott; Matthew Booth; Richard W.M. Jones; libguestfs@redhat.com Cc: Fredy Hernández; Joey Bertalan Subject: RE: [Libguestfs] P2Vs seem to require a very robust Ethernet After 5 or 6 hours, we aborted today's attempt, disconnected the 2nd HDD (sdb) from the original host, and started up a new one. Since all we have to go on are guesses - there was a bug with the Windows virtio network driver where the driver would go offline during bulk copies. I bring this up because our P2V conversion server is a Fedora VM, probably using the Linux virtio driver. Was there a similar bug with the Linux VirtIO driver? One possible sequence of events: - Data flies fast and furious in and out of the conversion server VM to the NFS server. - The conversion server VM NIC goes offline. - The source host eventually hangs or dies. - virt-p2v-server eventually gives up and writes a cryptic log message. Another possible sequence of events: - The source server starts copying. - The source server runs into a problem and either hangs or dies. - Virt-p2v-server on the conversion server eventually times out waiting for data. What do you think about trying a physical conversion server, possibly using itself as the NFS Server and RHEV Export domain? - Greg -----Original Message----- From: libguestfs-bounces@redhat.com [<A HREF="mailto:libguestfs-bounces@redhat.com">mailto:libguestfs-bounces@redhat.com</A>] On Behalf Of Greg Scott Sent: Friday, December 02, 2011 3:18 PM To: Matthew Booth; Richard W.M. Jones; libguestfs@redhat.com Cc: Fredy Hernandez; Joey Bertalan Subject: Re: [Libguestfs] P2Vs seem to require a very robust Ethernet Our track record for P2Vs isn't very good so far; we've had one run to completion in about 8 or 9 tries so far. We've tried source systems with different versions of Windows, all but one failed. The one success was a test Windows XP machine with one hard drive. We boot a Windows system from the CD, start up a P2V, it runs for an apparently random length of time, then the P2V percentage just stops somewhere. The other day was 13 percent. Today it's 8 percent. Eventually, virt-p2v-server on the conversion server also stops and I see a message in the log file that says, " virt-v2v: Error receiving data:". Is there anything we can look at from an alternate console on the source server booted from that CD? Thanks - Greg _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com <A HREF="https://www.redhat.com/mailman/listinfo/libguestfs">https://www.redhat.com/mailman/listinfo/libguestfs</A> Fredy Hernandez Systems Administrator 763-574-8734 Office hernandez@stylmark.com <IMG ALIGN="baseline" ALT="" BORDER="0" HEIGHT="33" HSPACE="0" SRC="cid:Stylmark-logo.jpg@c0fd63d4.6d8e48c8" STYLE="WIDTH: 193px; HEIGHT: 33px" WIDTH="214"></BODY></HTML>