Back to bug 1375563
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-09-13 12:13:29 UTC | Keywords | FutureFeature | |
| Flags | testing_ack? planning_ack? | |||
| Nisim Simsolo | 2016-09-13 12:16:17 UTC | CC | nsimsolo | |
| Gil Klein | 2016-09-13 12:31:22 UTC | CC | gklein | |
| Severity | unspecified | medium | ||
| Michal Skrivanek | 2016-09-14 07:21:18 UTC | Flags | ovirt-future? | |
| Tomas Jelinek | 2016-09-15 07:21:32 UTC | CC | tjelinek | |
| Assignee | michal.skrivanek | shavivi | ||
| Target Milestone | --- | ovirt-4.1.0-alpha | ||
| Flags | ovirt-4.1.0? | |||
| Red Hat Bugzilla Rules Engine | 2016-09-15 07:21:37 UTC | Flags | ovirt-future? | |
| meital avital | 2016-11-17 06:56:38 UTC | QA Contact | mavital | nsimsolo |
| Yaniv Lavi | 2016-12-08 14:39:29 UTC | Target Milestone | ovirt-4.1.0-alpha | ovirt-4.1.0-beta |
| Shahar Havivi | 2016-12-14 12:46:03 UTC | Status | NEW | MODIFIED |
| Doc Text | 1. create an export domain 2. run the command: $ virt-v2v-copy-to-local -ic xen+ssh://root@xenserver.com vmname this will copy the files locally. 3. run the command: virt-v2v -i libvirtxml vmname.xml -o rhev -of raw -os servername:/path/to/export/domain 4. the VM should be present in your export domain, now you can import it to a data domain. |
|||
| meital avital | 2016-12-19 12:43:08 UTC | CC | mavital | |
| Flags | testing_plan_complete+ | |||
| Lucy Bopf | 2017-01-17 05:42:40 UTC | Status | MODIFIED | ON_QA |
| CC | shavivi | |||
| Flags | needinfo?(shavivi) | |||
| Shahar Havivi | 2017-01-17 07:38:47 UTC | Doc Type | If docs needed, set a value | Release Note |
| Flags | needinfo?(shavivi) | |||
| Tahlia Richardson | 2017-01-23 06:43:29 UTC | CC | trichard | |
| Doc Text | 1. create an export domain 2. run the command: $ virt-v2v-copy-to-local -ic xen+ssh://root@xenserver.com vmname this will copy the files locally. 3. run the command: virt-v2v -i libvirtxml vmname.xml -o rhev -of raw -os servername:/path/to/export/domain 4. the VM should be present in your export domain, now you can import it to a data domain. | Currently, virtual machines with block devices cannot be imported from Xen to Red Hat Virtualization using the Administration Portal. This release adds a workaround to manually import Xen virtual machines with block devices: 1. Create an export domain. 2. Run the following command to copy the files locally: $ virt-v2v-copy-to-local -ic xen+ssh://root@xenserver.com vmname 3. Run the following command to convert the virtual machine to libvirt XML: $ virt-v2v -i libvirtxml vmname.xml -o rhev -of raw -os servername:/path/to/export/domain 4. The virtual machine should now appear in your export domain, and can be imported to a data domain. |
||
| Tahlia Richardson | 2017-01-23 06:46:28 UTC | Blocks | 1415582 | |
| Nisim Simsolo | 2017-01-25 09:28:42 UTC | Depends On | 1416112 | |
| Nisim Simsolo | 2017-02-14 10:02:26 UTC | Status | ON_QA | VERIFIED |
| Red Hat Bugzilla Rules Engine | 2017-02-14 10:02:31 UTC | Flags | testing_ack? | testing_ack+ |
| Sandro Bonazzola | 2017-02-15 14:58:40 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-02-15 09:58:40 UTC |
Back to bug 1375563