On Thu, Sep 29, 2011 at 12:31:39PM +0200, Paolo Bonzini wrote:
On 09/29/2011 06:19 AM, David Gibson wrote:
This patch updates the SLOF submodule and recompiled image. The new
SLOF versions contains two changes of note:
* The previous SLOF has a bug in SCSI condition handling that was
On 2011-09-29 21:45, Blue Swirl wrote:
On Wed, Sep 28, 2011 at 9:18 PM, Jan Kiszka jan.kis...@web.de wrote:
On 2011-09-28 20:01, Blue Swirl wrote:
On Wed, Sep 28, 2011 at 11:00 AM, Jan Kiszkajan.kis...@siemens.com
wrote:
As we clearly modify the PIC state on pic_reset, we also have to
From: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
Changes in v2:
- keep slavio_intctl local, introduce sun4m_pic/irq_info instead
hw/an5206.c | 10 --
hw/arm_pic.c| 11 ---
hw/cris_pic_cpu.c |6
On 2011-09-30 01:46, Richard Henderson wrote:
This allows us to generate unwind info for the dynamicly generated
code in the code_gen_buffer. Only i386 is converted at this point.
Signed-off-by: Richard Henderson r...@twiddle.net
---
elf.h |1 +
exec.c
Alex Graf has added support for KVM acceleration of the pseries
machine, using his Book3S-PR KVM variant, which runs the guest in
userspace, emulating supervisor operations. Recent kernels now have
the Book3S-HV KVM variant which uses the hardware hypervisor features
of recent POWER CPUs. Alex's
At present, using the hypervisor aware Book3S-HV KVM will only work
with qemu on POWER7 CPUs. PPC970 CPUs also have hypervisor
capability, but they lack the VRMA feature which makes assigning guest
memory easier.
In order to allow KVM Book3S-HV on PPC970, we need to specially
allocate the first
are at
https://github.com/dgibson/SLOF, and the image currently in qemu is
- built from git tag qemu-slof-20110323.
+ built from git tag qemu-slof-20110930.
- The PXE roms come from the iPXE project. Built with BANNER_TIME 0.
Sources available at http://ipxe.org. Vendor:Device ID - ROM
Alex Graf has already made qemu support KVM for the pseries machine
when using the Book3S-PR KVM variant (which runs the guest in
usermode, emulating supervisor operations). This code allows gets us
very close to also working with KVM Book3S-HV (using the hypervisor
capabilities of recent POWER
The pseries machine of qemu implements the TCE mechanism used as a
virtual IOMMU for the PAPR defined virtual IO devices. Because the
PAPR spec only defines a small DMA address space, the guest VIO
drivers need to update TCE mappings very frequently - the virtual
network device is particularly
I've finally managed to reproduce a very infrequent kernel boot hang
by forcing TCG (so it runs slower, bug seems to be timing sensitive)
and running a boot test in a loop thousands of times.
I'd like to find out where in the guest kernel this is looping.
Unfortunately I don't have access to
Sufficiently recent PAPR specifications define properties ibm,vmx
and ibm,dfp on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the
Currently the kvmppc_get_clockfreq() function reads the host's clock
frequency from /proc/device-tree, which is useful to past to the guest
in KVM setups. However, there are some other host properties
advertised in the device tree which can also be relevant to the
guests.
This patch, therefore,
Current versions of the PowerPC architecture require and fully define
4kB and 16MB page sizes. Other pagesizes (e.g. 64kB, 1MB) are
permitted and are often supported, but the exact encodings used to set
the up can vary from chip to chip.
The supported pagesizes and required encodings are
This series contains some patches which, when using KVM, gather
information about the capabilities of the host CPU and advertise them
to the guest system when using the pseries machine. Specifically it
does this for whether the CPU supports VMX, VSX and/or DFP
instructions, and for the CPUs
This patch excludes I/O requests ending with error from the
accounting of operations, bytes and time, and adds accounting
for errors separately.It could make the statistics more accurate
and record the number of I/O failure.
Signed-off-by: Mark Wu wu...@linux.vnet.ibm.com
---
block.c |
On Thu, Sep 29, 2011 at 09:07:19PM +0200, Robert P wrote:
Hello,
I still have a problem with the Live Snapshot feature of QEMU and
before migrating to XEN, VMware or something similare, a quick post here:
OS: Ubuntu Natty 64bit
First, i'm starting my KVM Machine with an image like
Am 30.09.2011 um 09:50 schrieb David Gibson da...@gibson.dropbear.id.au:
This series contains some patches which, when using KVM, gather
information about the capabilities of the host CPU and advertise them
to the guest system when using the pseries machine. Specifically it
does this for
On Fri, Sep 30, 2011 at 12:28 AM, q...@buildbot.b1-systems.de wrote:
The Buildbot has detected a new failure on builder default_x86_64_rhel5 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_x86_64_rhel5/builds/24
Build error on RHEL 5
With PowerKVM, exits from KVM to qemu are even more expensive than on
x86. One significant source of these we're finding (since we usually
work in -nographic mode) is the nographic_timer.
At present, we're using a hack to disable it, but that's obviously not
a long term solution. From
On 2011-09-30 10:18, David Gibson wrote:
With PowerKVM, exits from KVM to qemu are even more expensive than on
x86. One significant source of these we're finding (since we usually
work in -nographic mode) is the nographic_timer.
At present, we're using a hack to disable it, but that's
On 2011-09-30 09:42, Richard W.M. Jones wrote:
I've finally managed to reproduce a very infrequent kernel boot hang
by forcing TCG (so it runs slower, bug seems to be timing sensitive)
and running a boot test in a loop thousands of times.
I'd like to find out where in the guest kernel this
On 2011-09-30 10:46, Jan Kiszka wrote:
On 2011-09-30 10:18, David Gibson wrote:
With PowerKVM, exits from KVM to qemu are even more expensive than on
x86. One significant source of these we're finding (since we usually
work in -nographic mode) is the nographic_timer.
At present, we're using
On Fri, Sep 30, 2011 at 10:49:20AM +0200, Jan Kiszka wrote:
On 2011-09-30 09:42, Richard W.M. Jones wrote:
I've finally managed to reproduce a very infrequent kernel boot hang
by forcing TCG (so it runs slower, bug seems to be timing sensitive)
and running a boot test in a loop thousands
On 30 September 2011 01:20, Peter Chubb peter.ch...@nicta.com.au wrote:
Thanks Peter!
Here's a reworked patch.
NB: when you resend patches it's better to send them as completely
fresh emails (via git-send-email or equivalent) because otherwise they're
more of a pain to apply (you end up with
On 30 September 2011 07:47, Jan Kiszka jan.kis...@web.de wrote:
There is no difference between system reset after power-up or later on.
And there should be no difference between per device, per group of
devices or system-wide reset. A device model cannot tell these apart.
I think it's also
On 2011-09-30 10:55, Jan Kiszka wrote:
On 2011-09-30 10:46, Jan Kiszka wrote:
On 2011-09-30 10:18, David Gibson wrote:
With PowerKVM, exits from KVM to qemu are even more expensive than on
x86. One significant source of these we're finding (since we usually
work in -nographic mode) is the
I'm trying to get bridge-mode communication between a macvtap and a host
macvlan working correctly, but I think I must be doing something wrong as
the host macvlan and guest macvtap apparently can't communicate. I'm aware
that the underlying eth0 interface can't communicate with the macvtap, but I
Peter == Peter Maydell peter.mayd...@linaro.org writes:
Peter On 30 September 2011 01:20, Peter Chubb
Peter peter.ch...@nicta.com.au wrote:
Thanks Peter!
Here's a reworked patch.
Peter NB: when you resend patches it's better to send them as
Peter completely fresh emails (via git-send-email
On Wed, Sep 28, 2011 at 10:58:26AM +0200, Alexander Graf wrote:
On 28.09.2011, at 04:40, Alex Williamson wrote:
On Tue, 2011-09-27 at 16:28 -0500, Scott Wood wrote:
[snip]
I'm honestly pretty indifferent on ioctl vs. linear read. I got the
impression that people dislike ioctls for whatever
On Mon, Sep 26, 2011 at 12:34:52PM -0600, Alex Williamson wrote:
On Mon, 2011-09-26 at 12:04 +0200, Alexander Graf wrote:
Am 26.09.2011 um 09:51 schrieb David Gibson da...@gibson.dropbear.id.au:
[snip]
Also, if you can come up with an interface that does not have variable
length descriptors
On Mon, Sep 26, 2011 at 06:59:33PM -0500, Scott Wood wrote:
On 09/26/2011 01:34 PM, Alex Williamson wrote:
The other obvious possibility is a pure ioctl interface. To match what
this proposal is trying to describe, plus the runtime interfaces, we'd
need something like:
/* :0 - PCI
On Mon, Sep 26, 2011 at 12:04:47PM +0200, Alexander Graf wrote:
Am 26.09.2011 um 09:51 schrieb David Gibson da...@gibson.dropbear.id.au:
[snip]
Um, not to put too fine a point on it, this is madness.
Yes, it's very flexible and can thereby cover a very wide range of
cases. But it's
This allows the user to add custom parameters to the up or down
scripts.
Extra parameters are useful in more complex networking scenarios
where we would like to configure network devices when starting
or stopping the guest.
Cc: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Sasha Levin
On Thu, Sep 29, 2011 at 11:42:47PM +0530, M. Mohan Kumar wrote:
On Wednesday, September 28, 2011 08:29:06 PM Daniel P. Berrange wrote:
On Wed, Sep 28, 2011 at 07:49:34PM +0530, M. Mohan Kumar wrote:
Pass-through security model in QEMU 9p server needs root privilege to do
few file
On Fri, Sep 30, 2011 at 10:20:14AM +0200, Alexander Graf wrote:
Am 30.09.2011 um 09:50 schrieb David Gibson da...@gibson.dropbear.id.au:
This series contains some patches which, when using KVM, gather
information about the capabilities of the host CPU and advertise them
to the guest
On 30 September 2011 10:23, Peter Chubb peter.ch...@nicta.com.au wrote:
Peter == Peter Maydell peter.mayd...@linaro.org writes:
Peter hw_error() is a fatal error -- don't use it for conditions that
Peter can be triggered by a malicious guest. (And since it's noreturn
Peter there's not much
This is conceptually cleaner and will allow us to drop the nographic
timer. Moreover, it will be mandatory to fully exploit future per-device
coalesced MMIO rings.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/g364fb.c |4
hw/vga.c|4
vl.c|2 --
3
We flush coalesced MMIO in the device models now, and VNC - for which
this was once introduced - is also fine without it as it has its own
refresh timer.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
vl.c | 13 -
1 files changed, 0 insertions(+), 13 deletions(-)
diff --git
This patchset introduces Qemu Tracing to 9p pdu handlers and removes the
existing debug infrastructure which became less meaningful after the
introduction of coroutines. With the existing debug infra, parallel
operations creates a messy output and filtering becomes difficult.
With Qemu tracing in
This python script allows to pretty print 9p simpletrace logs and can be
further enhanced to filter 9p logs based on command line arguments.
Signed-off-by: Harsh Prateek Bora ha...@linux.vnet.ibm.com
---
scripts/analyse-9p-simpletrace.py | 142 +
1 files
Plan is to replace the existing debug infrastructure with Qemu tracing
infrastructure so that user can dynamically enable/disable trace events and
therefore a meaningful trace log can be generated which can be further
filtered using an analysis script.
Note: Because of current simpletrace
Removing the existing debug infrastrucure as proposed to be replaced by
Qemu Tracing infrastructure.
Signed-off-by: Harsh Prateek Bora ha...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
hw/9pfs/virtio-9p-debug.c | 646 -
QED's metadata caching strategy allows two parallel requests to race for
metadata lookup. The first one to complete will populate the metadata
cache and the second one will drop the data it just read in favor of the
cached data.
There is a use-after-free in qed_read_l2_table_cb() and
On 09/30/2011 04:06 PM, Harsh Prateek Bora wrote:
This python script allows to pretty print 9p simpletrace logs and can be
further enhanced to filter 9p logs based on command line arguments.
Sample ouput of this analysis script (will be added in commit log):
Pretty printing 9p
Paolo Bonzini writes:
These will be used when moving icount accounting to cpus.c.
I have something related to this kind of refactoring. While trying to understand
all the timing facilities in QEMU, I wrote some (unfinished) patches that try to
disentangle much of the code in qemu-timer into two
On 09/29/2011 10:46 PM, Stefan Hajnoczi wrote:
On Thu, Sep 29, 2011 at 06:09:47PM +0530, Harsh Prateek Bora wrote:
This patchset introduces Qemu Tracing to 9p pdu handlers and removes the
existing debug infrastructure which becomes less meaningful after the
introduction of coroutines. Parallel
On 09/30/2011 12:52 PM, Lluís Vilanova wrote:
Paolo Bonzini writes:
These will be used when moving icount accounting to cpus.c.
I have something related to this kind of refactoring. While trying to understand
all the timing facilities in QEMU, I wrote some (unfinished) patches that try to
On 5 September 2011 23:13, Stefan Weil w...@mail.berlios.de wrote:
Do you already know when you expect qemu-users to be available?
Due to lack of interest from the maintainers of this project, I have
decided to setup an unofficial mailing list for qemu users.
Description: This unofficial
On (Fri) 30 Sep 2011 [11:39:11], Stefan Hajnoczi wrote:
QED's metadata caching strategy allows two parallel requests to race for
metadata lookup. The first one to complete will populate the metadata
cache and the second one will drop the data it just read in favor of the
cached data.
There
On Fri, Sep 30, 2011 at 11:32 AM, Robert P robp...@gmail.com wrote:
Please use Reply-All to keep qemu-devel CCed so that others can contribute.
On Fri, Sep 30, 2011 at 10:16 AM, Stefan Hajnoczi stefa...@gmail.com
wrote:
On Thu, Sep 29, 2011 at 09:07:19PM +0200, Robert P wrote:
Hello,
Paolo Bonzini writes:
On 09/30/2011 12:52 PM, Lluís Vilanova wrote:
Paolo Bonzini writes:
These will be used when moving icount accounting to cpus.c.
I have something related to this kind of refactoring. While trying to
understand
all the timing facilities in QEMU, I wrote some
On 09/29/2011 10:21 PM, Stefan Berger wrote:
On 09/21/2011 08:34 PM, Anthony Liguori wrote:
For any major feature that you're targeting to the next release, you should:
# Make sure that you've posted a patch series to qemu-devel
# Write a Feature page on the qemu.org wiki describing the
I've not looked into this at all, it's just a report that something
seems to be up. I will try to git bisect this later if no one spots
anything obvious.
The next operation after insmod virtio_blk would be insmod_virtio_net.
Guest kernel is a Fedora kernel, version
We are mapping ESCC to a static (incorrect) address on machine init. This
overlaps with our vram, rendering the screen barely usable.
Since openBIOS is clever enough to map ESCC to where it needs to be, we can
just drop that invalid map and everyone's happy.
Signed-off-by: Alexander Graf
On 09/19/2011 09:41 AM, Michael Roth wrote:
Where possible common routines are used for both input and output, thus
save on lines of code, theoretically. The added lines here are mostly
due to extra logic for each save/load routine to manipulate strings into
a unique field name for each saved
Correction:
To subscribe to the mailing list just send a blank email to:
qemu-users-subscr...@yahoogroups.com (not
qemu-users-ow...@yahoogroups.com as previoulsy stated).
You will be given the option to join the mailing list only.
Sorry for the confusion.
-- Forwarded message --
On Fri, Sep 30, 2011 at 2:04 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Sep 30, 2011 at 11:32 AM, Robert P robp...@gmail.com wrote:
Please use Reply-All to keep qemu-devel CCed so that others can contribute.
On Fri, Sep 30, 2011 at 10:16 AM, Stefan Hajnoczi stefa...@gmail.com
On 09/30/2011 08:44 AM, Ottavio wrote:
Correction:
To subscribe to the mailing list just send a blank email to:
qemu-users-subscr...@yahoogroups.com (not
qemu-users-ow...@yahoogroups.com as previoulsy stated).
You will be given the option to join the mailing list only.
Sorry for the confusion.
On 09/30/2011 08:53 AM, Anthony Liguori wrote:
On 09/30/2011 08:44 AM, Ottavio wrote:
Correction:
To subscribe to the mailing list just send a blank email to:
qemu-users-subscr...@yahoogroups.com (not
qemu-users-ow...@yahoogroups.com as previoulsy stated).
You will be given the option to join
Instead of waiting for qemu-users to go away in order to recreate it, I
decided
to just create a qemu-discuss list.
That list is now open. See
http://lists.nongnu.org/mailman/listinfo/qemu-devel
^^
On 30 September 2011 14:53, Anthony Liguori anth...@codemonkey.ws wrote:
You know, it's possible to actually talk to people instead of going off and
declaring that there's lack of interest from the maintainers.
Both me and Stefan Weil had written to you and the list asking when
qemu-users was
On 09/30/2011 08:59 AM, Anthony Liguori wrote:
On 09/29/2011 10:21 PM, Stefan Berger wrote:
On 09/21/2011 08:34 PM, Anthony Liguori wrote:
For any major feature that you're targeting to the next release, you
should:
# Make sure that you've posted a patch series to qemu-devel
# Write a
On Fri, 30 Sep 2011 08:39:49 -0500, Anthony Liguori anth...@codemonkey.ws
wrote:
On 09/19/2011 09:41 AM, Michael Roth wrote:
Where possible common routines are used for both input and output, thus
save on lines of code, theoretically. The added lines here are mostly
due to extra logic for
Hi, Ottavio
Would you like to put http://tech.groups.yahoo.com/group/qemu-users/
on http://wiki.qemu.org/MailingLists ?
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
On 09/30/2011 09:04 AM, Ottavio wrote:
On 30 September 2011 14:53, Anthony Liguorianth...@codemonkey.ws wrote:
You know, it's possible to actually talk to people instead of going off and
declaring that there's lack of interest from the maintainers.
Both me and Stefan Weil had written to you
On 09/30/2011 12:12 AM, Jan Kiszka wrote:
Breakpoint 1, __ldb_mmu (addr=1001716, mmu_idx=0)
at /home/rth/work/qemu/qemu/softmmu_template.h:86
86 {
(gdb) where
#0 __ldb_mmu (addr=1001716, mmu_idx=0)
at /home/rth/work/qemu/qemu/softmmu_template.h:86
#1 0x4afc in ?? ()
On Fri, Sep 30, 2011 at 2:46 PM, Robert P robp...@gmail.com wrote:
On Fri, Sep 30, 2011 at 2:04 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Sep 30, 2011 at 11:32 AM, Robert P robp...@gmail.com wrote:
Please use Reply-All to keep qemu-devel CCed so that others can
contribute.
On 09/28/2011 10:27 AM, Peter Maydell wrote:
Include config.h in softfloat.c, so that the target specific ifdefs in
softfloat-specialize.h are evaluated correctly. This was accidentally
broken in commit 789ec7ce2 when config-target.h was removed from
softfloat.h, and means that most targets
On Fri, Sep 30, 2011 at 12:27 PM, Amit Shah amit.s...@redhat.com wrote:
On (Fri) 30 Sep 2011 [11:39:11], Stefan Hajnoczi wrote:
QED's metadata caching strategy allows two parallel requests to race for
metadata lookup. The first one to complete will populate the metadata
cache and the second
On Fri, Sep 30, 2011 at 11:39 AM, Stefan Hajnoczi
stefa...@linux.vnet.ibm.com wrote:
QED's metadata caching strategy allows two parallel requests to race for
metadata lookup. The first one to complete will populate the metadata
cache and the second one will drop the data it just read in favor
On 09/28/2011 10:27 AM, Peter Maydell wrote:
/*
+| Select which NaN to propagate for a three-input operation.
+| For the moment we assume that no CPU needs the 'larger significand'
+| information.
+| Return values
On (Fri) 30 Sep 2011 [16:23:30], Stefan Hajnoczi wrote:
On Fri, Sep 30, 2011 at 12:27 PM, Amit Shah amit.s...@redhat.com wrote:
On (Fri) 30 Sep 2011 [11:39:11], Stefan Hajnoczi wrote:
QED's metadata caching strategy allows two parallel requests to race for
metadata lookup. The first one to
On 30 September 2011 16:28, Richard Henderson r...@twiddle.net wrote:
On 09/28/2011 10:27 AM, Peter Maydell wrote:
/*
+| Select which NaN to propagate for a three-input operation.
+| For the moment we assume that no
On 30 September 2011 15:36, qemu-devel-requ...@nongnu.org wrote:
To: Ottavio pr0f3ss0r1...@yahoo.com
Date: Fri, 30 Sep 2011 22:09:48 +0800
Subject: Re: [Qemu-devel] Correction: Announcing qemu-users - the unofficial
mailing list for qemu users (was: Now, what's left to non-developers? ... )
This series adds new trace events for correlating filenames with
BlockDriverState pointers and observing QMP monitor command input. It also
expands the bdrv_co_io_em() trace event to provide more useful information.
Basically small additions to improve observability in QEMU :).
Stefan Hajnoczi
bdrv_open_common() is a useful point to trace since it reveals the
filename and block driver for a given BlockDriverState.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block.c |2 ++
trace-events |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git
Add trace events for handle_qmp_command(), which dispatches qmp
commands, and monitor_protocol_emitter(), which produces the reply to a
qmp command.
Also remove duplicate #include trace/control.h.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
monitor.c|5 -
It is useful to know the BlockDriverState as well as the
sector_num/nb_sectors of an emulated .bdrv_co_*() request.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block.c |2 +-
trace-events |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Sep 30, 2011 at 02:11:48PM +0100, Richard W.M. Jones wrote:
I've not looked into this at all, it's just a report that something
seems to be up. I will try to git bisect this later if no one spots
anything obvious.
The next operation after insmod virtio_blk would be
We've been playing a bit with kvm-kmod-3.0b. We use a cross compile
environment, and one of my coworkers noticed that the variables in config.mak
weren't actually exported and so didn't actually have any effect.
I think something like the following patch is required.
Thanks,
Chris Friesen
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi-bus.c | 49 +++--
1 files changed, 39 insertions(+), 10 deletions(-)
diff --git a/hw/scsi-bus.c b/hw/scsi-bus.c
index c0da8c7..17acf48 100644
--- a/hw/scsi-bus.c
+++ b/hw/scsi-bus.c
@@
On Fri, 2011-09-30 at 18:46 +1000, David Gibson wrote:
On Mon, Sep 26, 2011 at 12:34:52PM -0600, Alex Williamson wrote:
On Mon, 2011-09-26 at 12:04 +0200, Alexander Graf wrote:
Am 26.09.2011 um 09:51 schrieb David Gibson da...@gibson.dropbear.id.au:
[snip]
Also, if you can come up with
This also requires little more than adding the new argument to
scsi_device_find, and the qdev property. All devices by default
end up on channel 0.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/esp.c |4 ++--
hw/lsi53c895a.c |4 ++--
hw/scsi-bus.c| 24
On 2011-09-30 19:07, Chris Friesen wrote:
We've been playing a bit with kvm-kmod-3.0b. We use a cross compile
environment, and one of my coworkers noticed that the variables in config.mak
weren't actually exported and so didn't actually have any effect.
I think something like the
Change the devs array into a linked list, and add a scsi_device_find
function to navigate the children list instead. This lets the SCSI
bus use more complex addressing.
scsi_device_find may return another LUN on the same target if none is
found that matches exactly.
Signed-off-by: Paolo Bonzini
This only requires changes in two places: in SCSIBus, we need to look
for a free LUN if somebody creates a device with a pre-existing scsi-id
but the default LUN (-1, meaning search for a free spot); in vSCSI,
we need to actually parse the LUN according to the SCSI spec.
Signed-off-by: Paolo
This patch introduces the possibility to address SCSI devices by
channel/target/LUN. New properties are introduced to define the address.
The implementation is pretty trivial, and thanks to the ReqOps mechanism
does not require introducing dummy devices representing channels and
targets.
For
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/esp.c |7 +--
hw/lsi53c895a.c |9 ++---
hw/scsi-bus.c| 27 ---
hw/scsi-disk.c |2 +-
hw/scsi.h| 11 +--
hw/spapr_vscsi.c |8 +---
hw/usb-msd.c |7
SCSI buses will need to read the children list first-to-last. This
requires using a QTAILQ, because hell breaks loose if you just try
inserting at the tail (thus reversing the order of all existing
visits from last-to-first to first-to-tail).
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
When using qemu's linux-user binaries through binfmt, argv[0] gets lost
along the execution because qemu only gets passed in the full file name
to the executable while argv[0] can be something completely different.
This breaks in some subtile situations, such as the grep and make test
suites.
The variables being written to config.mak by configure
need to be exported in order to take effect when building
the package.
The following patch fixes this in our environment.
Signed-off-by: Chris Friesen chris.frie...@genband.com
Index: kvm-kmod-3.0b/configure
On 09/30/2011 10:07 AM, Chris Friesen wrote:
We've been playing a bit with kvm-kmod-3.0b. We use a cross compile
environment, and one of my coworkers noticed that the variables in
config.mak weren't actually exported and so didn't actually have any
effect.
Please elaborate on no effect, and
Am 30.09.2011 um 19:52 schrieb Richard Henderson r...@twiddle.net:
On 09/30/2011 10:07 AM, Chris Friesen wrote:
We've been playing a bit with kvm-kmod-3.0b. We use a cross compile
environment, and one of my coworkers noticed that the variables in
config.mak weren't actually exported and so
Am 30.09.2011 um 09:50 schrieb David Gibson da...@gibson.dropbear.id.au:
Currently the kvmppc_get_clockfreq() function reads the host's clock
frequency from /proc/device-tree, which is useful to past to the guest
in KVM setups. However, there are some other host properties
advertised in the
On 09/30/2011 11:52 AM, Richard Henderson wrote:
On 09/30/2011 10:07 AM, Chris Friesen wrote:
We've been playing a bit with kvm-kmod-3.0b. We use a cross compile
environment, and one of my coworkers noticed that the variables in
config.mak weren't actually exported and so didn't actually have
Hello,
I'm converting some images without problem,
but with one i cannot (vm_import) , due to error.
( this image was creating with qemu 0.14.1 and continue to work,
windows guest image)
So, is it possible to repair this image ?
I know my email is more for qemu user list, but qemu-img check
On Fri, Sep 30, 2011 at 4:54 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Sep 30, 2011 at 2:46 PM, Robert P robp...@gmail.com wrote:
On Fri, Sep 30, 2011 at 2:04 PM, Stefan Hajnoczi stefa...@gmail.com
wrote:
On Fri, Sep 30, 2011 at 11:32 AM, Robert P robp...@gmail.com wrote:
2011/9/29 Lluís Vilanova vilan...@ac.upc.edu:
Blue Swirl writes:
2011/9/29 Lluís Vilanova vilan...@ac.upc.edu:
+static uint64_t control_io_read(void *opaque, target_phys_addr_t addr,
unsigned size)
+{
+ State *s = opaque;
+
+ uint64_t res = ldq_p(s-size);
+ uint8_t *resb =
On Thu, Sep 29, 2011 at 10:35 PM, Frans de Boer fr...@fransdb.nl wrote:
On 09/29/2011 11:49 PM, Lluís Vilanova wrote:
Blue Swirl writes:
2011/9/29 Lluís Vilanovavilan...@ac.upc.edu:
+static uint64_t control_io_read(void *opaque, target_phys_addr_t addr,
unsigned size)
+{
+ State *s =
On Fri, Sep 30, 2011 at 6:50 AM, Jan Kiszka jan.kis...@web.de wrote:
From: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Acked-by: Blue Swirl blauwir...@gmail.com
---
Changes in v2:
- keep slavio_intctl local, introduce sun4m_pic/irq_info instead
1 - 100 of 139 matches
Mail list logo
