For my use case the newer image is fine too. I'm mildly curious what the
dwc_otg driver is doing in the older image though.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-
That part is easily fixed by running
qemu-img resize 2016-05-27-raspbian-jessie.img 4G
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_
Yep, it looks like that works! Sorry for the bogus report, I didn't
think to check the Changelog.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:
Note for bisection: it looks like it works fine as of tag stable-4.2 .
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read: Asse
Public bug reported:
When trying to run the 2016-05-27 Raspbian image on the emulated raspi2
platform, the system boots but shortly after the login prompt QEMU
(master; commit ID ca489cd037e4d50dc6c40570a167504ad7e5a521) dies with:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read: Asse
The initial bluescreen is caused because of unsupported CPU feature bits
(the DE flag, specifically). The experimental patch Clemens mentioned is
here:
http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg01412.html
Past that, however, there is a bug in QEMU's self-modifying code support
that
One possible option that has come up in the past is disabling the TLB
for your testing. It is slower, though, and would only work on TCG,
not KVM.
The way I'm currently doing this is by changing the conditional jump
here to an absolute one inside of the TCG code generator for i386 (and
of course y
The PC is not updated after every instruction in QEMU; instead it is
updated at the end of each block. If you want to see how the update is
done, you can look at the gen_jmp_im function in
target-i386/translate.c.
-Brendan
On Tue, Nov 26, 2013 at 12:51 PM, Mar Tsan wrote:
> I'm a master's studen
Argh, reply all is needed.
On May 19, 2013 4:45 PM, "Brendan Dolan-Gavitt"
wrote:
> We had to do something similar for our (soon to be released) record and
> replay implementation. To ensure interrupts are delivered at precisely the
> right time we added a global 64 bit inst
o walk the page
tables to fetch code even though paging is disabled. The symptom is
incorrect disassembly and some "Disassembler disagrees with translator
over instruction decoding" messages.
This was also reported as bug #1163065.
Signed-off-by: Brendan Dolan-Gavitt
---
ta
Public bug reported:
In target-i386 cpu_get_phys_page_debug, the CR4_PAE bit is checked
before CR0_PG. This means that if paging is disabled but the PAE bit has
been set in CR4, cpu_get_phys_page_debug will return the wrong result
(it will try to translate the address as virtual rather than using
t 12:59 PM, harryxiyou wrote:
> On Wed, Jan 23, 2013 at 12:58 AM, Brendan Dolan-Gavitt
> wrote:
>> Assuming you're using one of the -d options to qemu, they will by
>> default go into /tmp/qemu.log.
>
> How to add -d options to qemu.(Configure qemu/configure or Makefile?)
>
Assuming you're using one of the -d options to qemu, they will by
default go into /tmp/qemu.log. You can also specify where to put the
debug log using the -D option.
-Brendan
On Tue, Jan 22, 2013 at 11:49 AM, harryxiyou wrote:
> Hi all,
>
> When i debug our block driver in QEMU source codes, i c
Public bug reported:
Save and restore on mipsel seems to be broken (tested with commit
1c97e303d4ea80a2691334b0febe87a50660f99d). To reproduce:
1. Download debian_squeeze_mipsel_standard.qcow2 and vmlinux-2.6.32-5
-4kc-malta from from http://people.debian.org/~aurel32/qemu/mipsel/
2. Boot the sy
I also debugged this issue today and ended up in the same place --
after enabling the CPUID_DE bit in cpuid.c, I am able to start the
Windows 7 x64 installer, but it bluescreens with various messages
after a minute or so (with various codes like
DRIVER_IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HA
15 matches
Mail list logo
