From: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
To: Bug 1180923 <1180923@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Bug 1180923] Re: unused memory filled with 0x00 instead of 0xFF
Date: Mon, 1 Aug 2022 14:29:06 +0800 [thread overview]
Message-ID: <CAE2XoE8NUw+6fEHA4EvpkSBoqSv_iTrHotMxD7SkQFFrF5+J3w@mail.gmail.com> (raw)
In-Reply-To: <165930116695.48062.10370149944063594891.malone@dale.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
I create a issue at https://gitlab.com/qemu-project/qemu/-/issues/1133 to
tracking this
On Mon, Aug 1, 2022 at 5:06 AM David Glover <1180923@bugs.launchpad.net>
wrote:
> I know this is expired but it's still a problem in qemu 7.0.0. For
> example, when running MS-DOS 6.22, "mem" reports 0K of upper memory, and
> memmaker fails to run, complaining that it could not allocate any. I'd
> love to know if there's a workaround.
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1180923
>
> Title:
> unused memory filled with 0x00 instead of 0xFF
>
> Status in QEMU:
> Expired
>
> Bug description:
> Qemu, ever since it was made (so, since 2003), has this problem in DOS
> (either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the
> memory available when the memory is filled with 0x00 but when it is
> filled with 0xFF it gets recognized properly, where should I patch
> qemu to solve this memory problem?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1180923/+subscriptions
>
>
>
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
[-- Attachment #2: Type: text/html, Size: 1984 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Yonggang Luo <1180923@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1180923] Re: unused memory filled with 0x00 instead of 0xFF
Date: Mon, 01 Aug 2022 06:29:06 -0000 [thread overview]
Message-ID: <CAE2XoE8NUw+6fEHA4EvpkSBoqSv_iTrHotMxD7SkQFFrF5+J3w@mail.gmail.com> (raw)
Message-ID: <20220801062906.Wo6lC6Zj-m6bhS7UhPLy0SSc4nR2HyJFKwW1ggLjRq0@z> (raw)
In-Reply-To: 165930116695.48062.10370149944063594891.malone@dale.canonical.com
I create a issue at https://gitlab.com/qemu-project/qemu/-/issues/1133 to
tracking this
On Mon, Aug 1, 2022 at 5:06 AM David Glover <1180923@bugs.launchpad.net>
wrote:
> I know this is expired but it's still a problem in qemu 7.0.0. For
> example, when running MS-DOS 6.22, "mem" reports 0K of upper memory, and
> memmaker fails to run, complaining that it could not allocate any. I'd
> love to know if there's a workaround.
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1180923
>
> Title:
> unused memory filled with 0x00 instead of 0xFF
>
> Status in QEMU:
> Expired
>
> Bug description:
> Qemu, ever since it was made (so, since 2003), has this problem in DOS
> (either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the
> memory available when the memory is filled with 0x00 but when it is
> filled with 0xFF it gets recognized properly, where should I patch
> qemu to solve this memory problem?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1180923/+subscriptions
>
>
>
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1180923
Title:
unused memory filled with 0x00 instead of 0xFF
Status in QEMU:
Expired
Bug description:
Qemu, ever since it was made (so, since 2003), has this problem in DOS
(either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the
memory available when the memory is filled with 0x00 but when it is
filled with 0xFF it gets recognized properly, where should I patch
qemu to solve this memory problem?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1180923/+subscriptions
next prev parent reply other threads:[~2022-08-01 6:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 17:34 [Qemu-devel] [Bug 1180923] [NEW] unused memory filled with 0x00 instead of 0xFF TC1988
2013-05-16 17:40 ` [Qemu-devel] [Bug 1180923] " TC1988
2013-05-16 17:45 ` Battler
2013-05-16 19:20 ` [Qemu-devel] [Bug 1180923] [NEW] " Paolo Bonzini
2013-05-16 19:52 ` Stefan Hajnoczi
2013-05-16 20:00 ` Peter Maydell
2013-05-17 7:25 ` Paolo Bonzini
2013-05-17 15:59 ` Anthony Liguori
2013-05-21 1:31 ` Kevin O'Connor
2013-05-16 19:20 ` [Qemu-devel] [Bug 1180923] " Battler
2013-05-17 14:26 ` Battler
2013-05-17 14:36 ` Battler
2013-05-17 16:43 ` Battler
2020-08-07 9:25 ` Thomas Huth
2020-10-07 4:17 ` Launchpad Bug Tracker
2022-07-31 20:59 ` David Glover
2022-08-01 6:29 ` 罗勇刚(Yonggang Luo) [this message]
2022-08-01 6:29 ` Yonggang Luo
2022-08-01 6:30 ` Yonggang Luo
2023-06-12 21:57 ` Evren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE2XoE8NUw+6fEHA4EvpkSBoqSv_iTrHotMxD7SkQFFrF5+J3w@mail.gmail.com \
--to=luoyonggang@gmail.com \
--cc=1180923@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).