From: Oguz Bektas <1925496@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1925496] Re: nvme disk cannot be hotplugged after removal
Date: Mon, 26 Apr 2021 09:31:30 -0000 [thread overview]
Message-ID: <161942949105.11882.16762340478099415627.malone@wampee.canonical.com> (raw)
In-Reply-To: 161909487037.10022.905940620153099238.malonedeb@wampee.canonical.com
BTW Re: Regression, I think it's not, because this didn't work a year
ago either, but I wasn't sure if it's a bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1925496
Title:
nvme disk cannot be hotplugged after removal
Status in QEMU:
Confirmed
Bug description:
Hello,
When I try to re-add an nvme disk shortly after removing it, I get an
error about duplicate ID.
See the following commands to reproduce. This happens consistently on
all VMs that I tested:
attach
==========
$VAR1 = {
'arguments' => {
'command-line' => 'drive_add auto "file=/dev/zvol/rpool/data/vm-20000-disk-1,if=none,id=drive-nvme1,format=raw,cache=none,aio=native,detect-zeroes=on"'
},
'execute' => 'human-monitor-command'
};
$VAR1 = {
'execute' => 'device_add',
'arguments' => {
'serial' => 'nvme1',
'drive' => 'drive-nvme1',
'driver' => 'nvme',
'id' => 'nvme1'
}
};
detach
===========
$VAR1 = {
'arguments' => {
'id' => 'nvme1'
},
'execute' => 'device_del'
};
$VAR1 = {
'execute' => 'human-monitor-command',
'arguments' => {
'command-line' => 'drive_del drive-nvme1'
}
};
reattach
===========
$VAR1 = {
'arguments' => {
'command-line' => 'drive_add auto "file=/dev/zvol/rpool/data/vm-20000-disk-1,if=none,id=drive-nvme1,format=raw,cache=none,aio=native,detect-zeroes=on"'
},
'execute' => 'human-monitor-command'
};
and I get:
"Duplicate ID 'drive-nvme1' for drive"
although it does not show up in query-block or query-pci anymore after
the first detach.
Is this a bug or am I missing something? Please advise.
Best regards,
Oguz
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1925496/+subscriptions
next prev parent reply other threads:[~2021-04-26 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 12:34 [Bug 1925496] [NEW] nvme disk cannot be hotplugged after removal Oguz Bektas
2021-04-22 12:55 ` [Bug 1925496] " Klaus Jensen
2021-04-22 13:38 ` Oguz Bektas
2021-04-22 14:24 ` Klaus Jensen
2021-04-26 9:31 ` Oguz Bektas [this message]
2021-04-28 7:38 ` Klaus Jensen
2021-04-28 9:31 ` Oguz Bektas
2021-04-28 10:12 ` Klaus Jensen
2021-04-28 13:00 ` Max Reitz
2021-05-03 7:27 ` Klaus Jensen
2021-05-11 7:37 ` Hannes Reinecke
2021-05-18 4:32 ` Thomas Huth
2021-06-16 14:54 ` 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=161942949105.11882.16762340478099415627.malone@wampee.canonical.com \
--to=1925496@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.