OK,
well after a couple of hours of running 'valgrind' on a massive
piece of code I have had no problem at all.
Maybe something has change - but it is not in libvirt/kvm, there
have been no fedora changes there in the last few days. Unless it is the
guest, but that seems unlikely - it should not be allowed out!
Bill
William John Murray wrote:
Hi Mark,
Yes, you are correct. Trouble is it is a pig to do. I have to
actually use the machine
to generate a hang, and when I do who knows what it costs me.
But I'll try.
Would you think virt-manager is the culprit? I see nothing
suspicious in the log file
there. Or kvm? or libvirt?
Bill
Mark McLoughlin wrote:
> Hi Bill,
>
> On Tue, 2009-03-10 at 20:58 +0100, William Murray wrote:
>
>> Hello there,
>> I have a VM installed in Fedora 10 with the virt-manager
>> gui. Its
>> great! I love the fact I can mount disks so guest and host can both
>> see them.
>> But..I created it with 1-2GB ram (from my total 4), and it defaults
>> to 1GB.
>> That works. If I increase it to 2 I start to see weird crashes in
>> the host.
>>
>> How can I migrate this system to having always 2GB please?
>> ---and safely!
>>
>
> If this hasn't already been sorted out, please file a bug against the
> kvm package which as many details as possible. See:
>
>
https://fedoraproject.org/wiki/Reporting_virtualization_bugs
>
> Also - the fedora-virt(a)redhat.com list would be more appropriate.
>
> Thanks,
> Mark.
>
>