[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1314667] Re: PMPrebUSB - appcrash of qemu in Win-7-64b
From: |
Steve Si |
Subject: |
[Qemu-devel] [Bug 1314667] Re: PMPrebUSB - appcrash of qemu in Win-7-64bit |
Date: |
Wed, 30 Apr 2014 18:55:33 -0000 |
The QEMU used in RMPrepUSB is 32-bit only - it won't run 64-bit
programs. Normally, Windows will just display an error message saying it
needs a 64-bit system. Use Virtual Box for 64-bit OS testing and
DavidB's Virtual Machine USB Boot application - see www.rmprepusb.com
Tutorial #4
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1314667
Title:
PMPrebUSB - appcrash of qemu in Win-7-64bit
Status in QEMU:
New
Bug description:
I am not sure if this issue is a bug of qemu or by Win-7.
I want to test in advance with QEMU the ability if my USB-Rescue-Drive is
booting correctly. I have Win-7-64 and run qemu v.o.15.1.0 out of the
installed RMPrepUSB v.2.1.719
program. The settings for the preparation of my USB drive were FAT32 boot as
HD, bootloader WinPE/Win-7/Vista, set for running iso-files directly in %_ISO
\MAINMENU\Hiren’sBootCD.iso. When I run Qemu I get the messages in the cmd
starting window it says:
Administrator: RMPrepUSB QEMU Launcher
**************************************
EXECUTING "C:\Program Files (x86)\RMPrepUSB\qemu\STARTFROMUSB.cmd"
DRIVE NUMBER=3
MEMORY SIZE=1000
HARD DISK IMAGE=harddisk.img
NOWRITE=
Found OS=VISTA_OR_LATER
Sending command Start_VM.exe 3 500 qemu.exe -L . -name "RMPrepUSB Emulation
Session RAM=1000MB VirtualHDD=harddisk.i
lt+LCtrl)" -boot c -m 1000 -drive file=\\.
\PhysicalDrive3,if=ide,index=0,media=disk -hdb harddisk.img to shell...
Win-7: in the second window appears:
***********************************
-->qemu funktioniert nicht mehr
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: qemu.exe
Anwendungsversion: 0.15.1.0
Anwendungszeitstempel: 4f478c16
Fehlermodulname: qemu.exe
Fehlermodulversion: 0.15.1.0
Fehlermodulzeitstempel: 4f478c16
Ausnahmecode: 40000015
Ausnahmeoffset: 00053b06
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: bf8d
Zusatzinformation 2: bf8d49108a2e5a0707fc48438e01652a
Zusatzinformation 3: b0f1
Zusatzinformation 4: b0f155b0f1de9c5eb22bd6d100737cbe
If somebody can understand that behaviour I appreciate everybodies help.
Thank you with regards
H.O.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1314667/+subscriptions
- [Qemu-devel] [RFC 0/5] Allow object-add on X86CPU subclasses, for CPU model probing, Eduardo Habkost, 2014/04/30
- [Qemu-devel] [RFC 1/5] cpu: Initialize cpu->stopped=true earlier, Eduardo Habkost, 2014/04/30
- [Qemu-devel] [RFC 2/5] cpu: Don't try to pause CPUs if they are already stopped, Eduardo Habkost, 2014/04/30
- [Qemu-devel] [RFC 3/5] pc: Don't crash on apic_accept_pic_intr() if CPU has no apic_state, Eduardo Habkost, 2014/04/30
- [Qemu-devel] [RFC 4/5] target-i386: Make CPU objects user-creatable, Eduardo Habkost, 2014/04/30
- [Qemu-devel] [RFC 5/5] target-i386: Report QOM class name for CPU definitions, Eduardo Habkost, 2014/04/30