Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 895399 - Fail to boot win7 guest with x-data-plane=on for the system disk
Fail to boot win7 guest with x-data-plane=on for the system disk
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.4
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Stefan Hajnoczi
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-15 02:56 EST by Sibiao Luo
Modified: 2013-11-21 01:29 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-21 01:29:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1553 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2013-11-20 16:40:29 EST

  None (edit)
Description Sibiao Luo 2013-01-15 02:56:01 EST
Description of problem:
this issue was separated from https://bugzilla.redhat.com/show_bug.cgi?id=877836#c27
If specify the x-data-plane=on for the system disk, it will fail to boot up with error that 'A disk read error occurred'.

Version-Release number of selected component (if applicable):
host info:
kernel-2.6.32-348.el6.x86_64
qemu-kvm-0.12.1.2-2.345.el6.test.x86_64
guest info:
win7 64bit
virtio-win-1.5.4-1

How reproducible:
100%

Steps and results:
If specify the x-data-plane=on for the system disk, it will fail to boot up with error that 'A disk read error occurred', the detail log will be pasted as following:
eg:...-drive file=/home/windows_7_ultimate_sp1_x64.raw,if=none,id=drive-virtio-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x4,scsi=off,x-data-plane=on,drive=drive-virtio-disk,id=virtio-disk,bootindex=1...

Google, Inc.
Serial Graphics Adapter 07/26/11
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (mockbuild@hs20-bc2-3.build.redhat.com) Tue Jul 26 15:05:08 UTC 2011
4 0

SeaBIOS (version seabios-0.6.1.2-26.el6)

gPXE (http://etherboot.org) - 00:05.0 CB00 PCI2.10 PnP BBS PMM7FE0@10 CB00
Press Ctrl-B to configure gPXE (PCI 00:05.0)...main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.077000 ms, bitrate 9266968325 bps (8837.669683 Mbps)
inputs_connect: inputs channel client create
red_dispatcher_set_cursor_peer: 
                                                                               
Press F12 for boot menu.

Select boot device:

1. Virtio disk PCI:0:4           <---------select 1
2. Virtio disk PCI:0:6
3. Floppy [drive A]
4. DVD/CD [ata1-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
5. gPXE (PCI 00:05.0)
6. Legacy option rom

Booting from Hard Disk...

A disk read error occurred
Press Ctrl+Alt+Del to restart

Expected results:
it can boot win7 guest with x-data-plane=on for the system disk successfully.

Additional info:
Comment 1 Stefan Hajnoczi 2013-01-15 08:46:18 EST
Please try this build, it includes Windows patches:

https://brewweb.devel.redhat.com/taskinfo?taskID=5273068
Comment 2 Ademar Reis 2013-01-15 09:53:53 EST
Hopefully a dupe of Bug 895392. If not, we'll probably have to wait until RHEL6.5 to fix it (unless Stefan has a trivial patch that can be reviewed and included tomorrow, in snapshot 4).
Comment 3 Stefan Hajnoczi 2013-02-04 10:54:15 EST
(In reply to comment #1)
> Please try this build, it includes Windows patches:
> 
> https://brewweb.devel.redhat.com/taskinfo?taskID=5273068

Ping.

Please confirm that Windows 7 boot works now.
Comment 4 Sibiao Luo 2013-02-04 22:19:04 EST
(In reply to comment #3)
> (In reply to comment #1)
> > Please try this build, it includes Windows patches:
> > 
> > https://brewweb.devel.redhat.com/taskinfo?taskID=5273068
> 
> Ping.
> 
> Please confirm that Windows 7 boot works now.
this build (qemu-kvm-0.12.1.2-2.351.el6.test.src.rpm, x86_64) was deleted, so i have to try this issue with the latest version qemu-kvm-0.12.1.2-2.355.el6.x86_64.

host info:
kernel-2.6.32-358.el6.x86_64
qemu-kvm-0.12.1.2-2.355.el6.x86_64
guest info:
win7 64bit
virtio-win-1.6.2-1.el6

steps:
the same as comment #0

qemu-kvm command line:
# /usr/libexec/qemu-kvm -M rhel6.4.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -usb -device usb-tablet,id=input0 -name data-plane -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x3 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port2 -drive file=/home/windows_7_ultimate_sp1_x64.raw,if=none,id=drive-virtio-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x4,scsi=off,x-data-plane=on,drive=drive-virtio-disk,id=virtio-disk,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=virtio-net-pci0,mac=BC:96:9D:05:51:EC,bus=pci.0,addr=0x5 -balloon none -spice port=5931,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -boot menu=on -monitor stdio

results:
it can boot win7 guest with x-data-plane=on for the system disk successfully, no  any error like 'A disk read error occurred'.

Press F12 for boot menu.

Select boot device:

1. Virtio disk PCI:0:4           <---------select it
2. Floppy [drive A]
3. DVD/CD [ata1-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
4. gPXE (PCI 00:05.0)
5. Legacy option rom

Booting from Hard Disk...

It can boot up susccessfully without any error.
Comment 11 errata-xmlrpc 2013-11-21 01:29:22 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1553.html

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