FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to create a QEMU/KVM for a fedora virtual machine using Virtual Machine Manager v 0.4.0.
Step 1. Create a new fully virtualized with x86_64 architecture amd hardware acceleration ticked
Step 2. Use DVD drive with OS Type Linux and OS Variant Fedora 7
Step 3. Use a Simple File for the storage space which is allocated and formated OK
Step 4. Use Virtual Network selection with default
Step 5. Use 2048 MB of a possible 4096 MB an 1 of a possible 2 cpu's
Step 6. Click finish and get the following message:
Unable to complete install: 'virDomainCreateLinux() failed QEMU quit during console startup
Unable to complete install '<class 'libvirt.libvirtError'> virDomainCreateLinux() failed QEMU quit during console startup
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 681, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 710, in start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 563, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: virDomainCreateLinux() failed QEMU quit during console startup
Any ideas anyone??
Last edited by lighthouse; 09-17-2007 at 10:43 AM.
Reason: adding tags
It seems that the maximum amount of memory that QEMU support is 2047MB so once I reduced the max memory to 2000MB everything was sweet. I would have thought simple validation of the maximum memory when running the wizard to create a VM would't be that hard. Oh well - alls well that ends well!!
I got the same error but with F8 on a 32 bit machine, 4G of RAM available and I specified 512 for the VM. I dropped it back to 256 and it worked. It may work with a higher value, but I guess there's a relationship between x86, 86_64 and max RAM in VM that I don't know about.
I've got the same error after finishing creating the vm in F9 on a Dell PowerEdge 2850 which is a 64 bit platform but do not have virtualization support in CPU. I used the same config as lighthouse and reducing the memory to less than 2048 solved my problem.
Interesting is that this vm ran perfectly on PowerEdge 2950 (which has CPU virtualization support in BIOS), but we decided to move it to a less used server. After recreating the machine with the same disk we got into trouble. I haven't tried a BIOS update yet for 2850 ...
So ... think this issue is also platform dependent, but reducing the memory should do the trick.