Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> The attached patch should fix it. If you're using the external module,
>>> you'll need to apply with 'patch -p3' in the kernel/ subdirectory.
>>>
>> Thanks a lot, with this patch it's works very well. It boots cor
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> The attached patch should fix it. If you're using the external module,
>> you'll need to apply with 'patch -p3' in the kernel/ subdirectory.
>>
>
> Thanks a lot, with this patch it's works very well. It boots correctly,
> and everything se
Avi Kivity a écrit :
> The attached patch should fix it. If you're using the external module,
> you'll need to apply with 'patch -p3' in the kernel/ subdirectory.
Thanks a lot, with this patch it's works very well. It boots correctly,
and everything seems to work correctly, even with high load.
Aurelien Jarno wrote:
Okay, an mmu bug. Been a while since we've seen one.
Please post a URL for the .iso so I can take a look, along with exact
instructions for reproducing the bug.
I have put a qcow image on http://aurel32.free.fr . You have to bunzip2
the image and then run:
qemu-
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Yep. Here are what I get in my dmesg. The lines below are output when
>> the kernel is started (just after the bootloader):
>>
>> Mar 3 16:50:35 joule kernel: assertion failed
>> /usr/local/src/kvm-15/kernel/mmu.c:722: (gpa & HPA_ERR_MASK) == 0
>> M
Aurelien Jarno wrote:
> Yep. Here are what I get in my dmesg. The lines below are output when
> the kernel is started (just after the bootloader):
>
> Mar 3 16:50:35 joule kernel: assertion failed
> /usr/local/src/kvm-15/kernel/mmu.c:722: (gpa & HPA_ERR_MASK) == 0
> Mar 3 16:50:35 joule kernel:
On Wed, Mar 07, 2007 at 04:34:02PM +0200, Avi Kivity wrote:
> Aurelien Jarno wrote:
> >>>
> >>>
> >>Are you sure you set 'dbg = 0'? There aren't supposed to be any logs,
> >>except if an error is found during audit (that's what the '#define
> >>AUDIT' is for).
> >>
> >>
> >
> >Oh sor
Aurelien Jarno wrote:
>>>
>>>
>> Are you sure you set 'dbg = 0'? There aren't supposed to be any logs,
>> except if an error is found during audit (that's what the '#define
>> AUDIT' is for).
>>
>>
>
> Oh sorry, I did that wrong.
>
> I have tried with dbg = = 0 and #define AUDIT,
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>>> Can you try turning the '#undef AUDIT' to '#define AUDIT' in mmu.c?
>>> Also, change 'int dbg = 1' to 'int dbg = 0' in the same file. Note kvm
>>> will be very slower after this. dmesg will show any issues (issue a
>>> 'echo 9 > /proc/sysrq-tri
Aurelien Jarno wrote:
>> Can you try turning the '#undef AUDIT' to '#define AUDIT' in mmu.c?
>> Also, change 'int dbg = 1' to 'int dbg = 0' in the same file. Note kvm
>> will be very slower after this. dmesg will show any issues (issue a
>> 'echo 9 > /proc/sysrq-trigger' to make sure all mess
On Tue, Feb 27, 2007 at 09:08:50AM +0200, Avi Kivity wrote:
> Aurelien Jarno wrote:
> >Hi all,
> >
> >While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
> >am having problems with running a 32-bit FreeBSD under the same KVM:
> >
> >INIT: version 2.86 booting
> >INIT: PANIC: seg
Aurelien Jarno wrote:
> Hi all,
>
> While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
> am having problems with running a 32-bit FreeBSD under the same KVM:
>
> INIT: version 2.86 booting
> INIT: PANIC: segmentation violation! sleeping for 30 seconds.
> pid 34 (init), uid 0: e
Hi all,
While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I
am having problems with running a 32-bit FreeBSD under the same KVM:
INIT: version 2.86 booting
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
pid 34 (init), uid 0: exited on signal 11
INIT: PANIC: segm
13 matches
Mail list logo
