On Tue, Apr 10, 2007 at 10:09:20PM +0200, Ivan Voras wrote:
> Juergen Lock wrote:
>
> >> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d
> >> -m 512
> >
> > -m 512 ? Hmm did you increase kern.maxdsiz for that? Since the
> > default is 512M, and qemu needs memory for itse
Juergen Lock wrote:
>> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d
>> -m 512
>
> -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 a
In article <[EMAIL PROTECTED]> you write:
>-=-=-=-=-=-
>
>Ivan Voras wrote:
>> Juergen Lock wrote:
>>> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote:
>>
Good advice, except that qemu-system-x86_64 locks up the machine hard,
no autoreboot.
>>>
>>> Ouch! But only with kqemu I
In article <[EMAIL PROTECTED]> you write:
>-=-=-=-=-=-
>
>Juergen Lock wrote:
>> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote:
>
>>> Good advice, except that qemu-system-x86_64 locks up the machine hard,
>>> no autoreboot.
>>
>> Ouch! But only with kqemu I guess? Also, whats your g
Ivan Voras wrote:
> Juergen Lock wrote:
>> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote:
>
>>> Good advice, except that qemu-system-x86_64 locks up the machine hard,
>>> no autoreboot.
>>
>> Ouch! But only with kqemu I guess? Also, whats your guest and args
>> to qemu-system-x86_64
RW wrote:
Would you expect to able to run kqemu, when the architecture is
different between the host and guest?
Yes, I'd expect it to translate and fixup the instructions. (Why?
"VMware does it" :) ).
The point of kqemu is that some instructions in the guest can be run
natively on the host
Juergen Lock wrote:
On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote:
Good advice, except that qemu-system-x86_64 locks up the machine hard,
no autoreboot.
Ouch! But only with kqemu I guess? Also, whats your guest and args
to qemu-system-x86_64?
Yes, it works without kqemu load
On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote:
> Juergen Lock wrote:
> > In article <[EMAIL PROTECTED]> you write:
> >> -=-=-=-=-=-
> >>
> >> I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386
> >> FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info
Juergen Lock wrote:
> In article <[EMAIL PROTECTED]> you write:
>> -=-=-=-=-=-
>>
>> I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386
>> FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info
>> kqemu" command in qemu reports "kqemu not compiled". But it should be
In article <[EMAIL PROTECTED]> you write:
>-=-=-=-=-=-
>
>I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386
>FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info
>kqemu" command in qemu reports "kqemu not compiled". But it should be -
>the KQEMU option is active
On Fri, 06 Apr 2007 13:05:41 +0200
Ivan Voras <[EMAIL PROTECTED]> wrote:
> I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386
> FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info
> kqemu" command in qemu reports "kqemu not compiled". But it should be
> - the KQ
I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386
FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info
kqemu" command in qemu reports "kqemu not compiled". But it should be -
the KQEMU option is active on the port and the "configure" step in the
port reports "k
12 matches
Mail list logo
