Date: Tue, 10 Apr 2007 22:09:20 +0200 From: Ivan Voras <ivoras@fer.hr> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: freebsd-ports@freebsd.org Subject: Re: qemu: kqemu not compiled? Message-ID: <461BEEF0.8080905@fer.hr> In-Reply-To: <200704102000.l3AK05fR012647@saturn.kn-bremen.de> References: <200704061627.l36GRUwu009926@saturn.kn-bremen.de> <461A9956.3070009@fer.hr> <20070410000436.GB49375@saturn.kn-bremen.de> <200704102000.l3AK05fR012647@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig90853EF6131D4B8F49BEE781 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Juergen Lock wrote: >> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d= =20 >> -m 512 >=20 > -m 512 ? Hmm did you increase kern.maxdsiz for that? Since the > default is 512M, and qemu needs memory for itself too... (tunable > in loader.conf.) Or, failing that, try smaller -m args, like 256. Hmmm. But does the kqemu allocate the memory or the qemu? I've seen big qemu processes, so I conclude that qemu allocates this memory. But you're right - this may be something to try. >> I've now tried both i386 and AMD64 guests, and both panic with kqemu, = >> before kernel gets loaded. >=20 > Oh, panic, not lockup? Can you get a backtrace? (see Sorry, yes, lockup. Always lockup with qemu. --------------enig90853EF6131D4B8F49BEE781 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGG+7wldnAQVacBcgRAq+7AKCnS9M++9Ryf86AQZXmW27MBeW/NgCghEzL KtQefhTAMduW+fdkgjLlnzc= =gSHn -----END PGP SIGNATURE----- --------------enig90853EF6131D4B8F49BEE781--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?461BEEF0.8080905>