Bug 994280 - lxc application container creation from virt-manager fails
Summary: lxc application container creation from virt-manager fails
Keywords:
Status: CLOSED DUPLICATE of bug 982317
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-07 00:26 UTC by Dimitris
Modified: 2013-08-07 08:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-07 08:59:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dimitris 2013-08-07 00:26:44 UTC
Description of problem:

I was able to create a trivial lxc application container exactly once with virt-manager.  After deleting that, trying again results in an error at the end of the creation process.

Version-Release number of selected component (if applicable):

libvirt.x86_64 1.0.5.4-1.fc19
libvirt-daemon.x86_64 1.0.5.4-1.fc19

How reproducible:
Always, after the first successful time.

Steps to Reproduce:
1. Start virt-manager
2. Select the lxc:/// connection
3. Click on "Create new virtual machine" button
4. Select "Application container", named "test" or whatever
5. Click "Forward", leave the default "/bin/sh"
6. Click "Forward", leave the defaults: 1024MB, 1 CPU
7. Click "Forward"

Actual results:

8. Popup window, details:
Unable to complete install: 'internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=0e9d9df2-f498-8740-43ba-0de546ab493b LIBVIRT_LXC_UUID=0e9d9df2-f498-8740-43ba-0de546ab493b LIBVIRT_LXC_NAME=test /bin/sh
error receiving signal from container: Input/output error

'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1920, in do_install
    guest.start_install(False, meter=meter)
  File "/usr/share/virt-manager/virtinst/Guest.py", line 1134, in start_install
    noboot)
  File "/usr/share/virt-manager/virtinst/Guest.py", line 1202, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2782, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=0e9d9df2-f498-8740-43ba-0de546ab493b LIBVIRT_LXC_UUID=0e9d9df2-f498-8740-43ba-0de546ab493b LIBVIRT_LXC_NAME=test /bin/sh
error receiving signal from container: Input/output error

9. In the log:
Aug 06 17:22:38 gaspode libvirtd[3108]: Cannot recv data: Connection reset by peer
Aug 06 17:22:38 gaspode libvirtd[3108]: [282B blob data]
Aug 06 17:22:38 gaspode libvirtd[3108]: Cannot get interface flags on 'veth0': No such device
Aug 06 17:22:38 gaspode libvirtd[3108]: [102B blob data]
Aug 06 17:22:38 gaspode libvirtd[3108]: [102B blob data]


Expected results:
running shell

Additional info:
SELinux is enforcing.

Comment 1 Daniel Berrangé 2013-08-07 08:59:54 UTC
Libvirt 1.0.5.4-1.fc19 is fubar - use  1.0.5.5-1.fc19 which just hit stable updates.

*** This bug has been marked as a duplicate of bug 982317 ***


Note You need to log in before you can comment on or make changes to this bug.