Bug 1301334
Summary: | windows 2008 VM run once with sysprep, tries to load from network first. | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Ilanit Stein <istein> | ||||
Component: | Backend.Core | Assignee: | Nobody <nobody> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Ilanit Stein <istein> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.6.2 | CC: | bugs, istein, tjelinek | ||||
Target Milestone: | --- | Flags: | istein:
planning_ack?
istein: devel_ack? istein: testing_ack? |
||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-02-14 08:41:08 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: |
|
Description
Ilanit Stein
2016-01-24 10:39:14 UTC
same happens with windows 2008 R2 (with same flow). could you please attach the engine logs for the relevant part? Created attachment 1120793 [details]
engine log (relevant part is from 2016-02-03 13:48)
Comment on attachment 1120793 [details]
engine log (relevant part is from 2016-02-03 13:48)
The engine.log, starting 2016-02-03 13:48,
contain all steps from create VM from win 2008 R2, then fail to boot from network, disk, and eventually succeed to load with sysprep floppy attached (when removing the virtio nic).
Here a VM was created, and a disk was attached to it, and a nic added. Then the VM was sealed, a template created from it. Another V< let say VM-1, was created from this template (which has a nic) Run once VM-1, with attached floppy [sysprep] My expectation was that VM-1 will try to load from network, fail, and then load from disk, with setup run with the sysprep answer file. What happened was that it failed to load from network, and then failed to load from disk: no bootable disk. It turned out the attached disk wasn't marked as bootable. (There is inconsistency here since 1st attached disk is NOT marked as bootable, by default, while it is for add 1st disk) Based on that, we can close this bug. |