Gerd Hoffmann writes:
> On Mo, 2015-03-16 at 14:16 -0400, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>> > Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
>> >> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
>> >>> Hi,
>> >>>
>> >>> apparently since the latest QEMU updates I'm getting this on
On Mo, 2015-03-16 at 14:16 -0400, Bandan Das wrote:
> Jan Kiszka writes:
>
> > Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
> >> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
> >>> Hi,
> >>>
> >>> apparently since the latest QEMU updates I'm getting this once in a
> >>> while:
> >>
> >> h
Jan Kiszka writes:
> Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
>> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
>>> Hi,
>>>
>>> apparently since the latest QEMU updates I'm getting this once in a
>>> while:
>>
>> http://www.seabios.org/pipermail/seabios/2015-March/008897.html
>
> OK...
On Do, 2015-03-12 at 09:14 +0100, Jan Kiszka wrote:
> Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
> > On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
> >> Hi,
> >>
> >> apparently since the latest QEMU updates I'm getting this once in a
> >> while:
> >
> > http://www.seabios.org/pipermail/se
Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
>> Hi,
>>
>> apparently since the latest QEMU updates I'm getting this once in a
>> while:
>
> http://www.seabios.org/pipermail/seabios/2015-March/008897.html
OK... So we are waiting on a stable re
On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
> Hi,
>
> apparently since the latest QEMU updates I'm getting this once in a
> while:
http://www.seabios.org/pipermail/seabios/2015-March/008897.html
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the bod
Hi,
apparently since the latest QEMU updates I'm getting this once in a
while:
KVM internal error. Suberror: 1
emulation failure
EAX= EBX= ECX= EDX=000fd2bc
ESI= EDI= EBP= ESP=
EIP=000fd2c5 EFL=00010007 [-PC] CPL=0 II=0 A20=1 SMM=0 HLT=0
On Mon, 2009-06-22 at 11:26 +0300, Avi Kivity wrote:
> On 06/22/2009 09:55 AM, Ram Pai wrote:
> > On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
> >
> >> On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
> >>
> >>> I see this problem with a x86 sles10 guest running on x86_64 intel ho
On 06/22/2009 09:55 AM, Ram Pai wrote:
On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
I see this problem with a x86 sles10 guest running on x86_64 intel host.
If the guest is reset abruptly and rebooted, some where
before grub seq
On Monday 22 June 2009 14:55:46 Ram Pai wrote:
> On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
> > On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
> > > I see this problem with a x86 sles10 guest running on x86_64 intel
> > > host. If the guest is reset abruptly and rebooted, some where
> >
On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
> On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
> > I see this problem with a x86 sles10 guest running on x86_64 intel host.
> > If the guest is reset abruptly and rebooted, some where
> > before grub sequence it hangs and the following messag
On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
> I see this problem with a x86 sles10 guest running on x86_64 intel host.
> If the guest is reset abruptly and rebooted, some where
> before grub sequence it hangs and the following message is seen in the
> logs
>
> emulation failed (pagetable) rip
I see this problem with a x86 sles10 guest running on x86_64 intel host.
If the guest is reset abruptly and rebooted, some where
before grub sequence it hangs and the following message is seen in the
logs
emulation failed (pagetable) rip 7ed5 66 60 ac 20.
I located this instruction sequence in i
13 matches
Mail list logo