Unable to complete install: 'internal error unable to start guest: char device redirected to /dev/pts/4

Bug #521428 reported by Lacyc3
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Ubuntu 10.04 - Lucid
virt-manager 0.8.2-2ubuntu2

I tried to create a new virtual machine. At the last step, it can't create a vpc.

##
Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: char device redirected to /dev/pts/4
qemu: could not open disk image /var/lib/libvirt/images/ipcop.img: No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1435, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 660, in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/pymodules/python2.6/virtinst/Guest.py", line 758, in _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1097, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error unable to start guest: char device redirected to /dev/pts/4
qemu: could not open disk image /var/lib/libvirt/images/ipcop.img: No such file or directory'
##

ProblemType: Bug
Architecture: i386
CheckboxSubmission: c2e4a82d008774657bfd8cf42c962d44
CheckboxSystem: da9af3b901b5569a389df6337f3d812f
Date: Sat Feb 13 18:12:50 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/libvirtd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
NonfreeKernelModules: nvidia
Package: libvirt-bin 0.7.5-5ubuntu7
ProcEnviron:
 LANG=hu_HU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: libvirt
Uname: Linux 2.6.32-13-generic i686

Revision history for this message
Lacyc3 (lacyc3) wrote :
Revision history for this message
Mathias Gug (mathiaz) wrote :

The error is:

qemu: could not open disk image /var/lib/libvirt/images/ipcop.img: No such file or directory'

Could you outline the actual steps and options taken to create the vm in virt-manager?

What ipcop.img?

Changed in libvirt (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
affects: libvirt (Ubuntu) → virt-manager (Ubuntu)
Revision history for this message
Lacyc3 (lacyc3) wrote :

@Mathias: ipcop is a router linux distribution, and the ipcop.img is the virtual disk.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Hi,

Could you please give steps on how we can reproduce this issue?

Changed in virt-manager (Ubuntu):
assignee: nobody → Lacyc3 (lacyc3)
Revision history for this message
Lacyc3 (lacyc3) wrote :

Hi,

yes of course. I documented with screenshots: http://gallery.lacyc3.eu/main.php?g2_itemId=737

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Please make sure your user is in the libvirtd group, and try it again while connecting to "localhost (QEMU)" instead of "localhost (QEMU Usermode)".

Revision history for this message
Lacyc3 (lacyc3) wrote :

There is no bug if i connect to "localhost (QEMU)", only at Qemu usermode.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Well, that's your problem. The "localhost (QEMU Usermode)" attempts to run the VM with your user permissions, which do not have write access to the /var/lib/libvirt/images directory.

You need to either continue using "localhost (QEMU)", which would be my recommendation, or create your virtual machine in your home directory someplace.

I'm closing this bug. Feel free to reopen it if you feel this is still an issue.

Changed in virt-manager (Ubuntu):
status: Incomplete → Invalid
assignee: Lacyc3 (lacyc3) → nobody
Revision history for this message
Lacyc3 (lacyc3) wrote :

I'm sorry becouse i wasted your time. Thank you for your help, time and kindliness! :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.