>On Wed, Nov 04, 2015 at 08:48:20AM +0800, Gonglei wrote:
>> On 2015/11/3 14:58, Xulei (Stone, Euler) wrote:
>> > On qemu-kvm platform, when I reset a VM through "virsh reset", and
>> > coincidently
>> > the VM is in process of internal rebooting at
7;Connor wrote:
>> On Mon, Nov 09, 2015 at 08:32:53AM -0500, Kevin O'Connor wrote:
>> > On Fri, Nov 06, 2015 at 09:12:34AM +, Xulei (Stone) wrote:
>> > > >On Wed, Nov 04, 2015 at 08:48:20AM +0800, Gonglei wrote:
>> > > >I'm surprised you would
init bdf=00:0f.0 id=1af4:1001
>[2015-11-13 18:46:00] PCI: init bdf=00:10.0 id=1af4:1110
>[2015-11-13 18:46:00] PCI: init bdf=00:1f.0 id=1af4:
>[2015-11-13 18:46:00] PCI: Using 00:02.0 for primary VGA
>[2015-11-13 18:46:00] handle_smp: apic_id=1
>[2015-11-13 18:46:00] handle_smp: a
>On Thu, Nov 19, 2015 at 12:42:50PM +0000, Xulei (Stone) wrote:
>> Kevin,
>>
>> After deeply analyzing, i think there may be 3 possible reasons:
>> 1)wrong CountCPUs value. It seems CountCPUs++ in handle_smp() has no
>> lock to protect. So, sometimes, 2 or more
Hi,
Recently, i use a script to continuously reset a VM and
i found my VM frequently halts at "Attempting to allocate
VGA stack via pmm call". After analyzing, i think it may
be a problem of SeaBIOS.
>From the log(attached below), we can see handle_post()
executes twice and this makes the desti
>On Sat, Nov 28, 2015 at 07:12:47AM +0000, Xulei (Stone) wrote:
>> Hi,
>> Recently, i use a script to continuously reset a VM and
>> i found my VM frequently halts at "Attempting to allocate
>> VGA stack via pmm call". After analyzing, i think it may
>&g
>
>
>>On Sat, Nov 28, 2015 at 07:12:47AM +0000, Xulei (Stone) wrote:
>>> Hi,
>>> Recently, i use a script to continuously reset a VM and
>>> i found my VM frequently halts at "Attempting to allocate
>>> VGA stack via pmm call". A
> >>On Sat, Nov 28, 2015 at 07:12:47AM +0000, Xulei (Stone) wrote:
> >>> Hi,
> >>> Recently, i use a script to continuously reset a VM and
> >>> i found my VM frequently halts at "Attempting to allocate
> >>> VGA stack via pmm call&q
>On Wed, Dec 02, 2015 at 07:09:36AM +0000, Xulei (Stone) wrote:
>> I move HaveRunPost = 1 to handle_post() (after make_bios_writable()), and
>> I have tested for 1 day with continuously resetting, it seems works well!
>> Does following patch have some side effects?
>
>
f yes, does the KVM process show any register dumps or failure messages?
>- What's the output of:
>$ virsh qemu-monitor-command devstack --pretty '{"execute":"query-kvm"}'
>when seabios fails to load?
>
>Regards,
>Mohammed
>
>
>
>On Thu, Dec
e_hwpic1 irq=0
[2015-12-17 12:37:35] handle_hwpic1 irq=0
... always hanle_hwpic1 irq=0, never ends anymore...
>> -Original Message-
>> From: Kevin O'Connor [mailto:ke...@koconnor.net]
>> Sent: Tuesday, December 22, 2015 2:47 AM
>> To: Gonglei (Arei)
>> Cc: Xulei (Stone)
>This is a follow up to an email chain that in November:
>
> http://www.seabios.org/pipermail/seabios/2015-November/009887.html
>
>It was possible for the SeaBIOS code to get confused if an external
>reboot request occurs while seabios is already in the process of
>handling a boot or reboot.
>
>Th
CI: init bdf=00:1f.0 id=1af4:
2016-07-29 11:33:56PCI: Using 00:02.0 for primary VGA
--
Xulei (Stone)
___
SeaBIOS mailing list
SeaBIOS@seabios.org
https://www.coreboot.org/mailman/listinfo/seabios
>On Fri, Jul 29, 2016 at 04:04:59AM +0000, Xulei (Stone) wrote:
>> Hi, all:
>> Recently when i try to reset a vm, I find it may be stuck in SeaBIOS.
>> I use a shell script to continuously reset a vm to see what may happen.
>>
>> #!/bin/bash
>> while((1))
>On Tue, Aug 02, 2016 at 04:18:30AM +0000, Xulei (Stone) wrote:
>> >On Fri, Jul 29, 2016 at 04:04:59AM +0000, Xulei (Stone) wrote:
>> >> After one day, the vm is stuck. Looking from the following seabios log,
>> >> it seems seabios stops at "PCI: Using 00
>On Tue, Aug 02, 2016 at 04:18:30AM +0000, Xulei (Stone) wrote:
>> >On Fri, Jul 29, 2016 at 04:04:59AM +0000, Xulei (Stone) wrote:
>> >> After one day, the vm is stuck. Looking from the following seabios
>> >> log, it seems seabios stops at "PCI: Using 00
> On 09/08/2016 10:04, Xulei (Stone) wrote:
> > Following your suggestion, i'm now sure it is caused by missing SMI.
> > I have tried adding dprintf() like this:
> >
> > --- a/roms/seabios/src/fw/smm.c
> > +++ b/roms/seabios/src/fw/smm.c
> > @@ -65,7
> On 11/08/2016 04:13, Xulei (Stone) wrote:
> > Following your suggestion, I found this problem may be caused by the
> > flag of HF_SMM_MASK. I'm now sure QEMU is sending the KVM_SMI ioctl,
> > and kmod already handles this ioctl.
> >
> > I add print
Hiļ¼can you tell me what's the worst effect if i apply the following patch?
In order to boot a BIG vm (with 4T mem, 255 vCPUs, 60 virtio-scsi disk...), i
have to increase the
BUILD_MAX_HIGHTABLE to 512KB.
But, then i found i can not boot a specific VM anymore (oracle linux 6.7
64bits with kernel
Hello all,
Recently, I met a werid question when i run a VM in the following platfrom:
Vmware Vsphere 6.0/6.5
|-- centos 7.3 nested VM (with qemu 2.8, kmod 4.4.11, seabios 1.10)
|-- VM (with virtio-scsi controller, modern mode)
VM MUST hang in seabios when try to mmio write during virt
On 07/17/2017 11:13 AM, Xulei (Stone) wrote:
>> |--virtio_queue_empty
>>
>> Then, kmod falls in infinite loop in handle EPT_MISCONFIG.
>> As far as i know, when kvm enters guest after handling EPT_MISCONFIG,
>> seabios should return
&
21 matches
Mail list logo
