On Sat, Jun 9, 2012 at 12:12 PM, Andreas Färber wrote:
> Am 09.06.2012 03:53, schrieb Peter Crosthwaite:
>> On Fri, Jun 8, 2012 at 7:45 PM, Andreas Färber wrote:
>>> Am 08.06.2012 06:23, schrieb Peter Crosthwaite:
Each of the two core has three interfaces (+interrupt pins):
1: Sysb
On Sat, Jun 9, 2012 at 12:09 AM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 3:48 PM, Zhi Yong Wu wrote:
>> On Fri, Jun 8, 2012 at 9:23 PM, Stefan Hajnoczi wrote:
>>> On Mon, Jun 4, 2012 at 6:29 AM, wrote:
From: Stefan Hajnoczi
The vlan feature is implemented using hubs and
On Sat, Jun 9, 2012 at 12:31 PM, Andreas Färber wrote:
> Hi,
>
> Am 09.06.2012 04:15, schrieb Peter Crosthwaite:
>> On Sat, Jun 9, 2012 at 11:54 AM, Andreas Färber wrote:
>>> Speeds up the build.
>>>
>>> xilinx_ethlite uses tswap32() and is thus target-dependent.
>>>
>>> Signed-off-by: Andreas Fä
Hi,
Am 09.06.2012 04:15, schrieb Peter Crosthwaite:
> On Sat, Jun 9, 2012 at 11:54 AM, Andreas Färber wrote:
>> Speeds up the build.
>>
>> xilinx_ethlite uses tswap32() and is thus target-dependent.
>>
>> Signed-off-by: Andreas Färber
[...]
>> --- a/hw/Makefile.objs
>> +++ b/hw/Makefile.objs
>>
On Sat, Jun 9, 2012 at 11:54 AM, Andreas Färber wrote:
> Speeds up the build.
>
> Signed-off-by: Andreas Färber
> ---
> default-configs/microblaze-softmmu.mak | 1 +
> default-configs/microblazeel-softmmu.mak | 1 +
> hw/Makefile.objs | 2 ++
> hw/microblaze/Ma
On Sat, Jun 9, 2012 at 11:54 AM, Andreas Färber wrote:
> Speeds up the build.
>
> xilinx_ethlite uses tswap32() and is thus target-dependent.
>
> Signed-off-by: Andreas Färber
> ---
> default-configs/microblaze-softmmu.mak | 1 +
> default-configs/microblazeel-softmmu.mak | 1 +
> defaul
Speeds up the build.
Signed-off-by: Andreas Färber
---
default-configs/microblaze-softmmu.mak |1 +
default-configs/microblazeel-softmmu.mak |1 +
hw/Makefile.objs |2 ++
hw/microblaze/Makefile.objs |2 --
4 files changed, 4 insertions(+), 2
Am 09.06.2012 03:53, schrieb Peter Crosthwaite:
> On Fri, Jun 8, 2012 at 7:45 PM, Andreas Färber wrote:
>> Am 08.06.2012 06:23, schrieb Peter Crosthwaite:
>>> Each of the two core has three interfaces (+interrupt pins):
>>>
>>> 1: Sysbus attachment for device control
>>> 2: AXI stream TX link
>>>
On Fri, Jun 8, 2012 at 11:59 PM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 3:54 PM, Zhi Yong Wu wrote:
>> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
>>> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
@@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
/* en
On Sat, Jun 9, 2012 at 11:54 AM, Andreas Färber wrote:
> Hello Edgar and Peter,
>
> With the Makefile refactoring applied now, here's the Makefile improvements
> for MicroBlaze I mentioned.
>
> All Xilinx devices that are used for more than one softmmu are compiled once
> in libhw32. Actually some
Speeds up the build.
xilinx_ethlite uses tswap32() and is thus target-dependent.
Signed-off-by: Andreas Färber
---
default-configs/microblaze-softmmu.mak |1 +
default-configs/microblazeel-softmmu.mak |1 +
default-configs/ppc-softmmu.mak |1 +
default-configs/ppc64-softm
Add #ifdef to avoid complaint about use of poisoned "env".
Signed-off-by: Blue Swirl
Signed-off-by: Andreas Färber
---
qemu-log.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-log.h b/qemu-log.h
index fccfb110..a9b3ca4 100644
--- a/qemu-log.h
+++ b/qemu-log.h
@@
Hello Edgar and Peter,
With the Makefile refactoring applied now, here's the Makefile improvements
for MicroBlaze I mentioned.
All Xilinx devices that are used for more than one softmmu are compiled once
in libhw32. Actually some also in libhw64 due to ppc440 being compiled into
ppc64, but we can
On Fri, Jun 8, 2012 at 7:45 PM, Andreas Färber wrote:
> Am 08.06.2012 06:23, schrieb Peter Crosthwaite:
>> Each of the two core has three interfaces (+interrupt pins):
>>
>> 1: Sysbus attachment for device control
>> 2: AXI stream TX link
>> 3: AXI stream RX link
> [...]
>> struct XilinxDMAConnect
Am 09.06.2012 01:34, schrieb q...@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder default_ppc while building
> qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds/421
>
> Buildbot URL: http://buildbot.b1-systems.de/
The file is located in target-ppc/, not hw/.
Signed-off-by: Andreas Färber
Cc: Paolo Bonzini
Cc: Anthony Liguori
Cc: Blue Swirl
---
hw/ppc/Makefile.objs |1 -
target-ppc/Makefile.objs |2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/ppc/Makefile.objs b/hw/pp
On Sat, Jun 9, 2012 at 12:15 AM, Anthony Liguori wrote:
> On 06/08/2012 12:23 PM, Peter Crosthwaite wrote:
>>
>> Hi all,
>>
>> Im looking to QOMifying and refactoring the AXI stream interfaces
>> between the AXI ethernet and AXI DMA modules. I could use some
>> guidance on how to do this as I can
On Fri, Jun 8, 2012 at 10:46 PM, Alexander Graf wrote:
>
> On 07.06.2012, at 02:28, Peter Crosthwaite wrote:
>
>> On Thu, Jun 7, 2012 at 1:58 AM, Alexander Graf wrote:
>>> On 06/06/2012 07:11 AM, Peter Crosthwaite wrote:
On Wed, 2012-06-06 at 01:52 +0200, Alexander Graf wrote:
>
>>>
The Buildbot has detected a new failure on builder default_openbsd_current
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/288
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: brad_openbsd
The Buildbot has detected a new failure on builder default_openbsd_4.9 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/289
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_openbsd49
Bu
Am 07.06.2012 07:05, schrieb Peter A. G. Crosthwaite:
> diff --git a/Makefile.objs b/Makefile.objs
> index 70c5c79..a9c7bb9 100644
> --- a/Makefile.objs
> +++ b/Makefile.objs
> @@ -250,6 +250,7 @@ hw-obj-$(CONFIG_SMARTCARD) += usb/dev-smartcard-reader.o
> ccid-card-passthru.o
> hw-obj-$(CONFIG_SM
The Buildbot has detected a new failure on builder default_ppc while building
qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds/421
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: qemu-ppc.opensuse.org
Build Reason:
On Fri, 2012-06-08 at 14:08 -0500, Scott Wood wrote:
> > Yes, that's basically it. The patches allow you to add a set of
> routines
> > that will be used for translating DMA accesses to system memory
> along
> > with map/unmap operations etc...
>
> How easy is it to have multi-level translation --
Hi Andreas,
I'll read your patch and try to catch your step.
Thank you very much for reviewing and comments, you make me open my
eyes on QEMU.
On Fri, Jun 8, 2012 at 9:31 PM, Andreas Färber wrote:
> Am 08.06.2012 15:28, schrieb Andreas Färber:
>> Am 08.06.2012 14:56, schrieb Max Filippov:
>>> On
Hi Max,
On Fri, Jun 8, 2012 at 8:56 PM, Max Filippov wrote:
> Hi Jia.
>
> On Fri, Jun 8, 2012 at 4:00 AM, Jia Liu wrote:
>
> [...]
>
+ case 0x0009:
+ switch (op1) {
+ case 0x03: /*l.div*/
+ LOG_DIS("l.div r%d, r%d, r%d\n", rd, ra, rb);
+
Am 08.06.2012 17:35, schrieb Andreas Färber:
> Hello Anthony,
>
> To get moving with the merge of qom-next into qemu.git, now that the Makefile
> PULL is in, please pull a first small batch, grouping patches directly related
> to fixed-width visitors.
>
> Outlook:
>
> A second batch would includ
FIPS 140-2 requires disabling certain ciphers, including DES, which is used
by VNC to obscure passwords when they are sent over the network. The
solution for FIPS users is to disable the use of VNC password auth when the
host system is operating in FIPS mode.
This patch causes QEMU to emit a mess
On Thursday, June 07, 2012 09:21:12 AM Paul Moore wrote:
> On Thursday, June 07, 2012 12:31:25 PM Alexander Graf wrote:
> > On 07.06.2012, at 05:10, Anthony Liguori wrote:
> > > On 06/07/2012 06:56 AM, Paul Moore wrote:
> > >> On Wednesday, June 06, 2012 01:56:52 AM Alexander Graf wrote:
> > >>> Th
Hi,
On 06/08/2012 10:56 PM, Erik Rull wrote:
Hans de Goede wrote:
Hi,
On 06/08/2012 06:33 PM, Erik Rull wrote:
Hi all,
when assigning USB host devices to a guest using the hostport option,
there seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a
From: Frédéric Boiteux
The 'bepo' layout (a french dvorak-like keyboard layout) was added
about one year ago, (see commit 2a3c633c1eb8692716220195b6d3fe78b7e411d0),
but I missed to declare to install it.
Signed-off-by: Frédéric Boiteux
---
Makefile |3 ++-
1 file changed, 2 insertions(+),
Am 08.06.2012 20:33, schrieb Jeff Cody:
> On 06/08/2012 01:57 PM, Kevin Wolf wrote:
>> Am 08.06.2012 19:46, schrieb Jeff Cody:
>>> On 06/08/2012 12:11 PM, Kevin Wolf wrote:
Am 08.06.2012 16:32, schrieb Jeff Cody:
> On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
>> On Fri, Jun 8, 2012 a
Hans de Goede wrote:
Hi,
On 06/08/2012 06:33 PM, Erik Rull wrote:
Hi all,
when assigning USB host devices to a guest using the hostport option,
there seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a hostport format e.g. "1.5" or "1.2"
- On my De
Public bug reported:
current version of slirp doesn't allow feeded dns address to be outside of
given network.
in many scenarios you need to provide dns server that isn't local.
this simple patch removes checking for if dns server isn't in local
subnet.
** Affects: qemu
Importance: Undecid
** Patch added: "removes checking for if dns server isn't in local subnet."
https://bugs.launchpad.net/bugs/1010484/+attachment/3180767/+files/sliprp_dns_address.diff
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
On Fri, Jun 8, 2012 at 2:52 PM, Jan Kiszka wrote:
> On 2012-06-08 14:47, Igor Mammedov wrote:
>> - Original Message -
>>> From: "Jan Kiszka"
>>> To: "Andreas Färber"
>>> Cc: "Igor Mammedov" , "Anthony Liguori"
>>> , qemu-devel@nongnu.org, "Igor
>>> Mammedov" , "Paolo Bonzini"
>>> Sent:
On Tue, 2012-06-05 at 12:26 +0200, Jan Kiszka wrote:
> On 2012-06-05 12:20, Michael S. Tsirkin wrote:
> > On Mon, Jun 04, 2012 at 04:56:01PM +0200, Jan Kiszka wrote:
> >> No user in sight.
> >>
> >> Signed-off-by: Jan Kiszka
> >
> > Just to note, currently (since the memory API changes) all users
Am 08.06.2012 15:55, schrieb Anthony Liguori:
> On 06/07/2012 08:57 PM, Andreas Färber wrote:
>> Am 04.06.2012 10:52, schrieb Jan Kiszka:
>>> We will some use this function also for property parsing, so move it
>>> over unmodified and rename it.
>>>
>>> Signed-off-by: Jan Kiszka
>>
>> These last th
On 06/08/2012 06:01 AM, Benjamin Herrenschmidt wrote:
> From there, AFAIK, the MSI code will simply do stl_le_phys, which I
> -believe- will hit a BAR that does MMIO decoding for those addresses,
> but I'll let people knowing qemu more in depth reply whether that's true
> or not.
We may run into t
On 06/08/2012 04:03 AM, Bhushan Bharat-R65777 wrote:
> Hi All,
>
> When Freescale PCI controller configured in Root Complex mode then,
> its configuration header (type 1) have one inbound BAR (BAR0, called
> as CCSRBAR).
It maps to CCSRBAR, but it's called PCICSRBAR/PEXCSRBAR.
> And rest of BARs
On Fri, 8 Jun 2012, Andreas Färber wrote:
> >>> The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
> >>>
> >>> The new approach prevents system and user emulation from diverging -- all
> >>> the hflags state is initialized in one place now.
> >>
> >> I submitted a patch
On 2012-06-08 20:20, Chegu Vinod wrote:
> On 6/8/2012 11:08 AM, Jan Kiszka wrote:
>> [CC'ing qemu as this discusses its code base]
>>
>> On 2012-06-08 19:57, Chegu Vinod wrote:
>>> On 6/8/2012 10:42 AM, Alex Williamson wrote:
On Fri, 2012-06-08 at 10:10 -0700, Chegu Vinod wrote:
> On 6/8/2
On 06/08/2012 01:57 PM, Kevin Wolf wrote:
> Am 08.06.2012 19:46, schrieb Jeff Cody:
>> On 06/08/2012 12:11 PM, Kevin Wolf wrote:
>>> Am 08.06.2012 16:32, schrieb Jeff Cody:
On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 2:19 PM, Jeff Cody wrote:
>> On 06/08/20
On 6/8/2012 11:08 AM, Jan Kiszka wrote:
[CC'ing qemu as this discusses its code base]
On 2012-06-08 19:57, Chegu Vinod wrote:
On 6/8/2012 10:42 AM, Alex Williamson wrote:
On Fri, 2012-06-08 at 10:10 -0700, Chegu Vinod wrote:
On 6/8/2012 9:46 AM, Alex Williamson wrote:
On Fri, 2012-06-08 at 1
Hi,
On 06/08/2012 06:33 PM, Erik Rull wrote:
Hi all,
when assigning USB host devices to a guest using the hostport option, there
seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a hostport format e.g. "1.5" or "1.2"
- On my Debian 6.0 full blown l
[CC'ing qemu as this discusses its code base]
On 2012-06-08 19:57, Chegu Vinod wrote:
> On 6/8/2012 10:42 AM, Alex Williamson wrote:
>> On Fri, 2012-06-08 at 10:10 -0700, Chegu Vinod wrote:
>>> On 6/8/2012 9:46 AM, Alex Williamson wrote:
On Fri, 2012-06-08 at 16:29 +, Chegu Vinod wrote:
>
Am 08.06.2012 19:46, schrieb Jeff Cody:
> On 06/08/2012 12:11 PM, Kevin Wolf wrote:
>> Am 08.06.2012 16:32, schrieb Jeff Cody:
>>> On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
On Fri, Jun 8, 2012 at 2:19 PM, Jeff Cody wrote:
> On 06/08/2012 08:42 AM, Stefan Hajnoczi wrote:
>> Note t
sys/procfs is not available everywhere (MingW does not have it).
Remove this and more unused or redundant include statements.
This fixes the broken build.
qerror.h was previously included indirectly.
Add an explicit include statement for it because it is needed.
Signed-off-by: Stefan Weil
---
On 06/08/2012 12:11 PM, Kevin Wolf wrote:
> Am 08.06.2012 16:32, schrieb Jeff Cody:
>> On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
>>> On Fri, Jun 8, 2012 at 2:19 PM, Jeff Cody wrote:
On 06/08/2012 08:42 AM, Stefan Hajnoczi wrote:
> Note that block-commit cannot work on the top-most im
Am 08.06.2012 18:20, schrieb Maciej W. Rozycki:
> On Fri, 8 Jun 2012, Meador Inge wrote:
>
>>> The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
>>> The new approach prevents system and user emulation from diverging -- all
>>> the hflags state is initialized in one place
Please review this patch series if you could. I apologize for sending
it more than once. Thanks!
--
Regards,
Corey
On 06/08/2012 11:42 AM, Corey Bryant wrote:
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In oth
We have just completed a netmap extensions that let you build a
local high speed switch called VALE which i think can be very useful.
http://info.iet.unipi.it/~luigi/vale/
VALE is a software Virtual Local Ethernet whose ports are accessible
using the netmap API. Designed to be used as the
On Wed, May 30, 2012 at 03:50:37PM -0300, Luiz Capitulino wrote:
> On Mon, 21 May 2012 17:59:53 +0100
> "Daniel P. Berrange" wrote:
> > +/* Global, one-time initializer to configure the rate limiting
> > + * and initialize state */
> > +static void monitor_protocol_event_init(void)
> > +{
> > +
From: Paolo Bonzini
Range checking in PropertyInfo is now used only for pci_devfn
properties and some error reporting. Remove all code that implements
it in the various property types, and the now unused fields.
Signed-off-by: Paolo Bonzini
[AF: Fix blocksize min/max for 32-bit hosts by using
From: Michael Roth
Signed-off-by: Michael Roth
Signed-off-by: Andreas Färber
---
tests/test-visitor-serialization.c | 40
1 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/tests/test-visitor-serialization.c
b/tests/test-visitor-serializatio
Hi all,
when assigning USB host devices to a guest using the hostport option, there
seem to be different formats, when calling info usbhost:
- On my vanilla kernel linux there is a hostport format e.g. "1.5" or "1.2"
- On my Debian 6.0 full blown linux there is a hostport format "2" or "4",
t
From: Michael Roth
Valid range for devfn is -1 to 255 (-1 for automatic assignment). We do
not currently validate this due to devfn being stored as a uint32_t.
This can lead to segfaults and other strange behavior.
We could technically just cast it to int32_t to implement the checking,
but this
From: Michael Roth
This adds visitor interfaces for fixed-width integers types.
Implementing these in visitors is optional, otherwise we fall back to
visit_type_int() (int64_t) with some additional bounds checking to avoid
integer overflows for cases where the value fetched exceeds the bounds
of
On Fri, 8 Jun 2012, Meador Inge wrote:
> > The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
> > The new approach prevents system and user emulation from diverging -- all
> > the hflags state is initialized in one place now.
>
> I submitted a patch to fix this issue and
From: Michael Roth
This introduces {get,set}_uint{8,16,32,64}() functions for the
respective qdev types.
TADDR and VLAN are switched to explicit int64, BLOCKSIZE to uint16.
Signed-off-by: Michael Roth
Signed-off-by: Paolo Bonzini
Signed-off-by: Andreas Färber
---
hw/qdev-addr.c |4
This patch adds the passfd QMP command using the QAPI framework.
Like the getfd command, it is used to pass a file descriptor via
SCM_RIGHTS. However, the passfd command also returns the received
file descriptor, which is a difference in behavior from the getfd
command, which returns nothing.
The
This patch adds support to qemu_open to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X.
This can be used when QEMU is restricted from opening files, and
the management application opens files on QEMU's behalf.
v2:
-Get rid of file_open and move dup code to qemu_op
Am 08.06.2012 16:32, schrieb Jeff Cody:
> On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
>> On Fri, Jun 8, 2012 at 2:19 PM, Jeff Cody wrote:
>>> On 06/08/2012 08:42 AM, Stefan Hajnoczi wrote:
Note that block-commit cannot work on the top-most image since the
guest is still writing to tha
From: Michael Roth
Currently we test our visitors individually, and seperately for input
vs. output. This is useful for validating internal representations
against the native C types and vice-versa, and other visitor-specific
testing, but it doesn't cover the potential use-case of using visitor
p
From: Michael Roth
Currently string-output-visitor formats floats as %g, which is nice in
that trailing 0's are automatically truncated, but otherwise this causes
some issues:
- it uses 6 significant figures instead of 6 decimal places, which
means something like 155777.5 (which even has an
On Fri, Jun 8, 2012 at 3:48 PM, Zhi Yong Wu wrote:
> On Fri, Jun 8, 2012 at 9:23 PM, Stefan Hajnoczi wrote:
>> On Mon, Jun 4, 2012 at 6:29 AM, wrote:
>>> From: Stefan Hajnoczi
>>>
>>> The vlan feature is implemented using hubs and no longer uses
>>> special-purpose VLANState structs that are a
On Fri, Jun 08, 2012 at 12:52:54PM +0200, Juan Quintela wrote:
> Isaku Yamahata wrote:
> > This patch prepares for postcopy livemigration.
> > It introduces -postcopy option and its internal flag, migration_postcopy.
> > It introduces -postcopy-flags for chaging the behavior of incoming postcopy
>
On Fri, Jun 8, 2012 at 3:54 PM, Zhi Yong Wu wrote:
> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
>> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
>>> @@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
>>> /* end of connection */
>>> eoc:
>>> qemu_set_fd_handler
This simplifies the code and resolves TODOs.
Signed-off-by: Andreas Färber
Reviewed-by: Michael Roth
---
target-i386/cpu.c | 42 --
1 files changed, 4 insertions(+), 38 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 388bc5c..0b61
This patch converts all block layer open calls to qemu_open. This
enables all block layer open paths to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X. This is
useful if QEMU is restricted from opening certain files.
Note that this adds the O_CLOEXEC flag to the c
This patch adds the passfd QMP command using the QAPI framework.
Like the getfd command, it is used to pass a file descriptor via
SCM_RIGHTS. However, the passfd command also returns the received
file descriptor, which is a difference in behavior from the getfd
command, which returns nothing.
The
v2:
- Convert getfd and closefd to QAPI (lcapitul...@redhat.com)
- Remove changes that returned fd from getfd (lcapitul...@redhat.com)
- Wrap hmp_* functions around qmp_* functions (kw...@redhat.com)
- Move hmp_* functions to hmp.c (lcapitul...@redhat.com)
- Drop .user_print lines (lcapitul...
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from opening
files that do not belong to it.
sVirt provides this support by labeling guests and resources with
Please ignore this series. Something is amiss. I'll be resending.
--
Regards,
Corey
On 06/08/2012 10:49 AM, Corey Bryant wrote:
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to p
Please ignore this series as well. Something is amiss. I'll be resending.
--
Regards,
Corey
On 06/08/2012 10:53 AM, Corey Bryant wrote:
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELi
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from opening
files that do not belong to it.
sVirt provides this support by labeling guests and resources with
Hello Anthony,
To get moving with the merge of qom-next into qemu.git, now that the Makefile
PULL is in, please pull a first small batch, grouping patches directly related
to fixed-width visitors.
Outlook:
A second batch would include the QBus refactoring - still cherry-picking,
reordering and r
v2:
- Convert getfd and closefd to QAPI (lcapitul...@redhat.com)
- Remove changes that returned fd from getfd (lcapitul...@redhat.com)
- Wrap hmp_* functions around qmp_* functions (kw...@redhat.com)
- Move hmp_* functions to hmp.c (lcapitul...@redhat.com)
- Drop .user_print lines (lcapitul...
This patch converts all block layer open calls to qemu_open. This
enables all block layer open paths to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X. This is
useful if QEMU is restricted from opening certain files.
Note that this adds the O_CLOEXEC flag to the c
v2:
- Convert getfd and closefd to QAPI (lcapitul...@redhat.com)
- Remove changes that returned fd from getfd (lcapitul...@redhat.com)
- Wrap hmp_* functions around qmp_* functions (kw...@redhat.com)
- Move hmp_* functions to hmp.c (lcapitul...@redhat.com)
- Drop .user_print lines (lcapitul...
This patch converts all block layer open calls to qemu_open. This
enables all block layer open paths to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X. This is
useful if QEMU is restricted from opening certain files.
Note that this adds the O_CLOEXEC flag to the c
This patch adds support to qemu_open to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X.
This can be used when QEMU is restricted from opening files, and
the management application opens files on QEMU's behalf.
v2:
-Get rid of file_open and move dup code to qemu_op
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from opening
files that do not belong to it.
sVirt provides this support by labeling guests and resources with
This patch adds support to qemu_open to dup(X) a pre-opened file
descriptor if the filename is of the format /dev/fd/X.
This can be used when QEMU is restricted from opening files, and
the management application opens files on QEMU's behalf.
v2:
-Get rid of file_open and move dup code to qemu_op
This patch adds the passfd QMP command using the QAPI framework.
Like the getfd command, it is used to pass a file descriptor via
SCM_RIGHTS. However, the passfd command also returns the received
file descriptor, which is a difference in behavior from the getfd
command, which returns nothing.
The
On Fri, 2012-06-08 at 17:05 +0200, Jan Kiszka wrote:
> On 2012-06-08 16:56, Alex Williamson wrote:
> > The difference between VFIO and kvm device assignment is that VFIO
> > emulates a lot of config space for us, so most things are passed
> > through.
>
> That's not different from current device a
On 2012-06-08 16:56, Alex Williamson wrote:
> The difference between VFIO and kvm device assignment is that VFIO
> emulates a lot of config space for us, so most things are passed
> through.
That's not different from current device assignment, is it? I think the
major difference is that VFIO filte
On Fri, Jun 08, 2012 at 03:00:56PM +0200, Alexander Graf wrote:
>
> On 07.06.2012, at 14:13, David Gibson wrote:
>
> > On Thu, Jun 07, 2012 at 01:27:56PM +0200, Alexander Graf wrote:
> >>
> >> On 07.06.2012, at 01:45, David Gibson wrote:
> >>
> >>> [snip]
> > You mean internally? Yeah, prob
Am 08.06.2012 16:07, schrieb Anthony Liguori:
> On 06/08/2012 05:48 PM, Kevin Wolf wrote:
>> Am 07.06.2012 03:17, schrieb Anthony Liguori:
>>> On 06/04/2012 07:13 PM, Kevin Wolf wrote:
The following changes since commit
8cc9b43f7c5f826b39af4b012ad89bb55faac29c:
target-micro
On Fri, 2012-06-08 at 16:43 +0200, Jan Kiszka wrote:
> On 2012-06-08 16:00, Alexey Kardashevskiy wrote:
> > 08.06.2012 21:30, Jan Kiszka пишет:
> >> On 2012-06-08 13:16, Alexey Kardashevskiy wrote:
> >>> 08.06.2012 20:56, Jan Kiszka написал:
> On 2012-06-08 10:47, Alexey Kardashevskiy wrote:
>
On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
>> @@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
>> /* end of connection */
>> eoc:
>> qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
>> + qemu_set_fd_handler(
On Tue, Jun 5, 2012 at 11:04 PM, Paolo Bonzini wrote:
> This is v3 of the alternative implementation of writethrough caching
> for QEMU 1.2. By always opening drivers in writethrough mode and
> doing flushes manually after every write, it achieves three objectives:
> 1) it makes flipping the cach
On Fri, Jun 8, 2012 at 9:23 PM, Stefan Hajnoczi wrote:
> On Mon, Jun 4, 2012 at 6:29 AM, wrote:
>> From: Stefan Hajnoczi
>>
>> The vlan feature is implemented using hubs and no longer uses
>> special-purpose VLANState structs that are accessible as qdev
>> properties.
>>
>> Signed-off-by: Stefa
On Tue, Jun 5, 2012 at 11:04 PM, Paolo Bonzini wrote:
> This is v3 of the alternative implementation of writethrough caching
> for QEMU 1.2. By always opening drivers in writethrough mode and
s/writethrough/writeback/
> doing flushes manually after every write, it achieves three objectives:
St
On Fri, Jun 8, 2012 at 10:20 PM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 3:15 PM, Zhi Yong Wu wrote:
>> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
>>> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
@@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
/* en
On 2012-06-08 16:00, Alexey Kardashevskiy wrote:
> 08.06.2012 21:30, Jan Kiszka пишет:
>> On 2012-06-08 13:16, Alexey Kardashevskiy wrote:
>>> 08.06.2012 20:56, Jan Kiszka написал:
On 2012-06-08 10:47, Alexey Kardashevskiy wrote:
> Yet another try :)
>
> Normally the pci_add_capabi
On Fri, Jun 8, 2012 at 10:20 PM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 3:15 PM, Zhi Yong Wu wrote:
>> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
>>> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
@@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
/* en
On 06/08/2012 09:53 AM, Stefan Hajnoczi wrote:
> On Fri, Jun 8, 2012 at 2:19 PM, Jeff Cody wrote:
>> On 06/08/2012 08:42 AM, Stefan Hajnoczi wrote:
>>> On Thu, Jun 7, 2012 at 3:14 PM, Jeff Cody wrote:
On 06/07/2012 02:19 AM, Taisuke Yamada wrote:
>>> We want to commit snap1.qcow2 down into v
On Fri, Jun 8, 2012 at 3:15 PM, Zhi Yong Wu wrote:
> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi wrote:
>> On Thu, Jun 7, 2012 at 3:54 PM, wrote:
>>> @@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
>>> /* end of connection */
>>> eoc:
>>> qemu_set_fd_handler
On 06/08/2012 10:17 PM, Michael S. Tsirkin wrote:
On Fri, Jun 08, 2012 at 02:45:47PM +0200, Jan Kiszka wrote:
On 2012-06-08 14:18, Andreas Färber wrote:
Am 08.06.2012 14:14, schrieb Jan Kiszka:
On 2012-06-08 14:03, Andreas Färber wrote:
Can't understand that you're trying to push your v1 so h
On 06/08/2012 09:59 PM, Paul Brook wrote:
Of course we then hit the usual problem with QOM that we can only link
to objects, and it's impossible to expose multiple interfaces of the
same type.
I'm pretty sure Anthony claimed this was entirely possible --
presumably that's how Pins are going to
1 - 100 of 191 matches
Mail list logo
