Bug 1133452
| Summary: | Failed to detect bootable device in cloned vm from snapshot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Raz Tamir <ratamir> | ||||
| Component: | ovirt-engine-core | Assignee: | Omer Frenkel <ofrenkel> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | bugs, ecohen, gklein, iheim, michal.skrivanek, ofrenkel, ratamir, rbalakri, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-11-02 11:25:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
i could not reproduce this, what is the boot order for the original vm, and for the cloned vm? also, what is the output of select device_id,type,device,boot_order,is_managed,is_plugged,d.boot,d.shareable from vm_device left join base_disks d on d.disk_id=device_id where vm_id='xxx'; for original vm and for cloned vm? The boot order for the original vm is: PXE HD cd Raz, could you also provide the output of: select device_id,type,device,boot_order,is_managed,is_plugged,d.boot,d.shareable from vm_device left join base_disks d on d.disk_id=device_id where vm_id='xxx'; for original vm and for cloned vm? Original VM:
~~~~~~~~~~~~
device_id | type | device | boot_order | is_managed | is_plugged | boot | shareable
--------------------------------------+------------+---------------+------------+------------+------------+------+-----------
806b0130-fb1e-403d-94ce-b1aee7712f77 | interface | bridge | 0 | t | t | |
eb3e1a3c-3989-4340-a250-47d8a40ed967 | disk | cdrom | 0 | t | t | |
2c06c447-17b4-42e1-adca-362600f5d839 | controller | virtio-scsi | 0 | t | t | |
4e1e6e8c-04dd-40e3-9eba-d85434274892 | disk | disk | 1 | t | t | t | f
7d01fc42-7edf-464c-9539-34146af5e224 | video | qxl | 0 | t | t | |
f8a6a658-7be1-4eab-838e-0dfb89a6978c | controller | usb | 0 | f | t | |
1be4971c-232a-4a69-8dad-86bae69c62e7 | controller | ide | 0 | f | t | |
14d4a623-e2e8-48c8-9eaf-f216dcd29792 | controller | virtio-serial | 0 | f | t | |
f8498f8f-fc88-4ba2-9b52-a80d2ca3f127 | channel | unix | 0 | f | t | |
eb95584a-304b-4067-a947-901e14ac5a8f | channel | unix | 0 | f | t | |
b714dea6-c5d5-4405-9997-dbf35ad0a1c2 | channel | spicevmc | 0 | f | t | |
Cloned VM:
~~~~~~~~~~
device_id | type | device | boot_order | is_managed | is_plugged | boot | shareable
--------------------------------------+------------+---------------+------------+------------+------------+------+-----------
ecb06954-5e43-4117-a48a-e44255ae9c6b | interface | bridge | 0 | t | t | |
07bcf9ce-ec39-4794-a5ac-d63acd3c4000 | disk | disk | 1 | t | t | t | f
5c9d5650-d93c-41d6-afcf-5c500c906e14 | video | qxl | 0 | t | t | |
7257df9c-7d6f-4e98-8f6f-bb91a2de213d | controller | virtio-scsi | 0 | t | t | |
7470cf3b-da89-45f1-a12c-c30ad1307c9d | disk | cdrom | 0 | t | t | |
2b11af80-92c9-4f28-b100-5ba914b9bcb1 | controller | usb | 0 | f | t | |
9c03db48-34f1-4e10-a574-2d0bd3e69ade | controller | ide | 0 | f | t | |
c59553ce-597f-48f3-bb0d-5f298cc80e78 | controller | virtio-serial | 0 | f | t | |
6dc82565-e75e-49ce-a238-ae3ef595dd5c | channel | unix | 0 | f | t | |
b536af03-a7b9-4cb2-98f9-06e8beffaa0f | channel | unix | 0 | f | t | |
be4a370f-3580-413f-8a47-d7790426eba7 | channel | spicevmc | 0 | f | t | |
I see three disks in vdsm.log Also the first(bootable) disk in the "cloned" VM is type raw, whereas the original one has qcow2 I wonder if it still reproduces for you on newer builds and/or other setups? If not, well, engine config looks fine and we can't reproduce it since the beginning Any more information about the setup and its history might be relevant... Hi Michal, I can't reproduce this in vt7 closing, please re-open if it reproduce or you have more info |
Created attachment 930357 [details] vdsm and engine logs Description of problem: Setup: 1 vm with OS and snapshot of that vm. When cloning a vm from this snapshot, I expect that the cloned vm will have OS installed. In this case the boot process fails with "No bootable device." Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch vdsm-4.16.2-1.gite8cba75.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. vm with OS 2. create snapshot 3. clone vm from that snapshot 4. run the cloned vm Actual results: "No bootable device." Expected results: The cloned vm should be a clone of the base vm and should detect the bootable device Additional info: