Bug 816748

Summary:	virt-manager throws an internal error when trying to create new virtual machine
Product:	[Fedora] Fedora	Reporter:	Jared Smith <jsmith.fedora>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17	CC:	berrange, crobinso, dpierce, hbrock, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-06 20:05:57 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:
Embargoed:

Description Jared Smith 2012-04-26 21:02:13 UTC

Description of problem:

virt-manager throws an internal error when trying to create a new virtual machine.

I get the following message: 

Unable to complete install: 'internal error Process exited while reading console log output: char device redirected to /dev/pts/3
Could not allocate dynamic translator buffer
'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1911, in do_install
    guest.start_install(False, meter=meter)
  File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1239, in start_install
    noboot)
  File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1307, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2397, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/3
Could not allocate dynamic translator buffer

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

virt-manager-0.9.1-2.fc17.noarch
qemu-kvm-1.0-17.fc17.x86_64
libvirt-0.9.11-1.fc17.x86_64


How reproducible:

Very

Steps to Reproduce:
1.  Start virt-manager
2.  Create a new VM
3.  See the error message
  
Actual results:

Pasted above.

Expected results:

A newly created VM

Additional info:

Comment 1 Jared Smith 2012-04-26 21:44:06 UTC

Turns out this was user error on my part -- I didn't have the virtualization extensions turned on in my BIOS.  (Now I feel like an idiot.)

It seems I'm not the only person who has encountered this issue, though.  Would it be possible to have virt-manager probe for the processor extensions, and give a better warning message if it doesn't find them enabled?

Comment 2 Cole Robinson 2012-06-06 20:05:57 UTC

Hmm, we should already be detecting this situation fairly well, and warn about it up front in the New VM wizard.

Jared, if you feel inclined to test, please turn off virt extensions, reboot, and provide the following info:

dmesg
sudo virsh --connect qemu:///system capabilities
cat /proc/cpuinfo

And also the full

/var/log/libvirt/qemu/$vmname.log

After the failed guest creation.

Closing as WORKSFORME until then.