similar to: Windows P2V migration temporary recipe

Now that we can gather diagnostic info, I think I know why our P2Vs kept failing last week. Another one just died right in front of my eyes. I think either the Ethernet or NFS server at this site occasionally "blips" offline when it gets busy and that messes up P2V migrations. The RHEV export domain is an NFS share offered by an old Storagetek NAS, connected over a 10/100 Ethernet.

I just now ran into some traceback messages and other errors running virt-p2v-image-builder 0.8.5.1. Anything to worry about? . . . Installing: passwd ##################### [305/307] Installing: syslinux ##################### [306/307] Installing: vim-minimal ##################### [307/307] Note: Forwarding request to

On 10/11/14 16:01, Richard W.M. Jones wrote: > On Mon, Nov 10, 2014 at 04:12:35PM +0100, Nicolas Ecarnot wrote: >> Hi, >> >> In a oVirt 3.4.4 environnement, and using a >> virt-p2v-0.9.1-2.20130730.1.el6.centos, I'm trying to convert a >> windows 2003 server 32 bits into an oVirt KVM image. >> >> I already succeed doing that many times, but now,

Hi, In a oVirt 3.4.4 environnement, and using a virt-p2v-0.9.1-2.20130730.1.el6.centos, I'm trying to convert a windows 2003 server 32 bits into an oVirt KVM image. I already succeed doing that many times, but now, this is failing : - All the usual process sounds good : PXE -> DHCP -> connection to the P2V server -> choosing the profile -> (checking the debug option) ->

This series makes several enhancements to tests for v2v conversion of Windows guests. Specifically, it - adds a number of files which imitate the stuff that is supposed to be present on the host when the actual conversion is performed, but may not be there when the tests are run. This includes certain tools and virtio drivers - fixes the test for windows conversion to actually

Le 10/11/2014 20:09, Richard W.M. Jones a écrit : >>> Matt - any ideas? >>> >>> There is also the new version of p2v/v2v available, although it >>> requires recent Fedora or RHEL/Centos 7.0. >> >> This is the last thing it does before unwinding: >> >> libguestfs: trace: cp "/transferxdTiHj/windows/rhev-apt.exe" "/Program

Le 19/11/2014 13:03, Richard W.M. Jones a écrit : > On Wed, Nov 19, 2014 at 12:58:11PM +0100, Nicolas Ecarnot wrote: >> But it is now failing with an error message telling it can not >> connect to the local socket /var/run/libvirt/libvirt-sock. > > This is basically a libvirt bug that you have to solve separately. > I'm guessing that basic commands such as `virsh

Hi all, v2 includes all comments from Pino and Richard. I also removed the mkdir /run/lvm in the init since it only failed in one case and couldn't reproduce it anymore. Cédric Bosdonnat (11): v2v: also search for windows virtio drivers in symlinks Update packagelist for SLES and openSUSE customize: fix windows firstboot script customize: change windows firstboot path customize:

v2: - Fix virt-p2v messages too. Rich.

Hi there, Here is v3 of the remaining patches. Diff to v2: * Removed the patch related to QXL * Fixed the firstboot script with Roman's comments * Fixed ova with subfolders test * Handle MF-relative path in ova files * Fixed now unneeded match case as per Richard's comment Cédric Bosdonnat (3): customize: fix windows firstboot script v2v: add support for SUSE VMDP drivers v2v:

Hi there, SUSE ships Virtual Machine Driver Pack for the virtio windows drivers. Get v2v and customize to discover them and use them if available. Cédric Bosdonnat (7): v2v: check next free oem%d.inf in /Windows/Inf v2v: extract controller offset discovery as a function customize: add support for pvvxsvc v2v: extract reusable parts of viostor regedits v2v: adapt the subkey in Enum

Hi there! I know it's been a while since I posted my first version of some patches. But here I have rebased them on top of Roman's work and added a few other ones. Cédric Bosdonnat (11): v2v: also search for windows virtio drivers in symlinks Update packagelist for SLES customize: fix windows firstboot script customize: change windows firstboot path customize: add support for

I am waiting the process hangs, now the conversion is still running... Alain Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com] Envoyé : mardi 14 octobre 2014 11:09 À :

If present, Parallels Tools may stand in the way of proper running the windows guests in non-Parallels hypervisors, so we're better off uninstalling them on the first boot into the new environment. With this patch, the uninstall records for Parallels Tools are looked up in the registry and, if found, corresponding firstboot actions are registered, taking special care that those actions are

This patchset attempts to address a number of shortcomings in the firstboot infrastructure I came across while working with v2v conversion of various Windows VMs. Roman Kagan (4): firstboot: consolidate line ending conversion firstboot: enhance firstboot driver script for Windows firstboot: make script naming descriptive convert_windows: split firstboot into steps

if it works thank god for notepad2 (If it's not then be patience, I am just a windows user). Amos. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-use-single-registry-change-for-all-supported-windows.patch Type: application/octet-stream Size: 10635 bytes Desc: not available URL:

Store log from MSI installer. Log file will be located in firstboot scripts-done directory with name rhev-apt.log. The path has to be double-quoted to handle spaces in path name properly. Hopefully this can help resolve RHBZ#1584678 someday. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_windows.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Wait for driver installations fired by the PnP manager to complete before running firstboot scripts. The first patch is a minor refactoring to pave the way for the second patch. The latter contains the bulk of the changes as well as the description of the idea. Roman Kagan (2): v2v:windows: factor out getting CurrentControlSet v2v:windows: prevent conflicts with PnP on firstboot --- v1

One day I'm going to run a virt-p2v that works to completion. But evidently not today. The source physical machine is Windows 2003. This one copied the whole system drive and then died at the end and deleted the virtual disk it made. Here is the top and bottom of the trace log file on the conversion server. If the email garbles what I'm pasting in below, I can email the log as an

Hi, I'm trying to do a physical-to-virtual migration for a Windows 2003 Server to RHEV 3.0 and I'm getting errors in the conversion. I created a Virt-P2V.iso using Fedora 16 (i686) using virt-v2v-0.8.7 and virt-p2v-image-builder-0.8.7 instead of the 0.8.5 version available in the repos. The conversion server is the same server where I created the ISO. I edited the /etc/virt-v2v.conf