On 5 May 2011 00:16, Rob Landley r...@landley.net wrote:
I note that I have a half-dozen prebuilt system images at
http://landley.net/aboriginal/downloads/binaries and the build scripts
and such are in the directories above that.
I'm afraid I don't entirely understand your file naming
system
What is ITP ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/723871
Title:
qemu-kvm-0.14.0 Aborts with -vga qxl
Status in QEMU:
Confirmed
Status in “libvirt” package in Ubuntu:
Triaged
Status
Currently smp support for kvm does not work. Qemu does a kvm run even on
secondary CPUs which dont have a sane state (initial psw == 0)
triggering some program faults. Architecturally these cpus are in the stopped
state, so we should not do the kvm run ioctl. (these CPUs will be started
by a SIGP
Hi,
the subject's tag (qemu-kvm) is misleading. This is actually targeting
the uq/master patch queue, i.e. the upstream kvm staging area.
On 2011-05-05 05:03, brill...@viatech.com.cn wrote:
When KVM is running on VIA CPU with host cpu's model, the feautures of
VIA CPU will be passed into kvm
Hi Marcelo,
Other than that, shouldnt reset accounting variables to init state on
write to GLOBAL_ENABLE_CFG / writes to main counter?
I'd suggest to initialize/reset the driftfix-related fields in the
'HPETTimer' structure (including the backlog of unaccounted ticks)
in the following
Hi all,
I'm new to the list, so hopefully I'm not retracing old ground (I did
try to search the
archives, but maybe I missed something).
The problem I have is that when using the Stellarris ARMv7M target if I load an
ELF file as my kernel, and some of the ELF segments are outside the range of
Thank you for subscribing. You have now unsubscribed and no more messages will
be sent.
Hi all,
For some current software development I'm doing I've found it most easy
to use Qemu in the following manner
qemu-system-arm -M lm3s811evb -s -S arm-eabi-gdb
From GDB I then load any code I want to debug and test and run it.
For this to work however, I needed to make a small change to
case 2: /*RST2*/
- TBD();
+ if (_OP2 = 12) {
+ HAS_OPTION(XTENSA_OPTION_32_BIT_IDIV);
+ int label = gen_new_label();
+ tcg_gen_brcondi_i32(TCG_COND_NE, cpu_R[RRR_T], 0, label);
+
To track immediate values written to SAR? You mean that there may be
some performance difference of fixed size shift vs indirect shift and
TCG is able to tell them apart?
Well, not really fixed vs indirect, but if you know that the value
in the SAR register is in the right range, you can
When running qemu-system on Darwin, the vcpu processes guest code, but
I don't get to see anything on the cocoa screen.
When running a guest with -nographic, time stands still for the guest:
[0.00] Detected 2659.508 MHz processor.
[0.000756] Calibrating delay loop (skipped), value
On Thu, May 05, 2011 at 12:28:31AM +0200, Paolo Bonzini wrote:
Virtio SCSI Controller Device Spec
==
The virtio controller device groups together one or more simple virtual
devices (ie. disk), and allows communicating to these devices using the
SCSI protocol.
On 5 May 2011 09:23, Ben Leslie be...@benno.id.au wrote:
FWIW, the reason why I'm not using -kernel is that the current
way the armv7m code works, it expects the provided kernel to
be a full flash image including appropriate vector table, whereas
right now I just want to debug some stand-alone
On 04.05.2011, at 21:08, Blue Swirl wrote:
On Mon, May 2, 2011 at 6:03 PM, Alexander Graf ag...@suse.de wrote:
The e500 PCI controller isn't qdev'ified yet. This leads to severe issues
when running with -drive.
To be able to use a virtio disk with an e500 VM, let's convert the PCI
hi
I have sent corrected patches regarding MIPS64 user mode emulation with
Octeon support.
But i got no further review on these Patches the date of mailed patches is
29th of April.
the subjects of my mails are as follow
*[PATCH 1/3](Corrected version) linux-user:Support for MIPS64 user mode
From: Anthony PERARD anthony.per...@citrix.com
Hi all,
Here is an update on the series that add the support of a Xen HVM guest to
QEMU.
change v14-v15:
- add a patch to not initialise vmport with Xen.
The change v13-v14:
- Remove of ram_size parameter from pc_memory_init
- set both
From: Anthony PERARD anthony.per...@citrix.com
Introduce the Xen FV (Fully Virtualized) machine to Qemu, some more Xen
specific call will be added in further patches.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pc_piix.c | 41 +++--
From: Anthony PERARD anthony.per...@citrix.com
The xenpv machine use the common init function.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
Makefile.target |9 +
hw/xen.h| 13 +
hw/xen_backend.c|
From: Anthony PERARD anthony.per...@citrix.com
This patch moves above_4g_mem_size and below_4g_mem_size calculation in
the caller of pc_memory_init (pc_init1). And the prototype of
pc_memory_init is changed because there is no need anymore to have
variable pointer and the ram_size parameter.
From: Anthony PERARD anthony.per...@citrix.com
xen_domainbuild and xen_machine_pv are built only for i386 targets.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
Makefile.target |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile.target
From: Anthony PERARD anthony.per...@citrix.com
Every set_irq call makes a Xen hypercall.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
---
hw/pc_piix.c |8 ++--
hw/xen.h |2 ++
xen-all.c| 12
From: Jun Nakajima jun.nakaj...@intel.com
On IA32 host or IA32 PAE host, at present, generally, we can't create
an HVM guest with more than 2G memory, because generally it's almost
impossible for Qemu to find a large enough and consecutive virtual
address space to map an HVM guest's whole
From: Anthony PERARD anthony.per...@citrix.com
This is because there is not synchronisation of the vcpu register
between Xen and QEMU, so vmport can't work properly.
This patch introduces no_vmport parameter to pc_basic_device_init.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
From: Anthony PERARD anthony.per...@citrix.com
This patch updates the libxenctrl calls in Qemu to use the new interface,
otherwise Qemu wouldn't be able to build against new versions of the
library.
We check libxenctrl version in configure, from Xen 3.3.0 to Xen
unstable.
Signed-off-by: Anthony
From: John Baboval john.babo...@virtualcomputer.com
Adds a cap to the number of map cache entries. This prevents the map
cache from overwhelming system memory.
I also removed the bitmap macros and #included bitmap.h instead.
Signed-off-By: John Baboval john.babo...@virtualcomputer.com
From: Anthony PERARD anthony.per...@citrix.com
This tells to the xen management tool that the machine can begin run.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
xen-all.c | 23 +++
1 files changed, 23 insertions(+), 0
From: Anthony PERARD anthony.per...@citrix.com
This patch introduces Xen specific call in piix_pci.
The specific part for Xen is in write_config, set_irq and get_pirq.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
From: Anthony PERARD anthony.per...@citrix.com
With MapCache, we can handle a 64b target, even with a 32b host/qemu.
So, we need to have target_phys_addr_t to 64bits.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
configure |1 +
1 files
From: Anthony PERARD anthony.per...@citrix.com
This function allows to unlock a ram_ptr give by qemu_get_ram_ptr. After
a call to qemu_put_ram_ptr, the pointer may be unmap from QEMU when
used with Xen.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf
From: Anthony PERARD anthony.per...@citrix.com
Introduce two functions qemu_shutdown_requested_get and
qemu_reset_requested_get to get the value of shutdown/reset_requested
without reset it.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini
From: John Baboval john.babo...@virtualcomputer.com
Prevent a deadlock caused by leaving a map cache bucket locked by the
preceding qemu_get_ram_ptr() call.
Signed-off-By: John Baboval john.babo...@virtualcomputer.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pci.c |2
From: Arun Sharma arun.sha...@intel.com
Open and bind event channels; map ioreq and buffered ioreq rings.
Signed-off-by: Arun Sharma arun.sha...@intel.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
Acked-by:
From: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pc_piix.c |6 +-
hw/xen.h |1 +
xen-all.c|9 +
xen-stub.c |4
4 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/hw/pc_piix.c
On 04/03/11 07:33, Brad Hards wrote:
These descriptors are covered in Section 9.6.4 of the USB 3.0 spec,
but there is a better description in the Intel IAD whitepaper
(www.usb.org/developers/whitepapers/iadclasscode_r10.pdf).
The implementation basically introduces the concept of a grouped of
On Thu, May 5, 2011 at 19:56, Peter Maydell peter.mayd...@linaro.org wrote:
On 5 May 2011 09:23, Ben Leslie be...@benno.id.au wrote:
FWIW, the reason why I'm not using -kernel is that the current
way the armv7m code works, it expects the provided kernel to
be a full flash image including
diff --git a/hw/usb-uhci.c b/hw/usb-uhci.c
index 346db3e..a51d89b 100644
--- a/hw/usb-uhci.c
+++ b/hw/usb-uhci.c
@@ -732,11 +732,21 @@ out:
case USB_RET_STALL:
td-ctrl |= TD_CTRL_STALL;
td-ctrl= ~TD_CTRL_ACTIVE;
+s-status |= UHCI_STS_USBERR;
Just this line
On Fri, Apr 08, 2011 at 09:52:59PM +0900, Isaku Yamahata wrote:
vender id/device id... in configuration space are read-only registers
which are commonly defined for all pci devices.
So initialize them in common code and it simplifies the initialization a bit.
I converted some of them.
If
So the benefit as I see it would be that qemu will be able to list
supported devices by vendor id etc.
lspci has a database of readable vendor/device strings,
maybe we can import that.
And we could sort by device type, that's also helpful.
header type/prog interface - not so sure.
On Fri, Apr
Virtqueues
0..n-1:one requestq per target
n:control transmitq
n+1:control receiveq
1 requestq per target makes it harder to support large numbers or
dynamic targets.
I chose 1 requestq per target so that, with MSI-X support, each target
can be associated to one MSI-X vector.
#define VIRTIO_SCSI_T_BARRIER 0x8000
The type identifies the remaining fields. The value
VIRTIO_SCSI_T_BARRIER can be ORed in the type as well. This bit
indicates that this request acts as a barrier and that all preceding
requests must be complete before
On 05/05/2011 02:50 PM, Christoph Hellwig wrote:
Please don't repeat the barrier mistake done in the Xen and virtio-blk/lguest
protocols. It really doesn't make sense to put this kind of strict odering
in. If we really want ordering let's do it using SCSI ordered tags at least
to use a
On 05/05/2011 11:36 AM, Alexander Graf wrote:
When running qemu-system on Darwin, the vcpu processes guest code, but
I don't get to see anything on the cocoa screen.
Out of curiosity, does it work with iothread?
Paolo
On Sat, Apr 30, 2011 at 10:40:07PM +0200, Stefan Weil wrote:
QEMU sends frames smaller than 60 bytes to ethernet nics.
This should be fixed in the networking code because normally
such frames are rejected by real NICs and their emulations.
To avoid this behaviour, other NIC emulations pad
On Sat, Apr 30, 2011 at 10:40:03PM +0200, Stefan Weil wrote:
Hi,
this is the second version of a series of patches for eepro100 which mainly
fix endianness issues and enhance register access. There was a bug report
on qemu-devel recently which is fixed by these enhancements, see
On Mon, May 02, 2011 at 08:00:47PM +0200, Jan Kiszka wrote:
msi_init may fail, so we need to check on uninit if the cap was
actually installed. This also avoids that the users need to check.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Applied, thanks!
---
hw/ide/ich.c |5 +
On Mon, May 02, 2011 at 08:01:37PM +0200, Jan Kiszka wrote:
Used by HD audio controllers like our intel-hda.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Applied, thanks!
---
hw/pci.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
On 05.05.2011, at 14:56, Paolo Bonzini wrote:
On 05/05/2011 11:36 AM, Alexander Graf wrote:
When running qemu-system on Darwin, the vcpu processes guest code, but
I don't get to see anything on the cocoa screen.
Out of curiosity, does it work with iothread?
Seems to work with -nographic,
On 5 May 2011 13:03, Ben Leslie be...@benno.id.au wrote:
I still think it is somewhat nice that the simulator target can work
just like a blank board though, and then connect GDB to it either
directly for the sim or via JTAG for a real board. Then it is the
same work flow for simulated or real
On Tue, May 03, 2011 at 12:36:58PM -0600, Alex Williamson wrote:
When a phys memory client registers and we play catchup by walking
the page tables, we can make a huge improvement in the number of
times the set_memory callback is called by batching contiguous
pages together. With a 4G guest,
On Tue, May 03, 2011 at 12:36:19PM -0600, Alex Williamson wrote:
This series pulls together several related patches for bugs and
performance that I found last week. Only the 2nd patch is actually
modified from inital posting, adding the comments suggested by
Markus. The 1st two patches fix
On 05/05/2011 03:15 PM, Alexander Graf wrote:
On 05.05.2011, at 14:56, Paolo Bonzini wrote:
On 05/05/2011 11:36 AM, Alexander Graf wrote:
When running qemu-system on Darwin, the vcpu processes guest
code, but I don't get to see anything on the cocoa screen.
Out of curiosity, does it work
On 05.05.2011, at 15:23, Paolo Bonzini wrote:
On 05/05/2011 03:15 PM, Alexander Graf wrote:
On 05.05.2011, at 14:56, Paolo Bonzini wrote:
On 05/05/2011 11:36 AM, Alexander Graf wrote:
When running qemu-system on Darwin, the vcpu processes guest
code, but I don't get to see anything on
Quoting Boris Derzhavets (723...@bugs.launchpad.net):
What is ITP ?
ITP is an 'Intent to Package', as outlined at
https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages. It's a type of
bug to open in order to get packages into the universe archive.
--
You received this bug notification
On Thu, 2011-05-05 at 16:21 +0300, Michael S. Tsirkin wrote:
On Tue, May 03, 2011 at 12:36:58PM -0600, Alex Williamson wrote:
When a phys memory client registers and we play catchup by walking
the page tables, we can make a huge improvement in the number of
times the set_memory callback is
Hi all,
On 05/05/2011 02:49 PM, Paolo Bonzini wrote:
Virtqueues
0..n-1:one requestq per target
n:control transmitq
n+1:control receiveq
1 requestq per target makes it harder to support large numbers or
dynamic targets.
I chose 1 requestq per target so that, with MSI-X support, each
target
On 05/05/11 16:21, Alex Williamson wrote:
A bit worried that ram_addr_t size might thinkably overflow
(it's just a long, could be a 4G ram). Break it out when it fills up?
struct CPUPhysMemoryClient {
void (*set_memory)(struct CPUPhysMemoryClient *client,
On 05/05/2011 04:29 PM, Hannes Reinecke wrote:
I chose 1 requestq per target so that, with MSI-X support, each
target can be associated to one MSI-X vector.
If you want a large number of units, you can subdivide targets into
logical units, or use multiple adapters if you prefer. We can have
On Thu, May 05, 2011 at 04:30:57PM +0200, Jes Sorensen wrote:
On 05/05/11 16:21, Alex Williamson wrote:
A bit worried that ram_addr_t size might thinkably overflow
(it's just a long, could be a 4G ram). Break it out when it fills up?
struct CPUPhysMemoryClient {
void
On Thu, May 05, 2011 at 08:21:06AM -0600, Alex Williamson wrote:
On Thu, 2011-05-05 at 16:21 +0300, Michael S. Tsirkin wrote:
On Tue, May 03, 2011 at 12:36:58PM -0600, Alex Williamson wrote:
When a phys memory client registers and we play catchup by walking
the page tables, we can make a
On 05/05/11 17:18, Michael S. Tsirkin wrote:
A memory size can obviously not be bigger than the maximum physical
address, so I find it really hard to see how this could overflow.
For example, a 4G size does not fit in 32 bits.
That is the only corner case - you can handle that by -1 if you
On Thu, May 05, 2011 at 05:36:04PM +0200, Jes Sorensen wrote:
On 05/05/11 17:18, Michael S. Tsirkin wrote:
A memory size can obviously not be bigger than the maximum physical
address, so I find it really hard to see how this could overflow.
For example, a 4G size does not fit in 32 bits.
On 05/05/11 17:38, Michael S. Tsirkin wrote:
On Thu, May 05, 2011 at 05:36:04PM +0200, Jes Sorensen wrote:
On 05/05/11 17:18, Michael S. Tsirkin wrote:
A memory size can obviously not be bigger than the maximum physical
address, so I find it really hard to see how this could overflow.
On Thu, May 05, 2011 at 05:40:19PM +0200, Jes Sorensen wrote:
On 05/05/11 17:38, Michael S. Tsirkin wrote:
On Thu, May 05, 2011 at 05:36:04PM +0200, Jes Sorensen wrote:
On 05/05/11 17:18, Michael S. Tsirkin wrote:
A memory size can obviously not be bigger than the maximum
physical
The following changes since commit d2d979c628e4b2c4a3cb71a31841875795c79043:
NBD: Avoid leaking a couple of strings when the NBD device is closed
(2011-05-03 11:29:21 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
Alex
On Thu, May 05, 2011 at 03:41:57PM +0300, Michael S. Tsirkin wrote:
On Fri, Apr 08, 2011 at 09:52:59PM +0900, Isaku Yamahata wrote:
vender id/device id... in configuration space are read-only registers
which are commonly defined for all pci devices.
So initialize them in common code and it
Am 05.05.2011 15:00, schrieb Michael S. Tsirkin:
On Sat, Apr 30, 2011 at 10:40:07PM +0200, Stefan Weil wrote:
QEMU sends frames smaller than 60 bytes to ethernet nics.
This should be fixed in the networking code because normally
such frames are rejected by real NICs and their emulations.
To
Public bug reported:
As originally found at http://www.mail-
archive.com/k...@vger.kernel.org/msg08745.html from 3 years ago!
Basically qemu seizes up in the event that the file descriptor for its
emulated serial port has a full buffer, i.e. write() returns EAGAIN.
For me, this happened when the
On 05/03/2011 10:06 AM, Gerd Hoffmann wrote:
Hi,
This is the current spice patch queue ready for pull. Patches have been
posted a few days ago for review. A minor issue (leftover debug bit,
spotten by Alon) has been fixed and the patch queue has been rebased to
latest master, otherwise it
On 05/05/2011 10:45 AM, Michael S. Tsirkin wrote:
The following changes since commit d2d979c628e4b2c4a3cb71a31841875795c79043:
NBD: Avoid leaking a couple of strings when the NBD device is closed
(2011-05-03 11:29:21 +0200)
are available in the git repository at:
On 05/04/2011 10:41 AM, Gerd Hoffmann wrote:
Hi,
The USB patch queue is back! I'm still busy catching up with the
backlog, I know I didn't pick up everything from the list yet. If in
doubt it doesn't hurt to resend usb related patches, with me being
Cc'ed.
This pull brings old stuff, most
Correct handling of NaNs for VFP VMLA, VMLS, VNMLS and VNMLA requires that
we implement the set of negations and additions specified by the ARM ARM;
plausible looking simplifications like turning (-A + B) into (B - A) or
computing (A + B) rather than (B + A) result in selecting the wrong NaN or
On 05/05/2011 02:01 AM, Peter Maydell wrote:
On 5 May 2011 00:16, Rob Landley r...@landley.net wrote:
I note that I have a half-dozen prebuilt system images at
http://landley.net/aboriginal/downloads/binaries and the build scripts
and such are in the directories above that.
I'm afraid I
On 5 May 2011 23:13, Rob Landley r...@landley.net wrote:
On 05/05/2011 02:01 AM, Peter Maydell wrote:
I'm afraid I don't entirely understand your file naming
system there -- it seems to say which architecture the
system images are for but not what board?
Exactly. An armv5l root filesystem
On 05/05/2011 05:32 PM, Peter Maydell wrote:
On 5 May 2011 23:13, Rob Landley r...@landley.net wrote:
On 05/05/2011 02:01 AM, Peter Maydell wrote:
I'm afraid I don't entirely understand your file naming
system there -- it seems to say which architecture the
system images are for but not what
On 05.05.2011, at 11:56, Peter Maydell wrote:
On 5 May 2011 09:23, Ben Leslie be...@benno.id.au wrote:
FWIW, the reason why I'm not using -kernel is that the current
way the armv7m code works, it expects the provided kernel to
be a full flash image including appropriate vector table, whereas
The wiki's Documentation tab links to:
http://qemu.weilnetz.de/qemu-doc.html
But Google's first hit for qemu-doc.html is:
http://wiki.qemu.org/download/qemu-doc.html
Which exists but is not remotely the same file.
Which is correct?
Rob
On 6 May 2011 00:20, Rob Landley r...@landley.net wrote:
On 05/05/2011 05:32 PM, Peter Maydell wrote:
(ARM kernels having alas not yet got to the point where you
can build a single kernel that will boot on everything.)
Grant Likely's working on making it happen via device trees. Here's my
On 05/05/2011 06:26 PM, Alexander Graf wrote:
As an aside: I think QEMU should have an option which is just load
a plain ELF or raw binary, with no funny Linux-kernel-specific
behaviour rather than overloading -kernel to mean if it's a raw
image it's Linux and if it's an ELF file it's not.
Hi, Jan
Thank you very much for your advice. That's helpful for me.
Hi,
the subject's tag (qemu-kvm) is misleading. This is actually targeting
the uq/master patch queue, i.e. the upstream kvm staging area.
If I want to submit a patch for the qemu-kvm-git, should I use
Am 06.05.2011 01:29, schrieb Rob Landley:
The wiki's Documentation tab links to:
http://qemu.weilnetz.de/qemu-doc.html
But Google's first hit for qemu-doc.html is:
http://wiki.qemu.org/download/qemu-doc.html
Which exists but is not remotely the same file.
Which is correct?
Rob
Both were
80 matches
Mail list logo
