Bug 372871
| Summary: | [EMC 5.2 bug] virt-manager adds duplicate entries while adding disk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Sadique Puthen <sputhenp> |
| Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> |
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1 | CC: | andriusb, berthiaume_wayne, bjohnson, emcnabb, ogren_chris, pan_haifeng, xen-maint |
| Target Milestone: | --- | Keywords: | OtherQA |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-03 17:19:56 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 217106 | ||
|
Description
Sadique Puthen
2007-11-09 15:24:09 UTC
We have seen this same behavior whereby subsequent guest domain reboots failed with an error that the virtual block device is already connected. The additional virtual block devices were added after the initial domU creation using the virt manager. I manually edited the config file fo rthe guest OS in /etc/xen and was able to restart the domU. Does this also occur if the CLI `xm block-attach` method is used? Or is it strictly manifeted when using virt manager to add block devices? Will this bug be fixed in a patch to RHEL 5.1? This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Further Info: When I did a bit deeper investigation I found that this only happens if someone adds the disk to the guest via virt-manager while the guest is in a running state. If we add the disk while the guest is inactive, it adds the entries correctly. If I add a file based storage while the guest is running, old disk = section is, disk = [ "tap:aio:/vm/sadique/rhel5,xvda,w"] New disk section entry, disk = [ "tap:aio:/vm/sadique/rhel5,xvda,w", "tap:aio:/vm/sadique/disk2,xvdb,w", "tap:aio:/vm/sadique/disk2,xvdb,w"] If I add a block device it would be as below. disk = [ "phy:/dev/sda9,xvdb,w", "tap:aio:/vm/sadique/rhel5,xvda,w", "phy:/dev/sda9,xvdb,w"] Note the order of duplication! If it's block device one entry is added in the beginning and one entry in the last. If it's file backed, both entries are adding in the last. Setting Dev ACK for Dan. |