Bug 697455 - Fails to boot Windows guest when the second empty disk is xvda
Summary: Fails to boot Windows guest when the second empty disk is xvda
Keywords:
Status: CLOSED DUPLICATE of bug 692034
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.7
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 692034
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-18 10:55 UTC by Rita Wu
Modified: 2013-07-03 01:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-19 10:04:58 UTC
Target Upstream Version:


Attachments (Terms of Use)
Screen Shot of boot failure (19.78 KB, image/png)
2011-04-18 10:55 UTC, Rita Wu
no flags Details

Description Rita Wu 2011-04-18 10:55:17 UTC
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.

Comment 2 Miroslav Rezanina 2011-04-19 10:04:58 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.