Hi,

On Wed, Oct 25, 2023 at 04:44:18PM -0000, Michaal R via Users wrote:
> I checked for the Fast Startup feature, which I figured wouldn't be enabled, 
> and it's not even configurable.

it really seems the VM imports below got a step further.

> 
> I tried, again, to import from vCenter and got error "All chosen VMs couldn't 
> be retrieved by the external system and therefore have been filtered. Please 
> see log for details." When I look at the log, there's nothing there 
> referencing the error. Not even sure I'm looking in the right place.
> 
> I fired up the VM, double verified Fast Startup was disabled, shut down the 
> VM again, and exported it as an OVF (folder of files). Tried to import as 
> Windows 2019 x64, same error as before ("Cannot import VM. Invalid time zone 
> for given OS type."). Tried to import as Other OS, failed, event ID 1153. I 
> get the below error log from the import log:
> 
> { "message": "Copying disk 1/1", "timestamp": 
> "2023-10-25T10:49:56.302914729-05:00", "type": "message" }
> [ 222.2] Copying disk 1/1
> protocol: newstyle-fixed without TLS, using structured packets
> export="":
>       export-size: 214748364800 (200G)
>       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

I don't think this is a problem. virt-v2v properly detected that it is
Windows 10 what is installed in the VM.

>       uri: nbd+unix:///?socket=/tmp/v2v.qObfRy/in0
>       contexts:
>               base:allocation
>       is_rotational: false
>       is_read_only: false
>       can_cache: true
>       can_df: true
>       can_fast_zero: true
>       can_flush: true
>       can_fua: true
>       can_multi_conn: true
>       can_trim: true
>       can_zero: true
>       block_size_minimum: 1
>       block_size_preferred: 4096
>       block_size_maximum: 33554432
> 
> And this from the vdsm.log file right around when the import log ends:
> 
> 2023-10-25 10:54:07,224-0500 ERROR (v2v/e81442fd) [root] Job 
> 'e81442fd-04fc-4100-b9a1-7e0938164397' failed (v2v:851)
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
>     self._import()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
>     self._watch_process_output()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
> _watch_process_output
>     for event in parser.parse(out):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
>     for chunk in self._iter_progress(stream):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 963, in 
> _iter_progress
>     raise OutputParserError('copy-disk stream closed unexpectedly')
> vdsm.v2v.OutputParserError: copy-disk stream closed unexpectedly

This is the real problem. VDSM is confused because virt-v2v changed
output format and progress reporting looks different now. VDSM is still
waiting for progress update even though virt-v2v is already copying
data. And when virt-v2v terminates VDSM reports this error and aborts
the operation.

I could perhaps try creating a patch for that. But I don't have an
environment to test it.

    Tomas
> 
> 
> Tried importing as Other Linux. Failed, event ID 1153. Import log has below 
> snippet (much like above):
> export="":
>       export-size: 214748364800 (200G)
>       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
>       uri: nbd+unix:///?socket=/tmp/v2v.kRmHY0/in0
>       contexts:
>               base:allocation
>       is_rotational: false
>       is_read_only: false
>       can_cache: true
>       can_df: true
>       can_fast_zero: true
>       can_flush: true
>       can_fua: true
>       can_multi_conn: true
>       can_trim: true
>       can_zero: true
>       block_size_minimum: 1
>       block_size_preferred: 4096
>       block_size_maximum: 33554432
> 
> vdsm.log shows below:
> 
> 2023-10-25 11:25:58,100-0500 ERROR (v2v/542ae3e4) [root] Job 
> '542ae3e4-8ea8-4f85-a35f-30bc702b8d5d' failed (v2v:851)
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
>     self._import()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
>     self._watch_process_output()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
> _watch_process_output
>     for event in parser.parse(out):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
>     for chunk in self._iter_progress(stream):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 963, in 
> _iter_progress
>     raise OutputParserError('copy-disk stream closed unexpectedly')
> vdsm.v2v.OutputParserError: copy-disk stream closed unexpectedly
> 
> Not sure what's going on, since the folder that the OVF is accessible from is 
> an SMB mount in /mnt/ (mount dir: /mnt/vmexports). It's mounted rw, even, in 
> case it needs it, and the uid:gid is set 36:36.
> 
> Below are links to the screenshot of the directory listing for the mount 
> point, as well as the vdsm and import logs. Something's not clicking with me, 
> and it may just be that I've been wrestling with this issue for so long that 
> my brain's gotten clouded. Thanks for the help, guys.
> 
> vmexports mount directory listing: 
> https://1drv.ms/i/s!AuIX1bquDpYsgYYw8d8IuBkXqE3uTA?e=1gsyib
> vdsm.log: 
> https://www.dropbox.com/scl/fi/t35er0ixcelpljgx1wfoc/vdsm.log?rlkey=y77wh93dk5uovj3ayreovybpp&dl=0
> first import log: 
> https://www.dropbox.com/scl/fi/n67lauq1tdl3xo6tjyezf/import-e81442fd-04fc-4100-b9a1-7e0938164397-20231025T104614.log?rlkey=prjhgfezkp5q714l6x0ayvvnk&dl=0
> second import log: 
> https://www.dropbox.com/scl/fi/bcc3fvsczx485sixznpgq/import-542ae3e4-8ea8-4f85-a35f-30bc702b8d5d-20231025T111827.log?rlkey=fswiuq3k9wshmxv4sdw4zxd2c&dl=0
> _______________________________________________
> 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/ED66XYYI7NO6HKOPUSZIRWQAOEKO2BKD/
_______________________________________________
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/A4REURB32JQVUZCDW7P6IIO7Y4Z2OECF/

Reply via email to