On Feb 11, 2013, at 11:09 , Ricky <rockybaloo(a)gmail.com> wrote:
Hi Michael,
I think I have missunderstod something deeply.
After my reinstall of the hypervisors I got "The guest virtual machine
cannot be started: internal error guest CPU is not compatible with
host CPU" when trying to run a VM. So I found the Fake package and
after I have restarted vdsmd on the hypervisor Webadmin report
"Intel(Fake) CPU" and the VM started, but just with 15-20MB RAM.
Hi,
well, fake package is for something totally different. It won't allow you to run
anything, it's there for testing purposes only, you won't be able to run a VM.
Please try to uninstall it (at worst reinstall the node:-)
Then you should see a proper reporting again. Are you sure your Cluster is having the
compatible CPU type? Please attach the new logs once the hypervisor is without the
"fake" packageā¦
Thanks,
michal
So what I want to do is to start my VMs on the same hardware they
always have been on. :-)
My hypervisors are equipped AMD Opteron G3.
mvh //Ricky
2013/2/11 Michal Skrivanek <michal.skrivanek(a)redhat.com>:
>
> On Feb 10, 2013, at 20:18 , Rocky <rockybaloo(a)gmail.com> wrote:
>
>> Hi,
>>
>> Today after I reinstalled my hypvervisors I just got 15MB of RAM inside
>> my guests. I hade this problem on one of my hypervisors before but if I
>> started the VMs on the other hypervisors and then migrate the VM to the
>> "faulty" hypervisor all was ok. Just because of that behavior I then
>> started to reinstall my hypervisors today.
>>
>> I am using Centos 6.3 with Dreyous 3.1 repo.
>>
>> After the install i enabled and installed the Intel(Fake) CPU-package on
>> all of the hypervisors.
> VMs are not supposed to work with fake virtualization.
> Fake VMs are started with 20MB total memory.
>
> What are you trying to achieve? Why did you install the fake virt package?
>
>>
>> Now when Im trying to start a VM I only got 15MB of RAM inside the WM,
>> almost impossible to boot of course.
>>
>> One of the machines is definied to use 2048MB and has 2048MB as
>> "guaranteed memory".
>>
>> I have attached the vdsm.log from the hypervisor that the VM try to
>> start on.
>>
>> Regards //Ricky
>>
>> <vdsm_15MB.log>_______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>