Bug 1230304 - F22 guest installation on F21 host fails
Summary: F22 guest installation on F21 host fails
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-10 15:16 UTC by Vivek Goyal
Modified: 2015-12-02 18:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 13:37:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace output of dd command (4.71 KB, text/plain)
2015-06-10 15:27 UTC, Vivek Goyal
no flags Details

Description Vivek Goyal 2015-06-10 15:16:56 UTC
Description of problem:

I am trying to install F22 guest on F21 host and it fails. Primary source of the problem is that writes to /dev/vda inside guest are failing. I have tried
doing dd of one block on /dev/vda device and I can see in strace output that fsync failed with error "Input/output error". (-EIO).

Trying to create a partition on /dev/vda fails in similar manner. 

I am opening this bug against kernel component but I got a suspicion that
it has something to do with qemu/libvirt on host.

Version-Release number of selected component (if applicable):



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vivek Goyal 2015-06-10 15:25:14 UTC
I ran following command in guest.

[root@localhost ~]# strace -o strace-dd-fsync-output.txt dd if=/dev/zero of=/dev/vda bs=4K count=1 conv=fsync
dd: fsync failed for \u2018/dev/vda\u2019: Input/output error
1+0 records in
1+0 records out
4096 bytes (4.1 kB) copied, 0.0184981 s, 221 kB/s


And I see following message from kernel in guest.

Jun 10 11:24:05 localhost kernel: blk_update_request: I/O error, dev vda, sector 0
Jun 10 11:24:05 localhost kernel: Buffer I/O error on dev vda, logical block 0, lost async page write

Comment 2 Vivek Goyal 2015-06-10 15:27:21 UTC
Created attachment 1037347 [details]
strace output of dd command

Comment 3 Vivek Goyal 2015-06-10 15:28:07 UTC
Attached strace output of dd command. Following snippet shows that fsync failed.

read(0, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
fsync(1)                                = -1 EIO (Input/output error)

Comment 4 Kevin Wolf 2015-06-11 07:54:47 UTC
Can you please post the strace of the qemu-kvm process on the host? You will need
to use -f to trace all threads, and probably something like -e pwrite,pwritev to
make the output more manageable.

Comment 5 Fedora End Of Life 2015-11-04 11:29:36 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 13:37:51 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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