From: Mohammad Heib <1867519@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1867519] Re: qemu 4.2 segfaults on VF detach
Date: Wed, 18 Mar 2020 11:28:31 -0000 [thread overview]
Message-ID: <158453091148.28539.11460365760222230930.malone@gac.canonical.com> (raw)
In-Reply-To: 158428174672.11238.3583143675239092561.malonedeb@soybean.canonical.com
Hi Christian,
yes that exactly what we see in our tests,
so are the logs that you asked for in comment#1 still needed?
also if you fix it can you please provide us a link for a package or even a workaround until the issue resolved, since this issue stuck our QA from testing ASAP over Focal.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1867519
Title:
qemu 4.2 segfaults on VF detach
Status in QEMU:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
After updating Ubuntu 20.04 to the Beta version, we get the following
error and the virtual machines stucks when detaching PCI devices using
virsh command:
Error:
error: Failed to detach device from /tmp/vf_interface_attached.xml
error: internal error: End of file from qemu monitor
steps to reproduce:
1. create a VM over Ubuntu 20.04 (5.4.0-14-generic)
2. attach PCI device to this VM (Mellanox VF for example)
3. try to detaching the PCI device using virsh command:
a. create a pci interface xml file:
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address type='pci' domain='0x0000' bus='0x11' slot='0x00' function='0x2' />
</source>
</hostdev>
b. #virsh detach-device <VM-Doman-name> <pci interface xml file>
- Ubuntu release:
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
- Package ver:
libvirt0:
Installed: 6.0.0-0ubuntu3
Candidate: 6.0.0-0ubuntu5
Version table:
6.0.0-0ubuntu5 500
500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages
*** 6.0.0-0ubuntu3 100
100 /var/lib/dpkg/status
- What you expected to happen:
PCI device detached without any errors.
- What happened instead:
getting the errors above and he VM stuck
additional info:
after downgrading the libvirt0 package and all the dependent packages to 5.4 the previous, version, seems that the issue disappeared
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1867519/+subscriptions
next prev parent reply other threads:[~2020-03-18 11:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <158428174672.11238.3583143675239092561.malonedeb@soybean.canonical.com>
2020-03-18 11:19 ` [Bug 1867519] Re: libvirt 6.0 : virtual machine stuck when detaching PCI device using virsh command Christian Ehrhardt
2020-03-18 11:21 ` [Bug 1867519] Re: qemu 4.2 segfaults on VF detach Christian Ehrhardt
2020-03-18 11:28 ` Mohammad Heib [this message]
2020-03-18 11:37 ` Christian Ehrhardt
2020-03-18 11:40 ` Christian Ehrhardt
2020-03-18 11:46 ` Daniel Berrange
2020-03-18 15:49 ` Mohammad Heib
2020-03-19 9:01 ` Christian Ehrhardt
2020-03-19 9:08 ` Launchpad Bug Tracker
2020-03-20 6:28 ` Christian Ehrhardt
2020-03-20 16:39 ` Launchpad Bug Tracker
2020-03-23 11:41 ` Launchpad Bug Tracker
2020-03-23 11:45 ` Christian Ehrhardt
2020-03-24 9:28 ` Launchpad Bug Tracker
2020-03-25 5:59 ` Christian Ehrhardt
2020-03-26 13:00 ` Launchpad Bug Tracker
2020-08-20 15:39 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=158453091148.28539.11460365760222230930.malone@gac.canonical.com \
--to=1867519@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.