12:57 p.m.
Hi,
I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
Result from building virt-p2v boot disk:
# virt-p2v-make-disk -o /dev/sde --arch i686
virt-p2v-make-disk: cannot find /usr/lib64/virt-p2v/virt-p2v.i686.xz
You used the '--arch' option, so it’s likely that you will need to build
a virt-p2v.i686 binary yourself.
See p2v-building(1) section BUILDING i686 32 BIT VIRT-P2V for help.
It seems as virt-p2v.i686.xz blob isn't in Fedora (nor 'p2v-building'
man page, but it can be found easily).
What now? I see two possibilities:
1) it is somewhere on Fedora, but not in core repos
2) I have to build it myself - but have no idea about optimal way.
'p2v-building' man page recommends 32-bit chroot (without details),
or (on Fedora) use 'mock' - but it seems it is not there anymore.
Has anyone done this? What optimal way would you recommend?
---
TIA, Franta Hanzlik
1:14 p.m.
On Sun, Feb 26, 2023 at 1:58 PM Franta Hanzlik via users
<users(a)lists.fedoraproject.org> wrote:
I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
Result from building virt-p2v boot disk:
# virt-p2v-make-disk -o /dev/sde --arch i686
virt-p2v-make-disk: cannot find /usr/lib64/virt-p2v/virt-p2v.i686.xz
You used the '--arch' option, so it’s likely that you will need to build
a virt-p2v.i686 binary yourself.
See p2v-building(1) section BUILDING i686 32 BIT VIRT-P2V for help.
It seems as virt-p2v.i686.xz blob isn't in Fedora (nor 'p2v-building'
man page, but it can be found easily).
What now? I see two possibilities:
1) it is somewhere on Fedora, but not in core repos
2) I have to build it myself - but have no idea about optimal way.
'p2v-building' man page recommends 32-bit chroot (without details),
or (on Fedora) use 'mock' - but it seems it is not there anymore.
Has anyone done this? What optimal way would you recommend?
Fedora 37 and its encouragement to drop some (not all) i686 support
may be related: https://bugzilla.redhat.com/show_bug.cgi?id=2069738
Jeff
2:34 p.m.
On Sun, 26 Feb 2023 14:14:32 -0500
Jeffrey Walton <noloader(a)gmail.com> wrote:
On Sun, Feb 26, 2023 at 1:58 PM Franta Hanzlik via users
<users(a)lists.fedoraproject.org> wrote:
>
> I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
> Result from building virt-p2v boot disk:
>
> # virt-p2v-make-disk -o /dev/sde --arch i686
> virt-p2v-make-disk: cannot find /usr/lib64/virt-p2v/virt-p2v.i686.xz
> You used the '--arch' option, so it’s likely that you will need to build
> a virt-p2v.i686 binary yourself.
> See p2v-building(1) section BUILDING i686 32 BIT VIRT-P2V for help.
>
> It seems as virt-p2v.i686.xz blob isn't in Fedora (nor 'p2v-building'
> man page, but it can be found easily).
>
> What now? I see two possibilities:
> 1) it is somewhere on Fedora, but not in core repos
> 2) I have to build it myself - but have no idea about optimal way.
> 'p2v-building' man page recommends 32-bit chroot (without details),
> or (on Fedora) use 'mock' - but it seems it is not there anymore.
>
> Has anyone done this? What optimal way would you recommend?
Fedora 37 and its encouragement to drop some (not all) i686 support
may be related: https://bugzilla.redhat.com/show_bug.cgi?id=2069738
Jeff
What I now found, last package for i686 arch was
virt-p2v-maker-1.40.2-4.fc30.i686.rpm (F30 was likely last i686
Fedora distro?). It is not look good. Maybe I should switch my virtual
host to F30 or some other distro with i686 spport.
But - now I don't know if I understand this correctly - Windows XP PC
is old, with Core2 Duo E6300(a)1.86GHz CPU and 2 GB RAM (can be
increased at least to 4 GB), but IMO HW is 64-bit capable - maybe
is possible convert this 32-bit WinXP system when booting 64-bit F37
'virt-p2v' boot disk?
---
Franta Hanzlik
2:20 p.m.
On Sun, Feb 26, 2023 at 1:58 PM Franta Hanzlik via users
<users(a)lists.fedoraproject.org> wrote:
I want to virtualize any old i686 Windows XP 32-bit physical PC on
F37.
[...issues trying to use virt-p2v...]
Has anyone done this? What optimal way would you recommend?
I've never used virt-p2v - do you really need the --arch option? I
would expect your 32-bit Windows to run just fine in a 64-bit VM.
Another possibility would be to create a 64-bit VM, and then move the
storage to a 32-bit VM (assuming you can't just change the VM
architecture).
If you are willing to do the p2v steps by hand (it isn't hard):
Assuming your Fedora and Windows systems are separate computers (i.e.
not dual-booting), you have an external USB disk that has enough free
space to hold the data from the Windows XP system, and a way to boot a
clonezilla Live CD or USB on the Windows XP system:
- boot clonezilla on the Windows system and let it walk you through
creating an image of the Windows disk
-- do not connect the USB drive until clonezilla tells you to do so
- move the USB disk to the Fedora system
- create the VM but skip the auto-install steps
- boot clonezilla in the VM and let it walk you through restoring the disk image
-- you may need to tell virtual-machine-manager to pass the USB disk
through to the VM
If you insist on using virt-p2v you might have to see if there is a
Live CD for an older version of Fedora that still has it (assuming it
ever did).
3:39 p.m.
On Sun, 26 Feb 2023 15:20:28 -0500
Go Canes <letsgonhlcanes0(a)gmail.com> wrote:
On Sun, Feb 26, 2023 at 1:58 PM Franta Hanzlik via users
<users(a)lists.fedoraproject.org> wrote:
> I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
[...issues trying to use virt-p2v...]
> Has anyone done this? What optimal way would you recommend?
I've never used virt-p2v - do you really need the --arch option? I
would expect your 32-bit Windows to run just fine in a 64-bit VM.
Another possibility would be to create a 64-bit VM, and then move the
storage to a 32-bit VM (assuming you can't just change the VM
architecture).
I've never worked with virt-p2v, but all the tutorials I found
on the internet used it...
If you are willing to do the p2v steps by hand (it isn't hard):
Assuming your Fedora and Windows systems are separate computers (i.e.
not dual-booting), you have an external USB disk that has enough free
space to hold the data from the Windows XP system, and a way to boot a
clonezilla Live CD or USB on the Windows XP system:
WinXP system has two SATA disks, 1 TB + 500 GB. Windows uses only one
partition on each disk, and this partition are big, but contain little
data (850 GB partition with 10 GB data, and 400 GB partition with 85 GB
of data). There are also other partitions, which I probably don't need
(Acer? PQSERVICE partition + some recovery partition + partition from
other system).
I want to reduce the partitions used by the WinXP to some reasonably
small size before virtualization (hope gparted on some rescue disc
will be capable do it).
- boot clonezilla on the Windows system and let it walk you through
creating an image of the Windows disk
-- do not connect the USB drive until clonezilla tells you to do so
- move the USB disk to the Fedora system
- create the VM but skip the auto-install steps
- boot clonezilla in the VM and let it walk you through restoring the disk image
-- you may need to tell virtual-machine-manager to pass the USB disk
through to the VM
I used the program several times many years ago and I hardly know it
anymore. But isn't possible then use ntfsclone, or only dd partition
-> image file ?
I'm worried about booting, I don't know if it's possible to boot directly
from the partition, or if the entire disk structure (especially the MBR)
has to be.
If you insist on using virt-p2v you might have to see if there is a
Live CD for an older version of Fedora that still has it (assuming it
ever did).
---
Thanks, Franta
6:48 a.m.
On Sun, Feb 26, 2023 at 07:57:39PM +0100, Franta Hanzlik via users wrote:
Hi,
I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
Result from building virt-p2v boot disk:
# virt-p2v-make-disk -o /dev/sde --arch i686
virt-p2v-make-disk: cannot find /usr/lib64/virt-p2v/virt-p2v.i686.xz
You used the '--arch' option, so it’s likely that you will need to build
a virt-p2v.i686 binary yourself.
See p2v-building(1) section BUILDING i686 32 BIT VIRT-P2V for help.
It seems as virt-p2v.i686.xz blob isn't in Fedora (nor 'p2v-building'
man page, but it can be found easily).
What now? I see two possibilities:
1) it is somewhere on Fedora, but not in core repos
2) I have to build it myself - but have no idea about optimal way.
'p2v-building' man page recommends 32-bit chroot (without details),
or (on Fedora) use 'mock' - but it seems it is not there anymore.
Has anyone done this? What optimal way would you recommend?
You don't need a 32 bit virt-p2v to virtualize a 32 bit system,
just use normal 64 bit virt-p2v.
Having said that, virt-v2v won't give you any real value for Windows
XP. We don't have virtio drivers for it. Even after using p2v/v2v on
it, it will still use very slow IDE emulated devices. This is not to
say that virt-p2v won't work, it should do, but you might as well
simply copy the physical disk of the PC, eg. by pulling it out and
using a SATA-USB adapter.
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
3:43 p.m.
On 2/27/23 04:48, Richard W.M. Jones wrote:
On Sun, Feb 26, 2023 at 07:57:39PM +0100, Franta Hanzlik via users
wrote:
> Hi,
>
> I want to virtualize any old i686 Windows XP 32-bit physical PC on F37.
> Result from building virt-p2v boot disk:
>
> # virt-p2v-make-disk -o /dev/sde --arch i686
> virt-p2v-make-disk: cannot find /usr/lib64/virt-p2v/virt-p2v.i686.xz
> You used the '--arch' option, so it’s likely that you will need to build
> a virt-p2v.i686 binary yourself.
> See p2v-building(1) section BUILDING i686 32 BIT VIRT-P2V for help.
>
> It seems as virt-p2v.i686.xz blob isn't in Fedora (nor 'p2v-building'
> man page, but it can be found easily).
>
> What now? I see two possibilities:
> 1) it is somewhere on Fedora, but not in core repos
> 2) I have to build it myself - but have no idea about optimal way.
> 'p2v-building' man page recommends 32-bit chroot (without details),
> or (on Fedora) use 'mock' - but it seems it is not there anymore.
>
> Has anyone done this? What optimal way would you recommend?
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.
8:17 p.m.
On Feb 27, 2023, at 16:43, Samuel Sieb <samuel(a)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.
--
Jonathan Billings
11 p.m.
On 2/27/23 18:17, Jonathan Billings wrote:
On Feb 27, 2023, at 16:43, Samuel Sieb <samuel(a)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.
8:31 p.m.
On Feb 28, 2023, at 00:01, Samuel Sieb <samuel(a)sieb.net> wrote:
On 2/27/23 18:17, Jonathan Billings wrote:
> On Feb 27, 2023, at 16:43, Samuel Sieb <samuel(a)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:
https://www.libguestfs.org/virt-p2v-make-disk.1.html#bit-virt-p2v
Might be easier to just pull the disks and dump the disks to a file.
--
Jonathan Billings
419
days inactive
422
days old
9 comments
7 participants
participants (7)
-
Franta Hanzlik -
Franta Hanzlík
-
Go Canes -
Jeffrey Walton -
Jonathan Billings -
Richard W.M. Jones -
Samuel Sieb