On Feb 28, 2023, at 00:01, Samuel Sieb <samuel@sieb.net> wrote:
On 2/27/23 18:17, Jonathan Billings wrote:On Feb 27, 2023, at 16:43, Samuel Sieb <samuel@sieb.net> wrote:
On 2/27/23 04:48, Richard W.M. Jones wrote:
You don't need a 32 bit virt-p2v to virtualize a 32 bit system,
just use normal 64 bit virt-p2v.
I was going to say the same thing until I realized that the original system was 32-bit only, so couldn't run the 64-bit p2v. At least that's my understanding from the original post.
x86_64 CPUs are just x86_32 CPUs with a bunch of fancy extra features (to be slightly inaccurate but mostly true). The CPU can drive an x86_32 OS, it just won’t be able to use any of those fancy features.
You have the problem backwards. virt-p2v runs on the source system, so if the source CPU is 32-bit only, then you have to run a 32-bit virt-p2v executable. The resulting VM of course can run on a 64-bit host no money.
I thought we were talking about the resulting VM, because it would be difficult to build a 32-bit p2v when the 64-bit Fedora kernel/userspace can’t boot on a 32-bit only CPU.
I suspect the tool to make the p2v boot disk requires building all the dependencies as 32-bit executables and libraries and most of those are no longer included in Fedora repos. The instructions indicate it would be time consuming:
Might be easier to just pull the disks and dump the disks to a file.