- Added vfio_device_get_from_dev() as wrapper to get
reference to vfio_device from struct device.
- Added vfio_device_data() as a wrapper to get device_data from
vfio_device.
Signed-off-by: Vijay Mohan Pandarathil
---
drivers/vfio/vfio.c | 27 +++
- Create eventfd per vfio device assigned to a guest and register an
event handler
- This fd is passed to the vfio_pci driver through the SET_IRQ ioctl
- When the device encounters an error, the eventfd is signalled
and the qemu eventfd handler gets inv
- New VFIO_SET_IRQ ioctl option to pass the eventfd that is signaled
when
an error occurs in the vfio_pci_device
- Register pci_error_handler for the vfio_pci driver
- When the device encounters an error, the error handler registered by
the vfio_pci dr
Add support for error containment when a VFIO device assigned to a KVM
guest encounters an error. This is for PCIe devices/drivers that support AER
functionality. When the host OS is notified of an error in a device either
through the firmware first approach or through an interrupt handled by the A
Handle errors and cleanup from the error in a unified place for
parse_acl_file().
Signed-off-by: Doug Goldstein
CC: Anthony Liguori
CC: Richa Marwaha
CC: Corey Bryant
TO: qemu-devel@nongnu.org
---
qemu-bridge-helper.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
Allow the bridge helper to take a config directory rather than having to
specify every file in the directory manually via an include statement.
Signed-off-by: Doug Goldstein
CC: Anthony Liguori
CC: Richa Marwaha
CC: Corey Bryant
TO: qemu-devel@nongnu.org
---
qemu-bridge-helper.c | 55
The goal is to support an 'includedir' to include all files within a
directory specified in the bridge.conf file. The rationale is to allow
libvirt to be able to configure interfaces to for use by unprivileged
users by just simply generating a new configuration file to the directory.
Change from v
Juan,
Can I try this patch that Paolo mentioned?
Does it go directly from GET_LOG_DIRTY => migration_bitmap?
Or is there still an intermediate sync in your patch?
Thanks,
- Michael
On 03/01/2013 04:34 AM, Paolo Bonzini wrote:
Il 01/03/2013 00:22, Michael R. Hines ha scritto:te
Hi,
Currentl
Hi Kuo-Jung,
On Wed, Feb 27, 2013 at 5:15 PM, Kuo-Jung Su wrote:
> From: Kuo-Jung Su
>
> The FTINTC020 interrupt controller supports both FIQ and IRQ signals
> to the microprocessor.
> It can handle up to 64 configurable IRQ sources and 64 FIQ sources.
> The output signals to the microprocessor
Hi Kuo-Jung,
On Wed, Feb 27, 2013 at 5:15 PM, Kuo-Jung Su wrote:
> From: Kuo-Jung Su
>
> The Faraday A369 EVB is a Faraday SoC platform evalution board used for
> Faraday IP functional verification based on the well-known ARM AMBA 2.0
> architecture.
>
> Signed-off-by: Kuo-Jung Su
> ---
> hw/a
On 03/01/2013 10:17 PM, Anthony Liguori wrote:
Stefan Berger writes:
On 03/01/2013 06:59 PM, Anthony Liguori wrote:
Eric Blake writes:
On 03/01/2013 04:05 PM, Anthony Liguori wrote:
Eric Blake writes:
On 03/01/2013 02:08 PM, Anthony Liguori wrote:
You can pass chardevs to the egd bac
Stefan Berger writes:
> On 03/01/2013 06:59 PM, Anthony Liguori wrote:
>> Eric Blake writes:
>>
>>> On 03/01/2013 04:05 PM, Anthony Liguori wrote:
Eric Blake writes:
> On 03/01/2013 02:08 PM, Anthony Liguori wrote:
>
You can pass chardevs to the egd backend. It's rea
Eric Blake writes:
> On 03/01/2013 04:59 PM, Anthony Liguori wrote:
>> I said this when seccomp was first introduced and I'll say it again.
>> blacklisting open() is a bad idea. DAC and MAC already exist and solve
>> this problem. We've got filesystem namespaces too.
>
> Let's explore that idea
I've updated the Gentoo docs for the flag to read:
Enable VirtFS via fsdev (host) and virtio-9p-pci (guest). See
http://wiki.qemu.org/Documentation/9psetup
Hopefully that's a bit more clear that you need to enable that for this
support.
--
You received this bug notification because you are a me
On 03/01/2013 06:59 PM, Anthony Liguori wrote:
Eric Blake writes:
On 03/01/2013 04:05 PM, Anthony Liguori wrote:
Eric Blake writes:
On 03/01/2013 02:08 PM, Anthony Liguori wrote:
You can pass chardevs to the egd backend. It's really not a good idea
to pass a fd via rng-rangom.
Why not?
On 03/01/2013 04:59 PM, Anthony Liguori wrote:
> I said this when seccomp was first introduced and I'll say it again.
> blacklisting open() is a bad idea. DAC and MAC already exist and solve
> this problem. We've got filesystem namespaces too.
Let's explore that idea a bit further. What happens
On Wed, Feb 20, 2013 at 04:13:49PM +0800, Hu Tao wrote:
> On Thu, Feb 07, 2013 at 11:50:28PM -0200, Marcelo Tosatti wrote:
> > On Wed, Jan 23, 2013 at 03:19:23PM +0800, Hu Tao wrote:
> > > From: Wen Congyang
> > >
> > > The guest should run after resetting it, but it does not run if its
> > > old
On Thu, Feb 28, 2013 at 04:54:25PM +0800, Hu Tao wrote:
> > > diff --git a/arch/x86/include/uapi/asm/kvm_para.h
> > > b/arch/x86/include/uapi/asm/kvm_para.h
> > > index 06fdbd9..c15ef33 100644
> > > --- a/arch/x86/include/uapi/asm/kvm_para.h
> > > +++ b/arch/x86/include/uapi/asm/kvm_para.h
> > > @
Ping?
On 02/14/2013 03:21 PM, Satoru Moriya wrote:
> We have some plans to migrate legacy enterprise systems which require
> low latency (10 msec order) to kvm virtualized environment. In our
> usecase, the system runs with other untrusted guests and so locking
> memory which is used by the sys
Eric Blake writes:
> On 03/01/2013 04:05 PM, Anthony Liguori wrote:
>> Eric Blake writes:
>>
>>> On 03/01/2013 02:08 PM, Anthony Liguori wrote:
>>>
>> You can pass chardevs to the egd backend. It's really not a good idea
>> to pass a fd via rng-rangom.
>>>
>>> Why not? If you are runn
On 03/01/2013 04:05 PM, Anthony Liguori wrote:
> Eric Blake writes:
>
>> On 03/01/2013 02:08 PM, Anthony Liguori wrote:
>>
> You can pass chardevs to the egd backend. It's really not a good idea
> to pass a fd via rng-rangom.
>>
>> Why not? If you are running a single guest, why can't l
Peter Krempa writes:
> On 03/01/13 21:04, Anthony Liguori wrote:
>> Eric Blake writes:
>>
>>> Stefan Berger and I discovered on IRC that virtio-rng is unable to
>>> support fd passing. We attempted:
>>>
>>> qemu-system-x86_64 ... -add-fd set=4,fd=34,opaque=RDONLY:/dev/urandom
>>> -object rng-ra
Eric Blake writes:
> On 03/01/2013 02:08 PM, Anthony Liguori wrote:
>
You can pass chardevs to the egd backend. It's really not a good idea
to pass a fd via rng-rangom.
>
> Why not? If you are running a single guest, why can't libvirt pass that
> one guest an fd instead of making qemu
On 03/01/13 21:04, Anthony Liguori wrote:
Eric Blake writes:
Stefan Berger and I discovered on IRC that virtio-rng is unable to
support fd passing. We attempted:
qemu-system-x86_64 ... -add-fd set=4,fd=34,opaque=RDONLY:/dev/urandom
-object rng-random,id=rng0,filename=/dev/fdset/4 -device
vir
On Fri, Mar 01, 2013 at 12:02:07 -0300, Eduardo Habkost wrote:
> On Fri, Mar 01, 2013 at 02:12:38PM +0100, Jiri Denemark wrote:
> > Definitely, we plan to start using "enforce" flag as soon as we have
> > better CPU probing interface with QEMU. Since libvirt does not currently
> > consult CPU specs
Buildlog from an armfh PPA build as reference.
** Attachment added:
"buildlog_ubuntu-quantal-armhf.contour_3.0-0ubuntu1~ubuntu12.10.1~ppa1_FAILEDTOBUILD.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1077116/+attachment/3553219/+files/buildlog_ubuntu-quantal-armhf.contour_3.0-0ub
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> qcow2 images now accept a boolean lazy_refcounts options. Use it like
> this:
>
> -drive file=test.qcow2,lazy_refcounts=on
>
> If the option is specified on the command line, it overrides the default
> specified by the qcow2 header flags that were set
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> Any non-default -drive options are now passed down to the block drivers.
>
> Signed-off-by: Kevin Wolf
> ---
> blockdev.c | 45 -
> 1 file changed, 40 insertions(+), 5 deletions(-)
Reviewed-by: Eric Blake
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> This adds a function that adds all entries of a QDict to a QemuOpts if
> the keys are known, and leaves only the rest in the QDict.
>
> This way a single QDict of -drive options can be processed in multiple
> places (generic block layer, block driver, ba
On 02/27/2013 06:52 PM, mdroth wrote:
On Wed, Feb 27, 2013 at 06:24:45PM -0500, Stefan Berger wrote:
This is actually exactly what test-visitor-serialization.c does. It
feeds various normal/corner cases of visit_type_* into your output
visitor, takes that output and feeds it back into the input
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> The options are passed down to the block drivers, which are supposed to
> remove all options they have processed. Anything that is left over in
> the end is an unknown option and results in an error.
>
> Signed-off-by: Kevin Wolf
> ---
> block.c | 32 +
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf
> ---
> include/qapi/qmp/qdict.h | 2 ++
> qobject/qdict.c | 22 ++
> 2 files changed, 24 insertions(+)
Reviewed-by: Eric Blake
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virt
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> It doesn't do anything yet except storing the options QDict in the
> BlockDriverState.
>
> Signed-off-by: Kevin Wolf
> ---
> block.c | 47
> +++
> block/blkverify.c | 2 +-
> block
On 03/01/2013 01:13 PM, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf
> ---
> block.c | 4 ++--
> block/bochs.c | 2 +-
> block/cloop.c | 2 +-
> block/cow.c | 2 +-
> block/dmg.c | 2 +-
> block/parallels.c | 2 +-
> b
On 03/01/2013 02:08 PM, Anthony Liguori wrote:
>>> You can pass chardevs to the egd backend. It's really not a good idea
>>> to pass a fd via rng-rangom.
Why not? If you are running a single guest, why can't libvirt pass that
one guest an fd instead of making qemu open() the file?
>>
>> Fine,
Stefan Berger writes:
> On 03/01/2013 03:04 PM, Anthony Liguori wrote:
>> Eric Blake writes:
>>
>>> Stefan Berger and I discovered on IRC that virtio-rng is unable to
>>> support fd passing. We attempted:
>>>
>>> qemu-system-x86_64 ... -add-fd set=4,fd=34,opaque=RDONLY:/dev/urandom
>>> -object
Yeah, that's probably overdue -- it should gracefully downgrade to 9p2000.u
and/or 9p2000 anyways.
-eric
On Fri, Mar 1, 2013 at 1:38 PM, H. Peter Anvin wrote:
> On 02/28/2013 04:24 AM, M. Mohan Kumar wrote:
> >
> > By default 9p.u is used, you can override by that
> > mount -t 9p -otrans=
> +#ifdef TARGET_WORDS_BIGENDIAN
> +if (arm_feature(env, ARM_FEATURE_V6)
> +|| arm_feature(env, ARM_FEATURE_V7)) {
> +/* IE and EE bits stay set for big-endian */
> +env->cp15.c1_sys |= (1 << 31) | (1 << 25);
> +}
> +#endif
This is wrong for all the CPUs QEMU crrent
> From GDB Remote Serial Protocol doc:
>
> "The bytes with the register are transmitted in target byte order."
> /* Aliases for Q regs. */
> nregs += 16;
> if (reg < nregs) {
>
> -stfq_le_p(buf, env->vfp.regs[(reg - 32) * 2]);
> -stfq_le_p(buf
Il 01/03/2013 21:13, Stefan Berger ha scritto:
> On 03/01/2013 02:37 PM, H. Peter Anvin wrote:
>> On 02/28/2013 04:36 PM, Eric Blake wrote:
>>> Stefan Berger and I discovered on IRC that virtio-rng is unable to
>>> support fd passing. We attempted:
>>>
>>> qemu-system-x86_64 ... -add-fd
>>> set=4,
On 03/01/2013 03:04 PM, Anthony Liguori wrote:
Eric Blake writes:
Stefan Berger and I discovered on IRC that virtio-rng is unable to
support fd passing. We attempted:
qemu-system-x86_64 ... -add-fd set=4,fd=34,opaque=RDONLY:/dev/urandom
-object rng-random,id=rng0,filename=/dev/fdset/4 -devic
qcow2 images now accept a boolean lazy_refcounts options. Use it like
this:
-drive file=test.qcow2,lazy_refcounts=on
If the option is specified on the command line, it overrides the default
specified by the qcow2 header flags that were set when creating the
image.
Signed-off-by: Kevin Wolf
--
Any non-default -drive options are now passed down to the block drivers.
Signed-off-by: Kevin Wolf
---
blockdev.c | 45 -
1 file changed, 40 insertions(+), 5 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index d679174..1f896ca 100644
--- a/blockde
Signed-off-by: Kevin Wolf
---
include/qapi/qmp/qdict.h | 2 ++
qobject/qdict.c | 22 ++
2 files changed, 24 insertions(+)
diff --git a/include/qapi/qmp/qdict.h b/include/qapi/qmp/qdict.h
index 6d9a4be..685b2e3 100644
--- a/include/qapi/qmp/qdict.h
+++ b/include/qapi
The guest kernel already provides the PRNG itself. We have been over this...
Stefan Berger wrote:
>On 03/01/2013 02:37 PM, H. Peter Anvin wrote:
>> On 02/28/2013 04:36 PM, Eric Blake wrote:
>>> Stefan Berger and I discovered on IRC that virtio-rng is unable to
>>> support fd passing. We attemp
This adds a function that adds all entries of a QDict to a QemuOpts if
the keys are known, and leaves only the rest in the QDict.
This way a single QDict of -drive options can be processed in multiple
places (generic block layer, block driver, backing file block driver,
etc.), where each part pick
Signed-off-by: Kevin Wolf
---
block.c | 4 ++--
block/bochs.c | 2 +-
block/cloop.c | 2 +-
block/cow.c | 2 +-
block/dmg.c | 2 +-
block/parallels.c | 2 +-
block/qcow.c | 2 +-
block/qcow2.c |
It doesn't do anything yet except storing the options QDict in the
BlockDriverState.
Signed-off-by: Kevin Wolf
---
block.c | 47 +++
block/blkverify.c | 2 +-
block/qcow2.c | 2 +-
block/vmdk.c | 2
The options are passed down to the block drivers, which are supposed to
remove all options they have processed. Anything that is left over in
the end is an unknown option and results in an error.
Signed-off-by: Kevin Wolf
---
block.c | 32 ++--
1 file changed, 26 inse
Instead of constantly keeping complaining that we need this big -blockdev
things, let's start attacking individual parts of the project. Here is the
first part, allowing block drivers to provide additional -drive options.
Any options that isn't processed by the block layer is passed to the driver
On 03/01/2013 02:37 PM, H. Peter Anvin wrote:
On 02/28/2013 04:36 PM, Eric Blake wrote:
Stefan Berger and I discovered on IRC that virtio-rng is unable to
support fd passing. We attempted:
qemu-system-x86_64 ... -add-fd
set=4,fd=34,opaque=RDONLY:/dev/urandom
^
It did!
So this issue is resolved.
Thanks!
** Summary changed:
- VirtFS (virtio-9p-pci) error: Parameter 'driver' expects device type
+ [RESOLVED] VirtFS (virtio-9p-pci) error: Parameter 'driver' expects device
type
** Changed in: qemu
Status: New => Invalid
** No longer affects: qemu-k
Eric Blake writes:
> Stefan Berger and I discovered on IRC that virtio-rng is unable to
> support fd passing. We attempted:
>
> qemu-system-x86_64 ... -add-fd set=4,fd=34,opaque=RDONLY:/dev/urandom
> -object rng-random,id=rng0,filename=/dev/fdset/4 -device
> virtio-rng-pci,rng=rng0,bus=pci.0,add
On 02/28/2013 04:24 AM, M. Mohan Kumar wrote:
>
> By default 9p.u is used, you can override by that
> mount -t 9p -otrans=virtio,version=9p2000.L tag /mnt
>
Shouldn't we change that default?
-hpa
On 02/28/2013 04:36 PM, Eric Blake wrote:
> Stefan Berger and I discovered on IRC that virtio-rng is unable to
> support fd passing. We attempted:
>
> qemu-system-x86_64 ... -add-fd
> set=4,fd=34,opaque=RDONLY:/dev/urandom
> -object rng-random,id=rng0,fil
Oh, that's fantastic - thanks for the response.
- Michael
On 03/01/2013 04:34 AM, Paolo Bonzini wrote:
Il 01/03/2013 00:22, Michael R. Hines ha scritto:te
Hi,
Currently migration_bitmap_sync() is very expensive: on the order of
15-20 milliseconds by my count using timestamps (for a simple 2GB
On Fri, Mar 1, 2013 at 1:47 PM, Andreas Färber wrote:
> Am 01.03.2013 18:21, schrieb pe...@gridcentric.ca:
>
> Is it safe to use a MemoryRegion name as part of mkstemp()? "/../" seems
> rather unlikely but a "/" less so.
Since mkstemp essentially calls open, "/" does what you'd expect. So a
Memor
On Fri, Mar 01, 2013 at 06:34:31PM +, Daniel P. Berrange wrote:
> On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote:
> > Am 01.03.2013 14:12, schrieb Jiri Denemark:
> > > On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
> > >> = Listing CPU models =
> > >>
> > >> Requ
There's a USE flag for Gentoo's package "app-emulation/qemu":
virtfs Enable VirtFS support. See http://wiki.qemu.org/Documentation/9psetup
I'll try enabling it explicitly and see if it helps.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed t
Hi, Kuo-Jung
On 02/27/2013 11:15 AM, Kuo-Jung Su wrote:
> From: Kuo-Jung Su
>
> The Faraday A369 EVB is a Faraday SoC platform evalution board used for
> Faraday IP functional verification based on the well-known ARM AMBA 2.0
> architecture.
>
> Signed-off-by: Kuo-Jung Su
> ---
> hw/arm/Makefi
Am 01.03.2013 19:50, schrieb Peter Maydell:
> On 1 March 2013 18:33, Andreas Färber wrote:
>> Am 01.03.2013 17:57, schrieb Peter Maydell:
>>> The address_space field of PCIHostState was only ever written, never used.
>>> Drop it completely.
>>>
>>> Signed-off-by: Peter Maydell
>>
>> Reviewed-by:
On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote:
> Am 01.03.2013 14:12, schrieb Jiri Denemark:
> > On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
> >> = Listing CPU models =
> >>
> >> Requirement: libvirt needs to know which CPU models are available to be
> >> used
>
Am 27.02.2013 18:25, schrieb Fabien Chouteau:
> On 02/27/2013 05:58 PM, Peter Maydell wrote:
>> On 27 February 2013 16:37, Fabien Chouteau wrote:
>>> I'm making my first steps in the ARM world by looking at R4F
>>> implementation. More specifically I'm trying to add VFP3-D16 support
>>> which is,
On 1 March 2013 18:33, Andreas Färber wrote:
> Am 01.03.2013 17:57, schrieb Peter Maydell:
>> The address_space field of PCIHostState was only ever written, never used.
>> Drop it completely.
>>
>> Signed-off-by: Peter Maydell
>
> Reviewed-by: Andreas Färber
Incidentally I suspect you could if
Am 01.03.2013 18:21, schrieb pe...@gridcentric.ca:
> From: Peter Feiner
>
> Adds ramblocks' names to their backing files when using -mem-path. Eases
> introspection and debugging.
>
> Signed-off-by: Peter Feiner
> ---
>
> On Tue, Jan 8, 2013 at 2:04 PM, Anthony Liguori wrote:
>>
>> Yes, plea
Il 01/03/2013 16:50, Fabio Fantoni ha scritto:
>>
>>
> Thanks for reply.
> I have another questions:
> What exactly does the -usb parameter that seems to be necessary for usb
> passthrough?
> I mean usb devices passed through host (with -usbdevice).
> Is the number of such passthrough usb devices l
On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote:
> Am 01.03.2013 14:12, schrieb Jiri Denemark:
> > On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
> >> = Listing CPU models =
> >>
> >> Requirement: libvirt needs to know which CPU models are available to be
> >> used
>
Am 01.03.2013 17:57, schrieb Peter Maydell:
> The address_space field of PCIHostState was only ever written, never used.
> Drop it completely.
>
> Signed-off-by: Peter Maydell
Reviewed-by: Andreas Färber
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Haw
Am 01.03.2013 14:12, schrieb Jiri Denemark:
> On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
>> = Listing CPU models =
>>
>> Requirement: libvirt needs to know which CPU models are available to be used
>> with the "-cpu" option.
>>
>> Current problem: libvirt relies on help output p
On 03/01/2013 10:53 AM, Michael Roth wrote:
> We currently maintain a whitelist of commands that are safe during
> fsfreeze. During fsfreeze, we disable all commands that aren't part of
> that whitelist.
>
> guest-sync-delimited meets the criteria for being whitelisted, and is
> also required for
On 03/01/2013 10:38 AM, Eric Blake wrote:
>> +error_setg_errno(errp, errno, "Invalid time %ld for overflow",
>> + time_ns);
>
> That wording sounds awkward. Worse, errno is NOT set to anything sane,
> so you do NOT want error_setg_errno. And %ld is wrong for int64
Is there any way to verify? I see
"/lib64/modules/3.7.5-hardened/kernel/net/9p/9pnet_virtio.ko" - is that
it?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1130769
Title:
VirtFS (virtio-9p-pci) err
I wonder if the Gentoo build has got virtio-9p enabled at all. This kind
of error message is the sort of thing QEMU often prints for a feature
like this is disabled at build time
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:/
-fsdev can take local, handle and proxy. Could you please use try with
one of them?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1130769
Title:
VirtFS (virtio-9p-pci) error: Parameter 'driver' exp
We currently maintain a whitelist of commands that are safe during
fsfreeze. During fsfreeze, we disable all commands that aren't part of
that whitelist.
guest-sync-delimited meets the criteria for being whitelisted, and is
also required for qemu-ga clients that rely on guest-sync-delimited for
re
Hosts hold on to handles provided by guest-file-open for periods that can
span beyond the life of the qemu-ga process that issued them. Since these
are issued starting from 0 on every restart, we run the risk of issuing
duplicate handles after restarts/reboots.
As a result, users with a stale copy
Tim Comer writes:
> Same result:
>
> -fsdev
> local,id=fsdev-fs0,path=/srv/files,security_model=passthrough,writeout=immediate
> -device virtio-9p-pci,fsdev=fsdev-fs0,mount_tag=files
>
> qemu-kvm: -device virtio-9p-pci,fsdev=fsdev-fs0,mount_tag=files:
> Parameter 'driver' expects devi
On 03/01/2013 02:33 AM, Lei Li wrote:
> Signed-off-by: Lei Li
> ---
> qga/commands-posix.c | 55
>
> qga/qapi-schema.json | 27 ++
> 2 files changed, 82 insertions(+)
>
> diff --git a/qga/commands-posix.c b/qga/command
Fabien Chouteau (4):
QAPI: Add ARMEB target-type
Add default config for armeb-softmmu
target-arm: Fix VFP register byte order in GDB remote
target-arm: always set endian bits in big-endian mode
default-configs/armeb-softmmu.mak |3 +++
qapi-schema.json |9 +--
CPSR.E, SCTLR.EE and SCTLR.IE
Signed-off-by: Fabien Chouteau
---
target-arm/cpu.c| 11 +++
target-arm/helper.c | 18 ++
2 files changed, 29 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
index 5dfcb74..354843e 100644
--- a/target-arm/cpu.c
+++ b/t
Signed-off-by: Fabien Chouteau
---
qapi-schema.json |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 28b070f..0615715 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -2993,10 +2993,11 @@
# Since: 1.2.0
##
{ 'enum
Just create one that includes arm-softmmu.mak.
Signed-off-by: Fabien Chouteau
---
default-configs/armeb-softmmu.mak |3 +++
1 file changed, 3 insertions(+)
create mode 100644 default-configs/armeb-softmmu.mak
diff --git a/default-configs/armeb-softmmu.mak
b/default-configs/armeb-softmmu.m
>From GDB Remote Serial Protocol doc:
"The bytes with the register are transmitted in target byte order."
Signed-off-by: Fabien Chouteau
---
target-arm/helper.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/target-arm/helper.c b/target-arm/helper.c
index e9
From: Peter Feiner
Adds ramblocks' names to their backing files when using -mem-path. Eases
introspection and debugging.
Signed-off-by: Peter Feiner
---
On Tue, Jan 8, 2013 at 2:04 PM, Anthony Liguori wrote:
>
> Yes, please submit the oneliner.
Here it is :)
The commit should probably be c
On 03/01/2013 02:32 AM, Lei Li wrote:
> Signed-off-by: Lei Li
> ---
> qga/commands-posix.c | 16
> qga/qapi-schema.json | 16
> 2 files changed, 32 insertions(+)
>
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index 0ad73f3..f159e25 100644
> --- a
The address_space field of PCIHostState was only ever written, never used.
Drop it completely.
Signed-off-by: Peter Maydell
---
Noticed this when looking at converting versatile_pci to be a subclass
of pci_host; it's nice to be able to drop the ugly fishing around in
the object struct that the tw
Each PCI Bridge has a set of implied VGA regions that are enabled when
the VGA bit is set in the bridge control register. This allows VGA
devices behind bridges. Unfortunately with VGA Enable, which we
formerly allowed but didn't back, comes along some required VGA
baggage. VGA Palette Snooping
On Thu, 2013-02-28 at 23:03 -0500, Kevin O'Connor wrote:
> On Thu, Feb 28, 2013 at 10:52:49AM -0700, Alex Williamson wrote:
> > We currently expect to find VGA devices on the root bus but we will
> > also support them below bridges iff the VGA routing across the bridges
> > is pre-configured. This
On 02/28/2013 05:13 AM, Hu Tao wrote:
> This event will be emited when the guest is panicked.
>
> Signed-off-by: Wen Congyang
> ---
> include/monitor/monitor.h | 1 +
> monitor.c | 1 +
> 2 files changed, 2 insertions(+)
Missing documentation in QMP/qmp-events.txt
--
Eric Blak
On 03/01/2013 12:36 AM, Hu Tao wrote:
> On Thu, Feb 28, 2013 at 02:12:37PM -0700, Eric Blake wrote:
>> On 02/28/2013 05:13 AM, Hu Tao wrote:
>>> This patch enables preservation of cpu runstate during save/load vm.
>>> So when a vm is restored from snapshot, the cpu runstate is restored,
>>> too.
>>
Same result:
-fsdev
local,id=fsdev-fs0,path=/srv/files,security_model=passthrough,writeout=immediate
-device virtio-9p-pci,fsdev=fsdev-fs0,mount_tag=files
qemu-kvm: -device virtio-9p-pci,fsdev=fsdev-fs0,mount_tag=files:
Parameter 'driver' expects device type
Same result with a "shor
Blue Swirl writes:
> On Thu, Feb 28, 2013 at 7:42 PM, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>>> On Thu, Feb 28, 2013 at 8:14 AM, Markus Armbruster
>>> wrote:
[...]
Looks like the JSON formatter is not just broken (we knew that already),
it's broken in machine-dependent w
On 03/01/2013 07:50 AM, Peter Lieven wrote:
> just a quick test on my desktop:
>
> ~/git/qemu$ x86_64-softmmu/qemu-system-x86_64 -k de -enable-kvm -m 1024
> -drive
> if=virtio,file=iscsi://172.21.200.31/iqn.2001-05.com.equallogic:0-8a0906-16470e107-713001aa6de511e0-001-test/0
> -vnc :1 -boot dc -
Il 01/03/2013 13:45, Paolo Bonzini ha scritto:
Il 12/02/2013 14:05, Fabio Fantoni ha scritto:
I'm making patches to enable some qemu upstream features in xen that are
missing in libxl.
I'm trying to do it just by giving arguments to qemu, and I want them to
be dynamic (e.g. without physical addr
Signed-off-by: Lluís Vilanova
---
scripts/tracetool/backend/simple.py | 18 +-
trace/simple.c | 32 +---
trace/simple.h |6 +-
3 files changed, 11 insertions(+), 45 deletions(-)
diff --git a/scripts
Signed-off-by: Lluís Vilanova
---
scripts/tracetool/backend/stderr.py | 27 ---
trace/stderr.c | 34 ++
trace/stderr.h | 11 ---
3 files changed, 14 insertions(+), 58 deletions(-)
dele
Signed-off-by: Lluís Vilanova
---
trace/default.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/trace/default.c b/trace/default.c
index c9b27a2..6e07a47 100644
--- a/trace/default.c
+++ b/trace/default.c
@@ -1,7 +1,7 @@
/*
* Default implementation for backend init
Signed-off-by: Lluís Vilanova
---
monitor.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/monitor.c b/monitor.c
index 32a6e74..e287c06 100644
--- a/monitor.c
+++ b/monitor.c
@@ -740,9 +740,18 @@ static void do_trace_event_set_state(Monitor *mon, const
QDict
This interface decouples event obtaining from interaction.
Events can be obtained through three different methods:
* identifier
* name
* simple wildcard pattern
Signed-off-by: Lluís Vilanova
---
docs/tracing.txt | 44 ---
trace/control-internal.h | 67
trac
Hello lists,
As a QEMU developper I am looking for a way to help improving qemu/kvm block
performance for $customer.
Having read about APIC-V on #qemu I looked at the intel manual in order to have
an idea of what is an APIC and what is APIC-V.
Here is a summary that I am posting so it can help
1 - 100 of 175 matches
Mail list logo
