Bug 477841 - libvirt generates a boot=on in disc option, win2k won't boot with I/O error.
Summary: libvirt generates a boot=on in disc option, win2k won't boot with I/O error.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 9
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-24 04:41 UTC by roy.anonymous
Modified: 2009-04-20 10:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-20 10:17:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description roy.anonymous 2008-12-24 04:41:57 UTC
Description of problem:
virt-manager will generate a "boot=on" in the command line, win2k guest won't boot with error message of "Disk I/O error: Status = 00000001", It can be boot if the boot=on is removed manually by not using the virt-manager.

Version-Release number of selected component (if applicable):
libvirt 0.5.1-2.fc9
libvirt-python 0.5.1-2.fc9
python-virtinst 0.400.0-1.fc9
virt-manager 0.6.0-1.fc9 
No problem in previous version below.
libvirt 0.4.2-1.fc9
libvirt-python 0.4.2-1.fc9
python-virtinst 0.300.3-5.fc9
virt-manager 0.5.4-3.fc9

How reproducible:
upgrade the version of to the version below
libvirt 0.5.1-2.fc9
libvirt-python 0.5.1-2.fc9
python-virtinst 0.400.0-1.fc9
virt-manager 0.6.0-1.fc9 

Steps to Reproduce:
1. Install win2k in old version
2. update to latest version of virt-manager
3. won't boot
OR 
1. update to latest version of virt-manager
2. install win2k
3. won't boot
  
Actual results:


Expected results:


Additional info:

Comment 1 Cole Robinson 2009-01-23 17:54:17 UTC
Hmm, this is an issue at the libvirt level.

Can you provide the following:

versions of qemu and kvm
virsh dumpxml vmname
/var/log/libvirt/qemu/vmname.log

Thanks

Comment 2 Mark McLoughlin 2009-04-20 10:17:41 UTC
Missing info from reporter, closing


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