kqemu locking my machine hard on amd64 smp, with most recent patches

[Todd Wasson]

Yes, it was on this same system, configured in exactly the same with,  
with the same image.  I tried it again with 1.3.0.p11_4 and it still  
works, so I tried it with 1.3.0.p11_5.  That worked too.  The problem  
must be in 1.3.0.p11_6.

The command line I've been using is "qemu-system-x86_64 -hda test.img - 
net nic -net tap -localtime -m 1536 -vnc :2 -usbdevice tablet -soundhw  
es1370,pcspk".

I've tried running without ZFS (I unloaded the module), sound, and  
networking and it still crashes.  I enabled the debugging sysctl and  
just saw a lot of kqemu_vmalloc_to_phys calls before it crashed.  I  
haven't started playing with max_locked_mem yet, but will do so if  
narrowing it down specifically to the changes between 1.3.0.p11_5 and  
1.3.0.p11_6 isn't helpful enough.  The main reason I'm hesitant is  
that repeatedly crashing my box is rather undesirable and problematic  
for me, but I will resort to this if I can't learn more in another way.

Thanks for your help.


Todd


On May 15, 2008, at 4:09 AM, Bakul Shah wrote:

> When you said an earlier kqemu version worked, was it on the same
> hardware, with the same amount of memory and 7.0 release?  For the
> same image?  Can you try it again to see if it still works?
>
> Can you show the exact qemu command line?
>
> Some more things to try:
>
> In your earlier response I see
>> kqemu version 0x00010300
>> kqemu: KQEMU installed, max_locked_mem=3134224kB.
>
> This makes me wonder if the amount of max_locked_mem is the
> problem.  To test this, change kqemu-freebsd.c:554 to
>
>        max_locked_pages = MIN(physmem / 2, 0x1fffffff / PAGE_SIZE);
>
> This will allocate no more than 512B for max locked pages.
> If this works keep doubling the size until it breaks.
>
> You can enable kqemu debug prints by
>
>    sysctl debug.kqemu_debug=1
>
> before starting qemu.  May be we will find something unusual there.
>
> To rule out audio you can disable it from the qemu command line.
>
> If you can, remove zfs during testing.