Bug 680879 - Remove -net smb=$dir option or mark it unsupported in --help and man page
Summary: Remove -net smb=$dir option or mark it unsupported in --help and man page
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Markus Armbruster
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-28 10:04 UTC by David Jaša
Modified: 2013-01-09 23:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-01 13:13:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2011-02-28 10:04:38 UTC 
Description of problem:
Related to bug Bug 680463 - if the feature isn't supported, it should be clearly marked as such or it shouldn't be included at all.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.147.el6.x86_64
Comment 2 Dor Laor 2011-02-28 22:28:51 UTC 
Markus, I'm sure this was reported by the 6.0 big release note bug.
Can you check if we're done it and close this one in this case?
Comment 3 Markus Armbruster 2011-03-01 13:13:55 UTC 
Direct use of qemu-kvm is unsupported.  The only supported use is via libvirt.  There is no way to configure the built-in SMB server via libvirt. Therefore it is clearly unsupported.

Shipping unsupported features in the product is suboptimal, but can't always be avoided.  We do need to make "supportedness" as obvious as we can.

Cutting unsupported stuff completely (code & docs) is best, but as I said, it's not always feasible.  If we have to leave the code in place, then we should leave the documentaion in place as well. Withholding documentation is not a good way to communicate unsupportedness, in my opinion.

Closing NOTABUG.  If you disagree with my reasoning, feel free to reopen the bug and explain why you think I'm wrong.
Note You need to log in before you can comment on or make changes to this bug.