| Summary: | Fails to boot Windows guest when the second empty disk is xvda | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Rita Wu <rwu> | ||||
| Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.7 | CC: | cwei, leiwang, mbooth, mkenneth, mrezanin, mshao, rjones, xen-maint, yuzhang | ||||
| Target Milestone: | rc | Keywords: | Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-19 10:04:58 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | 692034 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
This problem is caused by incorrect patch for 692034. Fixed version was posted. Closing this as duplicate. *** This bug has been marked as a duplicate of bug 692034 *** |
Created attachment 492853 [details] Screen Shot of boot failure Description of problem: Virt-manager will still order the second disk from "a" when adding the other disk with different disk type. That will cause Windows guest boot fails. disk = [ "file:/var/lib/xen/images/8-win2k3-64b-50G.img,hda,w", "file:/var/lib/xen/images/8-win2k3-64b-disk2.img,xvda,w" ] Version-Release number of selected component (if applicable): kernel-xen-2.6.18-257.el5 xen-3.0.3-128.el5 libvirt-0.8.2-18.el5 virt-manager-0.6.1-13.el5 How reproducible: always Steps to Reproduce: 1.#qemu-img create -f raw 8-Win7-32-50G-disk2.img 4G 2.Add the above disk with "Virtual Disk" type to a Windows guest Hardware tab=>Storage=>Select the disk you created in step1 and select Device type as "Virtual Disk" 3. Run guest Actual results: Virt-manager will set the second virtual disk as 'xvda', which will cause "No bootable Device" Expected results: Windows guest boot successfully. Additional info: Edit the second disk as "xvdb" can let the guest boot successfully.