Bug 475789

Summary:	[RHEL5.4]: xm passes wrong device type for block-detach with TAP devices
Product:	Red Hat Enterprise Linux 5	Reporter:	Daniel Berrangé <berrange>
Component:	xen	Assignee:	Michal Novotny <minovotn>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.3	CC:	areis, berrange, ddutile, syeghiay, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-11 11:39:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***