Bug 638962
Summary: | [6.0] 'virsh start' succeeds even if an invalid domain is configured to an xml file. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sadique Puthen <sputhenp> |
Component: | libvirt | Assignee: | Osier Yang <jyang> |
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | ccui, dallan, dyuan, eblake, mzhan, 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: | 2011-03-01 16:42:23 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
Sadique Puthen
2010-09-30 13:54:59 UTC
virsh does not enforce the XML schema for permissible domain names. However, the XML schema needs to be very broad to encompass all possible valid names across all hypervisors, and the validity of the name should be enforced by the hypervisor driver or the hypervisor. IMO, the bug is that the domain.rng is too restrictive, as "#" may be a valid name for some hypervisors. I'm closing this bz as a duplicate of 639599, and we can discuss the proper behavior there. BTW, it's perfectly correct for virt-manager to enforce a stricter definition of what's a valid name. *** This bug has been marked as a duplicate of bug 639599 *** |