RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1334340 - the guest is crashed/rebooted during multiple attempts of disk addition
Summary: the guest is crashed/rebooted during multiple attempts of disk addition
Keywords:
Status: CLOSED DUPLICATE of bug 1318181
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: ppc64le
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Laurent Vivier
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-09 12:18 UTC by shajyan
Modified: 2016-10-04 04:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 15:43:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description shajyan 2016-05-09 12:18:16 UTC 
trying to attach a virtual disk image, after the 2nd attempt the guest is crashed/rebooted.

The disk.xml contains:

<?xml version='1.0' encoding='UTF-8'?>
<disk type="file"><driver name="qemu" type="raw" /><source file="/tmp/tmp_disk.raw" /><target bus="virtio" dev="vdb" /></disk>

the /tmp/tmp_disk.raw exists.


virsh attach-device avocado-vt-vm1 disk.xml
Device attached successfully


Before attaching the disk there are the following devices on the guest:

ls -ld /dev/vd*
brw-rw---- 1 root disk 252, 0 Mai  4 09:39 /dev/vda
brw-rw---- 1 root disk 252, 1 Mai  4 09:39 /dev/vda1
brw-rw---- 1 root disk 252, 2 Mai  4 09:39 /dev/vda2
brw-rw---- 1 root disk 252, 3 Mai  4 09:39 /dev/vda3

After attaching:

ls -ld /dev/vd*
brw-rw---- 1 root disk 252,  0 Mai  4 09:39 /dev/vda
brw-rw---- 1 root disk 252,  1 Mai  4 09:39 /dev/vda1
brw-rw---- 1 root disk 252,  2 Mai  4 09:39 /dev/vda2
brw-rw---- 1 root disk 252,  3 Mai  4 09:39 /dev/vda3
brw-rw---- 1 root disk 252, 16 Mai  4 09:39 /dev/vdb

The /dev/vdb is a new one. Seems everything is correct here. Then after deleting the new vdb from the guest we have the following layout:

ls -ld /dev/vd*
brw-rw---- 1 root disk 252, 0 Mai  4 09:39 /dev/vda
brw-rw---- 1 root disk 252, 1 Mai  4 09:39 /dev/vda1
brw-rw---- 1 root disk 252, 2 Mai  4 09:39 /dev/vda2
brw-rw---- 1 root disk 252, 3 Mai  4 09:39 /dev/vda3

Then after adding the same disk to the guest for the 2nd time the guest is crashed/rebooted again and the new layout looks like: (/dev/vda is the added disk)

ls -ld /dev/vd*
brw-rw---- 1 root disk 252,  0 Mai  4 09:40 /dev/vda
brw-rw---- 1 root disk 252, 16 Mai  4 09:40 /dev/vdb
brw-rw---- 1 root disk 252, 17 Mai  4 09:40 /dev/vdb1
brw-rw---- 1 root disk 252, 18 Mai  4 09:40 /dev/vdb2
brw-rw---- 1 root disk 252, 19 Mai  4 09:40 /dev/vdb3


qemu version:
qemu-kvm-common-rhev-2.5.0-4.el7.ppc64le
qemu-kvm-rhev-2.5.0-4.el7.ppc64le
qemu-kvm-tools-rhev-2.5.0-4.el7.ppc64le
qemu-img-rhev-2.5.0-4.el7.ppc64le

kernel version:
3.10.0-373.el7.ppc64le #1 SMP Tue Apr 5 19:12:32 EDT 2016 ppc64le ppc64le ppc64le GNU/Linux
Comment 1 shajyan 2016-05-09 12:32:38 UTC 
Probably can be related to hot-unplug disk BZ 1318181
Comment 3 Thomas Huth 2016-05-11 08:55:56 UTC 
Could this be a bug with qemu-kvm-rhev-2.5.0 only? I gave it a quick try with version 2.3.0, and I was not able to reproduce the crash. Then I had a try with 2.5.0, and my guest crashed, too. Then I upgraded to qemu-kvm-rhev-2.6.0-rc0, and the crash did not occur anymore.
Comment 5 shajyan 2016-05-11 09:57:40 UTC 
Thanks. Probably it could be a qemu-kvm-rhev bug. Later on I will test with your 2.6 build to see how it works in my case.
Comment 6 Laurent Vivier 2016-05-11 10:45:29 UTC 
I'm going to bisect qemu to find what is the fixing commit.
Comment 7 Laurent Vivier 2016-05-11 12:17:42 UTC 
upstream qemu-2.5.0 works fine whereas qemu-kvm-rhev-2.5.0 doesn't.
Comment 10 shajyan 2016-05-17 11:26:59 UTC 
I have now the recent qemu-kvm-rhev-2.6.0-2.el7.ppc64le built today.. and the guest crash/bug still exists..
Comment 13 shajyan 2016-05-18 06:58:21 UTC 
Thanks

I tried with those packages and still the guest is being crashed... maybe there could be something else which causes such an effect?
Note You need to log in before you can comment on or make changes to this bug.