similar to: virt-p2v NVMe disks

On Tue, Nov 10, 2020 at 11:53:19PM +0000, Femi Adegoke wrote: > Actually I suspect we need to modify virt-p2v to recognize > /dev/nvme* as a block device name. > > Hi Mr. Jones, > > Any approximate time frame on when the NVMe "mod" might happen? I guess when someone contributes a patch. Rich. -- Richard Jones, Virtualization Group, Red Hat

On Wed, Nov 04, 2020 at 08:01:49AM +0000, Femi Adegoke wrote: > Any idea how I can disable this message? It stops me from booting up the > virt-p2v iso. > > o/s is Fedora 33 WS. > > Probing EDD (edd=off to disable)... ok You mean this message specifically? It's a kernel message and shouldn't stop it from booting, but if it does try adding edd=off on the kernel command

On Wed, Nov 04, 2020 at 08:36:12AM +0000, Femi Adegoke wrote: > > Is this how I would get to the kernel cmd line of the virt-p2v iso? > > Add edd=off to the first(!) kernel line inside the VM in /boot/grub/grub.conf The easiest thing is just to interrupt grub at boot (hit "Esc"), then edit the kernel command line there. This is a one-off change that you have to do each

On Wed, Nov 04, 2020 at 09:04:44AM +0000, Femi Adegoke wrote: > virt-p2v hangs & displays the edd message right after I select which kernel to > boot into. > At that point I have to power cycle the pc. > Yesterday (before I sent you email), it hung a few times but after the 5th > power cycle it went through. EDD is an ancient BIOS standard that's not relevant today.

On Wed, Nov 19, 2014 at 10:05:53PM +0100, Nicolas Ecarnot wrote: > Nov 19 21:54:52 serv-p2v-adm1 sshd[2727]: pam_unix(sshd:session): > session opened for user root by (uid=0) > Nov 19 21:54:53 serv-p2v-adm1 sshd[2725]: channel 2: open failed: > connect failed: Connection refused > Nov 19 21:54:53 serv-p2v-adm1 sshd[2727]: Received disconnect from > 192.168.49.5: 11: disconnected

Le 19/11/2014 18:12, Richard W.M. Jones a écrit : > On Wed, Nov 19, 2014 at 04:42:23PM +0100, Nicolas Ecarnot wrote: >> disks: >> nbd:localhost:33363 (raw) [sda] >> nbd:localhost:49584 (raw) [sdb] >> nbd:localhost:41988 (raw) [sdc] >> removable media: >> >> NICs: >> >> [ 0.0] Creating an overlay to protect the source from being modified

Hello, I am trying to convert a physical server (10 year old hardware with PCI LSI Loging / Symbios LSI MegaRAID controller and SCSI drives, RAID 5 Configuration) into a Virtual Machine in oVirt (oVirt Version 4.1.8). Host to be converted has Fedora 5 OS. I have downloaded the virt-p2v.iso (Cent OS 7.3). I have prepared the conversion server, set it up as a VM in oVirt environment. I am able

A convenience method instead of having to work out the right qemu command line each time. --- .gitignore | 1 + p2v/Makefile.am | 28 ++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+) diff --git a/.gitignore b/.gitignore index 285b28d..8509a9d 100644 --- a/.gitignore +++ b/.gitignore @@ -337,6 +337,7 @@ Makefile.in /p2v/virt-p2v /p2v/virt-p2v.1 /p2v/virt-p2v.i686

On Thursday 26 May 2016 16:40:16 Richard W.M. Jones wrote: > A convenience method instead of having to work out the right > qemu command line each time. > --- > .gitignore | 1 + > p2v/Makefile.am | 28 ++++++++++++++++++++++++++++ > 2 files changed, 29 insertions(+) > > diff --git a/.gitignore b/.gitignore > index 285b28d..8509a9d 100644 > --- a/.gitignore

Currently 'make install' installs the virt-p2v binary in /usr/libexec/virt-p2v on the host. It is never supposed to be run from there, even by another program, so use of /usr/libexec is incorrect. It is only supposed to be copied into USB keys / ISOs / etc created by virt-p2v-make-* scripts. The other problem with shipping a "naked" binary on the host is that packages built

On Thu, Jun 23, 2016 at 10:18:02AM +0200, Cédric Bosdonnat wrote: > virt-p2v-make-kiwi now forces the launch-virt-p2v mode to 0755 to > ensure the executable bit it set for user. > --- > p2v/virt-p2v-make-kiwi.in | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/p2v/virt-p2v-make-kiwi.in b/p2v/virt-p2v-make-kiwi.in > index e493bd4..3506e9b 100644 > ---

Move all the dependencies with the same name in all the distributions to a single list at the end. There should be no change to the package list used to build the p2v ISO. --- p2v/dependencies.m4 | 72 ++++++++++++++++------------------------------------- 1 file changed, 21 insertions(+), 51 deletions(-) diff --git a/p2v/dependencies.m4 b/p2v/dependencies.m4 index 21541b4..e590f57 100644 ---

virt-p2v-make-kiwi now forces the launch-virt-p2v mode to 0755 to ensure the executable bit it set for user. --- p2v/virt-p2v-make-kiwi.in | 1 + 1 file changed, 1 insertion(+) diff --git a/p2v/virt-p2v-make-kiwi.in b/p2v/virt-p2v-make-kiwi.in index e493bd4..3506e9b 100644 --- a/p2v/virt-p2v-make-kiwi.in +++ b/p2v/virt-p2v-make-kiwi.in @@ -190,6 +190,7 @@ cp $datadir/issue $output/root/etc/issue

From: Alban Lecorps <alban.lecorps at ubisoft.com> The "-oo" option will be useful primarily for the openstack output mode (currently disabled, from commit b74c126629e3, "Ignore 'openstack' driver", 2020-03-16). Use a ConfigStringList knob for "-oo", and for each OPTION=VALUE element in that list, create a separate "-oo OPTION=VALUE" option.

On Debian systems, usually daemons are run automatically after their installations; since we are upgrading the template, and installing packages such as openssh, network-manager, etc, this may cause few daemon to stay running during the virt-builder execution, causing it to fail when shutting down (since e.g. /sysroot/dev would be in use). As workaround, use a temporary policy-rc.d policy layer

It relied on the qemu libguestfs was configured with, which is no more available now. Since we already require libguestfs tools for some functional tests, make run-virt-p2v-in-a-vm depend on libguestfs too, and use the qemu configured in libguestfs. --- Makefile.am | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index d27219d..d1b4bee 100644 ---

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 Wed, Feb 29, 2012 at 07:23:20PM -0500, Cole Robinson wrote: > On 02/29/2012 06:17 PM, Mike Brady wrote: > > I have been doing some testing with v2v and p2v and have got stuck on with p2v > > failing on mmy test systems and need some pointers. > > > > I got v2v working for Centos 5 Xen to Centos 6 KVM for both Linux (Centos) and > > Windows (2008) with out too

Hi, this small series fixes the generation of Debian-based images using virt-p2v-make-disk. With this series, the image can boot fine, X is started, and the p2v interface appears. I haven't tried an actual conversion, but I don't think there are Debian-specific problems preventing that. Thanks, Pino Toscano (4): p2v: fix Gtk dependencies on Debian p2v: remove

When virtualizing a physical machine ("P2V"), the conversion step is done by virt-v2v, but there is a small GUI / front end component called virt-p2v which has to run on the source physical machine in a special environment. http://libguestfs.org/virt-p2v.1.html#network-setup Because the nature of the problem is that we want to virtualize old machines, this means virt-p2v sometimes