similar to: P2V challenge that demands some creativity

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

On Wed, Nov 19, 2014 at 02:41:49PM +0100, Nicolas Ecarnot wrote: > When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely > then failed saying it was not a kind of OS it knows how to convert. We could probably support OEL with a bit of effort, but it's not supported now. The virt-v2v manual (which you should read, as well as the virt-p2v manual) provides a list of all OSes

These are the current steps we followed to set up and run Windows P2V migrations. Note that development is proceeding rapidly and the versions of all pieces below will likely be obsolete soon. ************************************************************* Windows RHEV P2V Cookbook 2011-1122 1. Install 32 bit Fedora 14 as a virtual machine or physical host. You will use this system to build

libguestfs is a set of tools for reading and modifying disk images and virtual machines. virt-v2v and virt-p2v are tools for converting guests from foreign hypervisors (especially VMware, Xen), or physical machines, to run on KVM (eg. virt-manager, OpenStack/RHOS or oVirt/RHEV). This is just a heads-up about some changes to the way libguestfs and related packages will be packaged in RHEL 7.2.

Le 19/11/2014 15:03, Richard W.M. Jones a écrit : > On Wed, Nov 19, 2014 at 02:41:49PM +0100, Nicolas Ecarnot wrote: >> When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely >> then failed saying it was not a kind of OS it knows how to convert. > > We could probably support OEL with a bit of effort, but it's not > supported now. The virt-v2v manual (which

Hello, Answers below : Le 13/11/2014 16:06, Richard W.M. Jones a écrit : >>>> This is the last thing it does before unwinding: >>>> >>>> libguestfs: trace: cp "/transferxdTiHj/windows/rhev-apt.exe" "/Program >>>> Files/RedHat/V2V Firstboot" >>>> libguestfs: trace: cp = 0 >>>> >>>> So, maybe

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.

Set mnemonics for all the labels with a text entry or combo box next to them, and for all the buttons, and check boxes. --- p2v/gui.c | 56 ++++++++++++++++++++++++++++++++++---------------------- 1 file changed, 34 insertions(+), 22 deletions(-) diff --git a/p2v/gui.c b/p2v/gui.c index 36bb655..dee8b83 100644 --- a/p2v/gui.c +++ b/p2v/gui.c @@ -285,13 +285,14 @@ create_connection_dialog (struct

-----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Tuesday, January 14, 2014 4:42 PM To: Исаев Виталий Анатольевич Cc: libguestfs@redhat.com Subject: Re: [Libguestfs] Libguestfs can't launch with one of the disk images in the RHEV cluster On Tue, Jan 14, 2014 at 08:07:43AM +0000, Исаев Виталий Анатольевич wrote: > [00072ms] /usr/libexec/qemu-kvm \

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 List, I have a very strange problem with NTBACKUP writing to a SAMBA share. NTBACKUP won't write files bigger than 4.29GB to a SAMBA share. Here are the specs of the systems: SAMBA Server: Slackware 10.1 SAMBA 3.0.21a (large file support turned on) Kernel 2.6.8 / ReiserFS Windows Server: Windows 2003 Server NTBACKUP (latest version) Data to backup is about 50GB

I have had this problem for more than one year and have asked this same question twice on this list without any answears for past two years. So I assume that this question is quite difficult unless I really missed something, :-). We are using Samba 2.2.0 on RedHat 7.2 with domain authentication on NT 4.0 server. We are using NTbackup on a NT BDC to backup samba shares via mapped drives. The

Hi all, I'm experiencing a problem when NTBACKING'UP my W2000 Server files against a Linux 2.4.9 + ReiserFS 3.6 file system + Samba share. It works OK for the first 4 Gb's around file size. Then ntbackup stops serving data and the file on the samba side appears to be downsized to 0 and growing ssssslowly. Once you stop ntbackup by killing the process, the file reappears at its real

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

We just released virt-v2v 0.8.5, which also covers virt-p2v. This is primarily a bugfix release, with a couple of new features thrown in. The major changes are summarised below: V2V *** * Default -ic and -oc to qemu:///session or qemu:///system as appropriate depending on root. * Allow Windows conversions to succeed when firstboot.bat, rhsrvany.exe and rhev-apt.exe aren't available. *

On Mon, Nov 10, 2014 at 08:28:53PM +0100, Nicolas Ecarnot wrote: > 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: >

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,

Currently virt-p2v requires Gtk 2. This commit changes virt-p2v so it can be built with either Gtk 2 or 3. By careful use of macros, this code should compile on both recent Gtk 2 and Gtk 3. With no other options, ./configure will now prefer Gtk 3 if it finds it, or fall back to Gtk 2. But you can control this by setting './configure --with-gtk=2|3|check|no' where the options mean: *

Le 19/11/2014 10:47, Richard W.M. Jones a écrit : > On Wed, Nov 19, 2014 at 09:08:36AM +0100, Nicolas Ecarnot wrote: >> I tried to use the virt-p2v-make-disk, but it failed to connect to a >> libvirt socket (obviously, there is none running in this VM.) > > To avoid libvirt problems, do: > > export LIBGUESTFS_BACKEND=direct > > Why don't you use the ISO?

On Mon, Nov 10, 2014 at 04:52:35PM +0000, Matthew Booth wrote: > 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