Re: [Libguestfs] virt-p2v NVMe disks
On Mon, Nov 02, 2020 at 11:15:18PM +0000, Femi Adegoke wrote:
Hello Mr. Jones,
Trying to convert a Fedora WS desktop to virtual. The WS is installed on a Samsung 1TB m2 NVMe drive . No local disk shows up so I can’t execute conversion.
Does virt-p2v support NVMe?
TBH I'm not sure. If you get a shell inside virt-p2v (press the "XTerm" button, or use the F-keys to get to a console), try running: lsblk and send us the output. Actually I suspect we need to modify virt-p2v to recognize /dev/nvme* as a block device name. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
This is the original output. I will send the virt-p2v version as soon as I can solve this (see below). It did this earlier but booted after a few re-tries. o/s is Fedora 33 WS. Probing EDD (edd=off to disable)... ok [femi@x9da7-fateknollogee-com ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 93.8M 1 loop /var/lib/snapd/snap/core/8935 loop1 7:1 0 62.1M 1 loop /var/lib/snapd/snap/gtk-common-themes/1506 loop2 7:2 0 193M 1 loop /var/lib/snapd/snap/mailspring/440 loop3 7:3 0 193M 1 loop /var/lib/snapd/snap/mailspring/468 loop4 7:4 0 54.9M 1 loop /var/lib/snapd/snap/core18/1705 loop5 7:5 0 93.9M 1 loop /var/lib/snapd/snap/core/9066 loop6 7:6 0 48.3M 1 loop /var/lib/snapd/snap/gtk-common-themes/1474 loop7 7:7 0 54.9M 1 loop /var/lib/snapd/snap/core18/1754 zram0 252:0 0 4G 0 disk [SWAP] nvme1n1 259:0 0 931.5G 0 disk nvme0n1 259:1 0 931.5G 0 disk ├─nvme0n1p1 259:2 0 200M 0 part /boot/efi ├─nvme0n1p2 259:3 0 2G 0 part /boot ├─nvme0n1p3 259:4 0 382G 0 part │ ├─fedora_x9da7-root │ │ 253:0 0 75G 0 lvm / │ ├─fedora_x9da7-swap │ │ 253:1 0 32G 0 lvm [SWAP] │ └─fedora_x9da7-home │ 253:2 0 300G 0 lvm /home └─nvme0n1p4 259:5 0 25G 0 part └─fedora_x9da7-root 253:0 0 75G 0 lvm / ________________________________ From: Richard W.M. Jones <rjones@redhat.com> Sent: Tuesday, November 3, 2020 12:01 AM To: Femi Adegoke <femi@awedio.com>; ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks On Mon, Nov 02, 2020 at 11:15:18PM +0000, Femi Adegoke wrote:
Hello Mr. Jones,
Trying to convert a Fedora WS desktop to virtual. The WS is installed on a Samsung 1TB m2 NVMe drive . No local disk shows up so I can’t execute conversion.
Does virt-p2v support NVMe?
TBH I'm not sure. If you get a shell inside virt-p2v (press the "XTerm" button, or use the F-keys to get to a console), try running: lsblk and send us the output. Actually I suspect we need to modify virt-p2v to recognize /dev/nvme* as a block device name. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
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 ________________________________ From: Femi Adegoke <femi@awedio.com> Sent: Tuesday, November 3, 2020 2:14 AM To: ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks This is the original output. I will send the virt-p2v version as soon as I can solve this (see below). It did this earlier but booted after a few re-tries. o/s is Fedora 33 WS. Probing EDD (edd=off to disable)... ok [femi@x9da7-fateknollogee-com ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 93.8M 1 loop /var/lib/snapd/snap/core/8935 loop1 7:1 0 62.1M 1 loop /var/lib/snapd/snap/gtk-common-themes/1506 loop2 7:2 0 193M 1 loop /var/lib/snapd/snap/mailspring/440 loop3 7:3 0 193M 1 loop /var/lib/snapd/snap/mailspring/468 loop4 7:4 0 54.9M 1 loop /var/lib/snapd/snap/core18/1705 loop5 7:5 0 93.9M 1 loop /var/lib/snapd/snap/core/9066 loop6 7:6 0 48.3M 1 loop /var/lib/snapd/snap/gtk-common-themes/1474 loop7 7:7 0 54.9M 1 loop /var/lib/snapd/snap/core18/1754 zram0 252:0 0 4G 0 disk [SWAP] nvme1n1 259:0 0 931.5G 0 disk nvme0n1 259:1 0 931.5G 0 disk ├─nvme0n1p1 259:2 0 200M 0 part /boot/efi ├─nvme0n1p2 259:3 0 2G 0 part /boot ├─nvme0n1p3 259:4 0 382G 0 part │ ├─fedora_x9da7-root │ │ 253:0 0 75G 0 lvm / │ ├─fedora_x9da7-swap │ │ 253:1 0 32G 0 lvm [SWAP] │ └─fedora_x9da7-home │ 253:2 0 300G 0 lvm /home └─nvme0n1p4 259:5 0 25G 0 part └─fedora_x9da7-root 253:0 0 75G 0 lvm / ________________________________ From: Richard W.M. Jones <rjones@redhat.com> Sent: Tuesday, November 3, 2020 12:01 AM To: Femi Adegoke <femi@awedio.com>; ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks On Mon, Nov 02, 2020 at 11:15:18PM +0000, Femi Adegoke wrote:
Hello Mr. Jones,
Trying to convert a Fedora WS desktop to virtual. The WS is installed on a Samsung 1TB m2 NVMe drive . No local disk shows up so I can’t execute conversion.
Does virt-p2v support NVMe?
TBH I'm not sure. If you get a shell inside virt-p2v (press the "XTerm" button, or use the F-keys to get to a console), try running: lsblk and send us the output. Actually I suspect we need to modify virt-p2v to recognize /dev/nvme* as a block device name. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
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 line as suggested. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
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 ________________________________ From: Richard W.M. Jones <rjones@redhat.com> Sent: Wednesday, November 4, 2020 12:16 AM To: Femi Adegoke <femi@awedio.com> Cc: ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks 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 line as suggested. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
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 time you boot P2V. If you are making virt-p2v disks/ISOs then how to change this permanently depends on what method you're using. It may be better to look at the source code of the virt-p2v-make* scripts in the virt-p2v git repository. https://github.com/libguestfs/virt-p2v Does adding edd=off actually help? Does virt-p2v hang at boot? I wasn't clear on exactly what was happening. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
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. ________________________________ From: Richard W.M. Jones <rjones@redhat.com> Sent: Wednesday, November 4, 2020 12:57 AM To: Femi Adegoke <femi@awedio.com> Cc: ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks 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 time you boot P2V. If you are making virt-p2v disks/ISOs then how to change this permanently depends on what method you're using. It may be better to look at the source code of the virt-p2v-make* scripts in the virt-p2v git repository. https://github.com/libguestfs/virt-p2v Does adding edd=off actually help? Does virt-p2v hang at boot? I wasn't clear on exactly what was happening. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
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. However the fact it prints "ok" means it should have got past EDD detection (so I expect edd=off will make no difference) and the kernel is getting stuck somewhere else. If you look at where EDD is queried (query_edd ()): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch... it's just before changing video mode and going into protected mode, so most likely it's one of those things which is breaking. Also the EDD message is the last message printed through BIOS calls which is why it can appear to hang there even though the boot is continuing and perhaps stopping much later - you're just losing the later messages. You might want to try enabling more debug messages or (the ideal way) adding a serial console to enable you to see all kernel messages. What hardware is this? Something very old or unusual? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
This is a SuperMicro motherboard booting off an NVMe disk. https://www.supermicro.com/products/motherboard/xeon/c600/x9da7.cfm ________________________________ From: Richard W.M. Jones <rjones@redhat.com> Sent: Wednesday, November 4, 2020 1:17 AM To: Femi Adegoke <femi@awedio.com> Cc: ptoscano@redhat.com <ptoscano@redhat.com>; libguestfs@redhat.com <libguestfs@redhat.com> Subject: Re: virt-p2v NVMe disks 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. However the fact it prints "ok" means it should have got past EDD detection (so I expect edd=off will make no difference) and the kernel is getting stuck somewhere else. If you look at where EDD is queried (query_edd ()): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch... it's just before changing video mode and going into protected mode, so most likely it's one of those things which is breaking. Also the EDD message is the last message printed through BIOS calls which is why it can appear to hang there even though the boot is continuing and perhaps stopping much later - you're just losing the later messages. You might want to try enabling more debug messages or (the ideal way) adding a serial console to enable you to see all kernel messages. What hardware is this? Something very old or unusual? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
participants (2)
-
Femi Adegoke -
Richard W.M. Jones