BHyVe: vm_setup_memory(highmem): Cannot allocate memory
Roman Bogorodskiy
novel at FreeBSD.org
Sat Sep 15 08:56:51 UTC 2012
Peter Grehan wrote:
> Hi Roman,
>
> > When I was seing this 'Failed to emulate instruction at
> > 0xffffffff80594f3a', it happened right after boot loader menu (the one
> > with the ascii-art). At that time I had 'hw.physmem="0x180000000"' in my
> > host's loader.conf. Also the problem wasn't 100% reproducible, it
> > started to show up after creating/destroying several VMs.
>
> OK - I'm now wondering if this is a guest phys memory leak in the
> hypervisor, and it's not reporting the error correctly.
>
> How many times do you have to create/destroy vm's for this to occurr ?
I'm writing some sort of automation scripts so I created and destroy vms
quite often, I guess maybe 20 times or so...
BTW, any ideas why I stared loosing a console after:
GDB: debug ports: bvm
GDB: current port: bvm
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
?
Roman Bogorodskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-virtualization/attachments/20120915/150c6777/attachment.pgp
More information about the freebsd-virtualization
mailing list