From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 47451] need to re-load driver in guest to make a hot-plug VF work
Date: Thu, 20 Sep 2012 03:36:31 +0000 (UTC) [thread overview]
Message-ID: <20120920033631.78CC311FA61@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-47451-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=47451
--- Comment #2 from Jay Ren <yongjie.ren@intel.com> 2012-09-20 03:36:31 ---
(In reply to comment #1)
> The steps to reproduce don't indicate what you've done in the host to prepare
> the device. Is igbvf loaded in the host?
No, I don't load igbvf driver in host.
>Is the vf attached to igbvf or pci-stub or nothing?
VF is attached to 'pci-stub' in host.
>Can we narrow down the kvm.git commit range at all? The
> one provided is over 12k commits covering v3.4-rc3 to v3.5-rc6. Thanks
I did more testing.
Do you remember the bug #43328 ( VT-d/SR-IOV totally doesn't work in guest)?
Just use your fix commit for that bug, I'll meet this hot-plug issue.
Is there a chance your patch fixed one bug but introduced another one? :)
commit a76beb14123a69ca080f5a5425e28b786d62318d
Author: Alex Williamson <alex.williamson@redhat.com>
Date: Mon Jul 9 10:53:22 2012 -0600
KVM: Fix device assignment threaded irq handler
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-09-20 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 9:21 [Bug 47451] New: need to re-load driver in guest to make a hot-plug VF work bugzilla-daemon
2012-09-14 16:24 ` [Bug 47451] " bugzilla-daemon
2012-09-20 3:36 ` bugzilla-daemon [this message]
2012-09-20 4:36 ` bugzilla-daemon
2012-09-28 6:07 ` bugzilla-daemon
2012-12-10 3:00 ` bugzilla-daemon
2012-12-10 3:00 ` bugzilla-daemon
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=20120920033631.78CC311FA61@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).