Hello.
I tried to install windows on a qemu img and got this error:
Windows boot manager
Windows failed to start. A recent hardware or software change might
be the cause. To fix the problem:
1. Insert windows installation cd and restart you computer
On Sun, Nov 23, 2014 at 2:57 AM, jenia.ivlev jenia.iv...@gmail.com wrote:
I tried to install windows on a qemu img and got this error:
...
Ramdisk device creation failed due to insufficient memory.
This is how I did it (and got the error from above):
qemu-img create windows 15G
On Tue, Aug 12, 2014 at 05:49:13PM +0800, Tiejun Chen wrote:
v5:
* Simplify to make sure its really inherited from the standard one in patch #3
* Then drop the original patch #3
I carried
i440fx: make types configurable at run-time
pc_init1: pass parameters just with types
And seen from QEMU:
qemu: fatal: Trap 0x02 while interrupts disabled, Error state
[register dump removed]
Bah. Do you know whether this happens only on SPARC QEMU, or
is this an issue for all QEMU ports?
According to Fabien, one of our QEMU experts, it's related to the
tcp_get_fds API discards fds if there's more than 1 of these.
It's tricky to fix this without API changes in the generic case.
However, this API is only used by tests ATM, and tests know how
many fds they expect.
So let's not waste cycles trying to fix this properly:
simply assume at most 16
The following changes since commit 0e88f478508b566152c6681f4889ed9830a2c0a5:
Merge remote-tracking branch 'remotes/stefanha/tags/net-pull-request' into
staging (2014-11-21 14:15:37 +)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
From: Igor Mammedov imamm...@redhat.com
Performance wise it's better to align GVA by the backend's
page size.
Also do not allow to create DIMM device with suboptimal
size (i.e. not aligned to backends page size) to aviod
memory loss.
Do above only for 2.2 and newer machine types to avoid
From: Igor Mammedov imamm...@redhat.com
split addr initialization from declaration so that
later when new local vars are added property getter
wouldn't drift off of error check.
Signed-off-by: Igor Mammedov imamm...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by:
From: Igor Mammedov imamm...@redhat.com
When more memory devices are used than available
KVM memory slots, QEMU crashes with:
kvm_alloc_slot: no free slot available
Aborted (core dumped)
Fix this by checking that KVM has a free slot before
attempting to map memory in guest address space.
From: Igor Mammedov imamm...@redhat.com
if DIMMs with different size/alignment are interleaved
in creation order, it could lead to hotplug-memory
container fragmentation and following inability to use
all RAM upto maxmem.
For example:
-m 4G,slots=3,maxmem=7G
-object
From: Igor Mammedov imamm...@redhat.com
introduce memory_region_get_alignment() that returns
underlying memory block alignment or 0 if it's not
relevant/implemented for backend.
Signed-off-by: Igor Mammedov imamm...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by:
From: Igor Mammedov imamm...@redhat.com
When running in KVM mode, kvm_set_phys_mem() will silently
fail if registered MemoryRegion address/size is not page
aligned. Causing memory hotplug failure in guest.
Mapping non aligned MemoryRegion in TCG mode 'works', but
sane guest OS still expects page
From: Igor Mammedov imamm...@redhat.com
Currently maxmem limit is not checked and depends on
hotplug region container not being able to fit more RAM
than maxmem. Do check explicitly so that it would
be possible to change hotplug container size later
to deal with fragmentation.
Signed-off-by:
From: Igor Mammedov imamm...@redhat.com
Signed-off-by: Igor Mammedov imamm...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/mem/pc-dimm.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/mem/pc-dimm.c
From: Marcel Apfelbaum marce...@redhat.com
If the pci bridge enters in error flow as part
of init process it will only delete the shpc mmio
subregion but not remove it from the properties list,
resulting in segmentation fault when the bridge runs
the exit function.
Example: add a pci bridge
acpi build modifies internal FW CFG RAM on first access
but we forgot to mark it dirty.
If this RAM has been migrated already, it won't be
migrated again, returning corrupted tables to guest.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/hw/loader.h | 2 +-
hw/core/loader.c
From: Gonglei arei.gong...@huawei.com
Reported-by:
https://bugs.launchpad.net/qemu/+bug/1393440
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci/pcie.c | 2 +-
1 file changed, 1
From: Paolo Bonzini pbonz...@redhat.com
This makes it simpler to keep the SSDT byte-for-byte identical for a
given machine type, which is a goal we want to have for 2.2 and newer
types.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
From: Gonglei arei.gong...@huawei.com
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci/pcie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/pci/pcie.c
From: Igor Mammedov imamm...@redhat.com
If QEMU is started with -numa ... Windows only notices that
CPU has been hot-added but it will not online such CPUs.
It's caused by the fact that possible CPUs are flagged as
not enabled in SRAT and Windows honoring that information
doesn't use
El Mon, 17 Nov 2014 15:48:09 +
Stefan Hajnoczi stefa...@gmail.com escribió:
On Sat, Nov 01, 2014 at 06:02:30PM +0100, Marc Marí wrote:
+static void mmio_basic(void)
+{
+QVirtioMMIODevice *dev;
+QVirtQueue *vq;
+QGuestAllocator *alloc;
+QVirtioBlkReq req;
+
On Tue, Oct 28, 2014 at 10:09:12AM +0100, Gerd Hoffmann wrote:
This patch switches the default display from cirrus to vga
for the new (qemu 2.2+) machine types. Old machines types
stay as-is for compatibility reasons.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Gerd, I noticed that
-Origin email-
From: Peter Maydell peter.mayd...@linaro.org
Sent Time: Friday, November 21, 2014
To: Kaiyuan kaiyu...@tju.edu.cn
Cc: Greg Kurz gk...@linux.vnet.ibm.com, qemu-devel qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fw:Re:Re: How to access guest memory from qemu
device
Hi,
This patch adds support for sending AUXV packet.
This is required for debugging Linux position independent executables.
Otherwise, gdb client cannot find out where the executable is loaded.
Signed-off-by: Wei-cheng, Wang cole...@gmail.com
---
gdbstub.c | 41
Ping?
On 10/27/2014 12:58 AM, Wei-cheng Wang wrote:
QEMU should convert signal number reciving from GDB cilent
from gdb-signal number to target sginal number - using gdb_signal_to_target().
In this case, GDB_SIG_BUS is 10. However, 10 is SIGUSR1 for target.
So QEMU continues with the wrong
Never mind. I just found Martin Simmons fixed the same issue.
On Sun, Nov 23, 2014 at 9:30 PM, Wei-cheng, Wang cole...@gmail.com wrote:
Ping?
On 10/27/2014 12:58 AM, Wei-cheng Wang wrote:
QEMU should convert signal number reciving from GDB cilent
from gdb-signal number to target sginal
Thats exactly it. thanks very much ;)
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: kvm (Ubuntu Hardy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: qemu (Ubuntu Hardy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: usbview (Ubuntu Hardy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
On 23 November 2014 at 13:18, Kaiyuan kaiyu...@tju.edu.cn wrote:
Thanks for your explanation about guest physical/virtual
address and host physical/virtual address, and I think I
asked a wrong question. Is there a function that translates
guest Physical address to host Virtual address so that
Greetings,
Could you kindly elaborate QEMU threading model under the following
condition.
I started virtual machine with 2 virtual cpus (KVM assisted). It generated
a number of threads in qemu, though I was not doing any CPU intense or IO
intense operations. I understand from
I think it is related to Apparmor, I see the following lines in
/etc/syslog:
Nov 22 14:36:23 uvir kernel: [18882.602278] audit: type=1400
audit(1416663383.171:69): apparmor=DENIED operation=open
profile=libvirt-30619811-d285-944a-026a-cdd4a753b77a
Paolo - I should have some time to do that this week, as well as bone up
on git (it's been a bit . . .)
And thanks for the quick reply!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217
Title:
On 2014/11/23 18:10, Michael S. Tsirkin wrote:
On Tue, Aug 12, 2014 at 05:49:13PM +0800, Tiejun Chen wrote:
v5:
* Simplify to make sure its really inherited from the standard one in patch #3
* Then drop the original patch #3
I carried
i440fx: make types configurable at run-time
# @auto-converge: If enabled, QEMU will automatically throttle down the
guest
# to speed up convergence of RAM migration. (since 1.6)
#
# Since: 1.2
##
{ 'enum': 'MigrationCapability',
- 'data': ['xbzrle', 'rdma-pin-all', 'auto-converge', 'zero-blocks']
}
+
Array index starts at 0, so the valid index of ext_queue array,
io_queue array, mchk_queue array should be MAX_EXT_QUEUE - 1,
MAX_IO_QUEUE - 1, MAX_MCHK_QUEUE - 1.
The original checks missed the invalid bound value, which will lead
possible out of bounds read in the follow codes.
Signed-off-by:
Hi all,
Thank you for your time to read this email, is there anyone can tell me the
options qemu was configured when it was released?
I configured it by myself and found that there was a audio latency problem, but
the qemu in the repository doesn't have this problem,
so i want to kown about
the qemu command is as below:
qemu-system-x86_64 -machine accel=kvm:tcg -m 4096 -smp 4 -M pc-i440fx-1.4 -spi
ce port=5906,addr=0.0.0.0,disable-ticketing,jpeg-wan-compression=always -vga
qxl -global qxl-vga.vram_size=268435456
/opt/instances/win7_sh_2.1.1_driver.qcow2 -net
On 11/22/2014 at 12:25 AM, in message
20141121162505.gf3...@noname.redhat.com, Kevin Wolf kw...@redhat.com wrote:
Am 30.07.2014 um 04:55 hat Chunyan Liu geschrieben:
Add nocow info in 'qemu-img info' output to show whether the file
currently has NOCOW flag set or not.
Coverity reports the 'size' may be used uninitialized, but that can't happen,
because the caller has checked if (binfo-dtb_filename || binfo-get_dtb)
before call 'load_dtb'.
Here we simply remove the 'if (binfo-get_dtb)' to satisfy coverity.
Signed-off-by: zhanghailiang
-Origin email-
From: Peter Maydell peter.mayd...@linaro.org
Sent Time: Monday, November 24, 2014
To: Kaiyuan kaiyu...@tju.edu.cn
Cc: Greg Kurz gk...@linux.vnet.ibm.com, qemu-devel qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to access guest memory from qemu device internal
On 11/17/2014 11:26 PM, Alexander Graf wrote:
Am 17.11.2014 um 05:12 schrieb Samuel Mendoza-Jonas sam...@au1.ibm.com:
If a spapr guest reboots during a live migration, the guest HTAB on the
destination is not updated properly, usually resulting in a kernel panic.
This is a (delayed!)
43 matches
Mail list logo
