Date: Thu, 13 Sep 2012 13:18:56 -0600 From: Peter Grehan <grehan@freebsd.org> To: Roman Bogorodskiy <novel@FreeBSD.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory Message-ID: <505231A0.1070304@freebsd.org> In-Reply-To: <20120913161247.GA1671@kloomba> References: <20120815155222.GA46502@kloomba> <20120819191127.GA1733@kloomba> <5031C58C.40108@freebsd.org> <20120820133613.GA1701@kloomba> <50324270.9040504@freebsd.org> <20120902164750.GA3721@kloomba> <20120902165648.GB3721@kloomba> <CAPS9%2BStBftj=q7cki8i%2BRpQmTvU9hKpS4w8aqDCqHSAnx-eSow@mail.gmail.com> <20120909182811.GB8000@kloomba> <504E779A.4020006@freebsd.org> <20120913161247.GA1671@kloomba>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ? later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?505231A0.1070304>