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

[Todd Wasson]

Hi Bakul.  I tried changing max_locked_pages, as well as lowering  
hw.physmem to 2GB and in the dmesg it printed "kqemu: KQEMU installed,  
max_locked_mem=524284kB."

I ran qemu with -m 256 after all of this, and it still hung in the  
same spot.  Argh.  I'm not sure if I should just keep arbitrarily  
lowering it and praying, or what.  My filesystems keep getting trashed  
though thanks to the hanging, so I'm not inclined to take that path  
unless I have to...  Any other ideas?

Thanks for your help so far, I really appreciate it.


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.