Guys, please do not panic. virt-v2v output is full of messages and
combindes unprocessed output of various tools virt-v2v uses to do the
operation. You might even see errors there which are pretty normal and
expected.
You can tell virt-v2v properly discovered your guest OS for example by
this lines:
libguestfs: trace: v2v: inspect_get_format "/dev/sda4"
ct_name: Windows Server 2019 Datacenter
product_variant: Server
version: 10.0
arch: x86_64
hostname: ******
build ID: 17763
or this line:
guestfsd: => inspect_glibguestfs: trace: v2v: inspect_get_product_name =
"Windows Server 2019 Datacenter"
Which are from the inspection phase. Or you can see that in the final
OVF it generated on exit:
<Section ovf:id='75636d68-d067-4570-84b3-3829c5cf1963' ovf:required='false'
xsi:type='ovf:OperatingSystemSection_Type'>
<Info>Windows Server 2019 Datacenter</Info>
<Description>windows_2019x64</Description>
</Section>
On Thu, Oct 26, 2023 at 09:31:52PM +0000, Simon Coter wrote:
> It’s failing due to this error:
>
> import-75636d68-d067-4570-84b3-3829c5cf1963-20231026T153906.log: content:
> DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid
> partition
> table" at offset 0x17b "Error loading operating system" at offset 0x19a
> "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2),
> end-CHS
> (0x1fb,254,63), startsector 1, 4294967295 sectors
Now to clarify this. This message (and those around like export-size,
uri, etc.) come from nbdkit which is the tool that handles copying the
data from VMware. It does not need to know and does not even care what
is on the disk. Yet it is trying to interpret what's inside. It can tell
there is MBR boot sector and that there are some strings. First strings
that it could find are "Invalid partition table", "Error loading
operating system" and "Missing operating system". This is expected
because those strings belong to the bootloader. It is something you
might see if your OS failed to start. But in this context it is not
relevant at all. Nbdkit might as well say there is a string "Alice has
an apple." and the importance of the message would be the same.
Tomas
>
> So, “virt-v2v” is not able to get your Windows-7 disk mounted to load the OS.
>
> Simon
>
>
> On Oct 26, 2023, at 11:23 PM, Michaal R via Users <users@ovirt.org> wrote:
>
> Okay, it seems it got a bit further, but still errored out. I watched it
> get past the disk import (or what looked like the disk import), but I
> couldn't see
> in the vdsm.log file where it failed the remaining import. I tried as
> both Other OS and as Linux (just in case the latter had a chance), but still
> failures. There were errors from vdsmd like "cannot lookup default
> selinux label for /var/tmp/.guestfs-36/appliance.d/initrd" and some SELinux
> errors with
> access control from qemu-kvm (the latter of which I ran the fix scripts
> for as suggested by Cockpit). Below are the log file links from this run.
>
> vdsm.log:
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/aylya0u16l55ef8k36qu8/vdsm-10.26.23-15.37.log?rlkey=mawo0smdau51ja4a042bhsrqi&dl=
>
> 0__;!!ACWV5N9M2RV99hQ!NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQb_maUM6w$
> import log 1:
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/xuwslr1sz9lrvbyhacasa/
>
> import-75636d68-d067-4570-84b3-3829c5cf1963-20231026T153906.log?rlkey=kned3464ek7ctsggqddix0dsi&dl=0__;!!ACWV5N9M2RV99hQ!
>
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQZjHc7hRg$
> import log 2:
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/yuimr3j0hwdpkz4siofum/
>
> import-4a6237d9-05a0-4d5a-a7b1-ff01764a761f-20231026T155635.log?rlkey=y6kp8ttd59sbh0j8k16eauvsw&dl=0__;!!ACWV5N9M2RV99hQ!
>
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQb2bdYygQ$
> import log 3:
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/ipeol7uk00gimyn6rgfrg/
>
> import-44bb07d9-fb1d-4e91-a025-35dc70b55cd8-20231026T160749.log?rlkey=yrrznpyagxhhgkwqsokgmk09z&dl=0__;!!ACWV5N9M2RV99hQ!
>
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYrVJ_ATw$
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement:
> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!ACWV5N9M2RV99hQ!
>
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYZUcAT1w$
> oVirt Code of Conduct:
> https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!ACWV5N9M2RV99hQ!
>
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYpOT8vxg$
> List Archives:
> https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/WRNUCEDMDKUACQZPELZJAL6GAOR27XVE/__;!!
>
> ACWV5N9M2RV99hQ!NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQbwRSBMCQ$
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SWTLWSVQKZ3ASBWNN37XGYU4JF3OZQQ7/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7IJGIITK5BICSXUTKKWTKLXM4C5U6XBZ/
