Bug 1277738
| Summary: | Error while converting VMware VM - Windows Server 2008 R2 64bit | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alessandro <alfonsi.alex> | |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rawhide | CC: | alfonsi.alex, angelo.lisco, dornelas, ggalloro, juwu, juzhou, mbooth, mzhan, ptoscano, rjones, tzheng, virt-bugs, virt-maint | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Windows | |||
| Whiteboard: | V2V | |||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1190669 | |||
| : | 1277741 (view as bug list) | Environment: | ||
| Last Closed: | 2015-11-05 08:57:28 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1280501 | |||
|
Description
Alessandro
2015-11-03 23:43:03 UTC
> Looks like the tool looks for a "-flat.vmdk" disk that does not exist.
> The only VMDK present in Datastore is "vDiskName_1.vmdk"
That's new to me. What's the actual directory listing
if you visit that through the vCenter web page?
(In reply to Richard W.M. Jones from comment #1) > > Looks like the tool looks for a "-flat.vmdk" disk that does not exist. > > The only VMDK present in Datastore is "vDiskName_1.vmdk" > > That's new to me. What's the actual directory listing > if you visit that through the vCenter web page? The directory name is same as the vm name. I browse the vm's Datastore using the vSphere Client and not through the Web page. Is that a difference from libvirt/virt-v2v prospective? The vm's files look fine and there are no snapshots present, which would explain the -flat.vmdk. The only thing that pops up in my mind as first is that the vm was created using a Template from a vCloud Director environment. I do not know if this can make a difference/create an issue. It would be helpful if you could go to the vCenter webpage, navigate down to the VM, and paste here the VM's directory and all the files in it. Preferably with the URLs of everything too. (In reply to Richard W.M. Jones from comment #3) > It would be helpful if you could go to the vCenter webpage, > navigate down to the VM, and paste here the VM's directory > and all the files in it. Preferably with the URLs of > everything too. I believe this is what you asked for: https://vCenterServerName:9443/vsphere-client/#extensionId=vsphere.core.datastore.manage.filesView;context=com.vmware.core.model%3A%3AServerObjectRef~21F3B6D6-26FB-430E-BA4A-BAF302EBA2F8%3ADatastore%3Adatastore-23633~core This is the URL from the datastore view when clicking on the folder containing the VM's files. Richard, I believe I have found the issue. The vm I was trying to convert was created using the Fast Provisioning method from vCloud Director. SO basically the vm VMDK is a snapshot of a source template vm's VMDK. This is why we see the -flat.vmdk and why Virt-v2v cannot convert the vm. I am asking for a confirmation about this and confirm this to you asap. Thanks! Richard, I confirm to you that the VMDK was a snapshot of a source VM. The vDisk has been consolidated and I have ran the test again, everything works fine now. You can close this case. Thank you! |