From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Inform users about busy device assignment attempt
Date: Wed, 9 Dec 2009 18:19:56 +0000 [thread overview]
Message-ID: <20091209181956.GA13487@redhat.com> (raw)
In-Reply-To: <1260381853-8954-1-git-send-email-agraf@suse.de>
On Wed, Dec 09, 2009 at 07:04:13PM +0100, Alexander Graf wrote:
> When using -pcidevice on a device that is already in use by a kernel driver
> all the user gets is the following (very useful) information:
>
> Failed to assign device "04:00.0" : Device or resource busy
> Failed to deassign device "04:00.0" : Invalid argument
> Error initializing device pci-assign
>
> Since I usually prefer to have my computer do the thinking for me, I figured
> it might be a good idea to check and see if a device is actually used by a
> driver. If so, tell the user.
>
> So with this patch applied you get the following output:
>
> Failed to assign device "04:00.0" : Device or resource busy
> *** The driver 'igb' is occupying your device 04:00.0.
> *** Try running "rmmod igb" on the commandline
> Failed to deassign device "04:00.0" : Invalid argument
> Error initializing device pci-assign
>
> That should keep people like me from doing the most obvious misuses :-).
Unconditionally telling people to run rmmod is a pretty dangerous thing
todo. If they typod and gave the PCI addr of their disk controller instead
of the NIC, they'll be less than happy at the results of our recommended
command to "fix" the error. Likewise if they have multiple devices using
the same driver & just want to assign one of them. I think it is safer to
just have the first bit of your proposed error message
"The device 04:00.0 is in use by the kernel driver 'igb'."
NB 'rmmod' is not the ideal approach for PCI assignment. It is better
to explicitly re-bind the device to 'pcistub' because that ensures that
no other driver will ever be able to reclaim the device.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-12-09 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 18:04 [PATCH] Inform users about busy device assignment attempt Alexander Graf
2009-12-09 18:19 ` Daniel P. Berrange [this message]
2009-12-09 19:18 ` Alexander Graf
2009-12-09 19:40 ` Daniel P. Berrange
2009-12-09 19:44 ` Alexander Graf
2009-12-09 20:14 ` Daniel P. Berrange
2009-12-09 20:15 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 20:13 Alexander Graf
2009-12-10 23:06 [PATCH] Enable non page boundary BAR device assignment Alexander Graf
2009-12-10 23:06 ` [PATCH] Inform users about busy device assignment attempt Alexander Graf
2009-12-11 11:38 ` Michael S. Tsirkin
2009-12-15 15:18 ` Alexander Graf
2009-12-15 15:18 ` Michael S. Tsirkin
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=20091209181956.GA13487@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--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 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.