[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1402289
Title:
netware 5.1
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1376938
Title:
detect-zero
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1397157
Title:
cpu high wi
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1405176
Title:
ctrl+alt+2
On Sat, Apr 14, 2018 at 11:44 PM, Su Hang wrote:
> Thanks for your detailed reply! I will carefully treat
> all the content that you mentioned, and apply them in v5.
By the way, if you are wondering why the parser needs to validate
everything, here is an example scenario:
QEMU may be used to ho
Hi,
I had the same problem, and maybe it can help. I wrote my own toy OS
with a PATA / IDE driver back in 2012 using older version of QEMU and
everything worked fine. These days, I tried that on a recent version
(2.5) and it failed with exactly the same behaviour - lots of zeros
being written duri
On 04/05/2018 04:13 PM, Emilio G. Cota wrote:
> The acquisition of tb_lock was added when the async tlb_flush
> was introduced in e3b9ca810 ("cputlb: introduce tlb_flush_* async work.")
>
> tb_lock was there to allow us to do memset() on the tb_jmp_cache's.
> However, since f3ced3c5928 ("tcg: cons
Has anyone been able to find a workaround to run this with KVM from an
ARM64 host? What exactly is the problem with Qemu/KVM/Aarch64 that stops
KVM from working - and are any efforts being made to get around it?
--
You received this bug notification because you are a member of qemu-
devel-ml, whi
Thanks for your detailed reply! I will carefully treat
all the content that you mentioned, and apply them in v5.
> -Original Messages-
> From: "Stefan Hajnoczi"
> Sent Time: 2018-04-14 22:08:43 (Saturday)
> To: "Su Hang"
> Cc: "Jim Mussared" , qemu-devel
> , "Joel Stanley"
> Subject:
Signed-off-by: Michael Tokarev
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 727ef118f3..8644c2e918 100644
--- a/Makefile
+++ b/Makefile
@@ -856,7 +856,7 @@ ifneq ($(BLOBS),)
$(INSTALL_DATA) $(SRC_PATH)/pc-bios/$$x
"$(D
On Mon, Apr 9, 2018 at 11:39 AM, Su Hang wrote:
> This patch adds Intel Hexadecimal Object File format support to
> the loader. The file format specification is available here:
> http://www.piclist.com/techref/fileext/hex/intel.htm
>
> The file format is mainly intended for embedded systems
> and
Implement a QMP command similar to the HMP's "info usbhost" command.
This allows a QMP client to query which USB devices may be available
for redirection. Because the availability of the command needs to
depend on the target's (not the build host's) USB configuration,
a stub function in host-stub.c
12 matches
Mail list logo
