On Thu, 22 Apr 2021, Ottavio Caruso wrote:
> On Thu, 22 Apr 2021 at 13:46, Andreas Gustafsson
> <1743...@bugs.launchpad.net> wrote:
>>
>> Paul Goyette wrote:
>>> This bug was fixed long ago, so long ago that I have no idea when!
>>
>> No, it is
2d5b6787, in which seabios was
> updated to 1.11 prerelease, and the problem is still there as of
> commit 7398166ddf7c6dbbc9cae6ac69bb2feda14b40ac. The host operating
> system used for the tests was Debian 9 x86_64.
>
> Credit for discovering this bug goes to Paul Goyette.
>
t causes
> NetBSD to fall-back on a
> check-and-pause loop while an application CPU is waiting to be told to
> proceed by the boot CPU.)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1693667/+subscriptions
>
> !DSPAM:5ec7625625
ed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1693649/+subscriptions
>
> !DSPAM:5ec7625658281532840571!
>
>
++--+---+
| Paul Goyette | PGP Key fingerprint:
** Changed in: qemu
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1654137
Title:
Ctrl-A b not working in 2.8.0
Status in QEMU:
Confirmed
Bug description:
This bug is no longer fixed. See also bug #1743191
** Changed in: qemu
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1654137
Title:
Ctrl-A b not working
Further investigation shows that pause may be working, but very very
slowly.
The "use-case" in NetBSD is for "hatching" application CPUs. The target
CPU runs a loop that does
while (flag_1 not set)
for (i = 0; i < 1; i++)
x86_pause(); /* which is assem
Public bug reported:
In qemu 2.9.0 if you run
qemu-system-x86_64 -cpu Broadwell (or Haswell)
then the CPU features1 flag include the SSE3 bit, but do NOT include the
MONITOR/MWAIT bit. This is so even when the host includes the features.
Additionally, running qemu in this manner results i
Public bug reported:
Using qemu-2.9.0
When booting NetBSD using '-cpu haswell -smp 4', the system fails to
initialize the additional CPUs. It appears as though the "application
processor" enters routine x86_pause() but never returns.
x86_pause() is simply two assembler instructions: 'pause; ret
I can confirm that this bug is fixed in qemu 2.8.1
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1654137
Title:
Ctrl-A b not working in 2.8.0
Status in QEMU:
New
Bug description:
Wit
e this bug.
+--+--+----+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netb
Public bug reported:
With a recent update from 2.7.0 to 2.8.0 I have discovered that I can no
longer send a "break" to the VM. Ctrl-A b is simply ignored. Other
Ctrl-A sequences seem to work correctly.
This is on a NetBSD amd64 system, version 7.99.53, and qemu was
installed on this system from
On Mon, 3 Jan 2011, Paul Goyette wrote:
> The following is a complete, standalone test program:
>
> #include
> #include
> #include
> #include
>
>volatile int flt_signal = 0;
>
> static sigjmp_buf sigfp
# cc -o test test.c
# ./test
Start
FPE signal handler invoked 0 times.
#
On "real" hardware,
{225} cc -o test test.c
{226} ./test
Start
FPE signal handler invoked 1 times.
{227}
-------
Public bug reported:
I recognize that NetBSD is not one of the officially supported host OS.
However, qemu 0.13.0 is available in the NetBSD pkgsrc collection, and
works quite well. Well, with one exception (pun intended): It seems
that Floating Point exceptions don't get reported properly.
The
15 matches
Mail list logo
