| Summary: | lxc guest with operating system container can not be login with no network interface | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | tingting zheng <tzheng> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | acathrow, ajia, berrange, codong, dyuan, hyao, lcui, lsu, mzhan, zsong |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-11 10:40:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
tingting zheng
2013-12-11 07:27:15 UTC
If you are running a full operating system in LXC, you *must* have a private network namespace either by adding an <interface> or by requesting a new namespace with
<features>
<privnet/>
</features>
(In reply to Daniel Berrange from comment #1) > If you are running a full operating system in LXC, you *must* have a private > network namespace either by adding an <interface> or by requesting a new > namespace with > > <features> > <privnet/> > </features> If I create a lxc guest running a full operating system from virt-manager,then dump the xml file of the guest,there is no such namespace in xml file,does virt-manager need to add it to xml? Yes, that is a virt-manager issue. |