Bug 475789 - [RHEL5.4]: xm passes wrong device type for block-detach with TAP devices
Summary: [RHEL5.4]: xm passes wrong device type for block-detach with TAP devices
Keywords:
Status: CLOSED DUPLICATE of bug 484110
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Michal Novotny
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-10 14:43 UTC by Daniel Berrangé
Modified: 2014-02-02 22:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-11 11:39:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Daniel Berrangé 2008-12-10 14:43:47 UTC 
+++ This bug was initially created as a clone of Bug #473882 +++

There are two core problems with block detach

 - virsh & xm both pass 'type=vbd' even for TAP devices. This causes the wrong device controller to be used. This is the cause of the detach failure. This patch checks for the bogus type=vbd and fixes it

 - The /vm/$UUID/device/{vbd,tap}/$DEVID  path is not removed from xenstore, preventing a later re-attachment. This patch removes that path upon detach




This bug is to track the correct fixing of 'xm' command wrt to type=tap parameter.
Comment 2 Michal Novotny 2009-03-11 11:39:18 UTC 
Well, I've been already solving bug #484110 which appears to be duplicate. If it's not please give me some information about information about the problem.

*** This bug has been marked as a duplicate of bug 484110 ***
Note You need to log in before you can comment on or make changes to this bug.