On 7/20/07 6:42 PM, "James Morris" <[EMAIL PROTECTED]> wrote:
> On Fri, 20 Jul 2007, Anthony Liguori wrote:
>
>> James Morris wrote:
>>> On Fri, 20 Jul 2007, Daniel P. Berrange wrote:
>>>
>>>
It could be - if your put the policy at the control API layer instead of
in QEMU itself.
>>
On Sat, 21 Jul 2007, Daniel P. Berrange wrote:
> obviously the UNIX user has a corresponding SELinux domain. In the remote
> case, one could map x509 certificate IDs (the remote user's identify) to
> appropriate local SELinux domains.
There is already a mechanism for conveying SELinux labels ov
Add infrastructure to qemu to make it an SELinux object manager. Currently,
the AVC is not being used, since only one permission is currently being
checked.
Index: src/kvm-userspace/qemu/vl.c
===
--- src.orig/kvm-userspace/qemu/vl.c
Hi,
After a bit more discussion about integrating SELinux and KVM, it seems that
there is little interest in adding enforcement hooks to KVM as it stands.
Once KVM gets some type of inter-vm communication mechanism, MAC hooks will
probably be added in that space.
Until then, there seems to be int
This patchset modifies libselinux to include the vm object class and the
entrypoint permission for use with the userspace qemu SELinux code.
Index: src/selinux/libselinux/include/selinux/av_permissions.h
===
--- src.orig/selinux/libs
On 7/20/07, James Morris <[EMAIL PROTECTED]> wrote:
On Fri, 20 Jul 2007, Daniel P. Berrange wrote:
> It could be - if your put the policy at the control API layer instead of
> in QEMU itself.
I think that libvirt may be a bit too high in the virtualization stack
for this control.
What benefits
On 7/20/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
David Windsor wrote:
> Hi,
>
> After a bit more discussion about integrating SELinux and KVM, it seems that
> there is little interest in adding enforcement hooks to KVM as it stands.
> Once KVM gets some type of inter-vm communication mechan
On Fri, Jul 20, 2007 at 05:57:29PM -0400, David Windsor wrote:
> On 7/20/07, James Morris <[EMAIL PROTECTED]> wrote:
> >On Fri, 20 Jul 2007, Daniel P. Berrange wrote:
> >
> >> It could be - if your put the policy at the control API layer instead of
> >> in QEMU itself.
> >
> I think that libvirt ma
David Windsor wrote:
On 7/20/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
David Windsor wrote:
> Hi,
>
> After a bit more discussion about integrating SELinux and KVM, it
seems that
> there is little interest in adding enforcement hooks to KVM as it
stands.
> Once KVM gets some type of inter
Stuart Anderson <[EMAIL PROTECTED]> writes:
> Index: qemu/linux-user/syscall.c
> ===
> --- qemu.orig/linux-user/syscall.c2007-07-19 01:42:43.0 -0400
> +++ qemu/linux-user/syscall.c 2007-07-19 01:43:18.0 -0400
> @@
At least armel implements discreet IPC calls instead of multiplexing
them through a single syscall. This patch adds support for this.
Stuart
Stuart R. Anderson [EMAIL PROTECTED]
Network & Software Engineering http:
Does this mean that there will be ACPI updates in the next Qemu release?
Thanks,
Jerry K
Sylvain Petreolle wrote:
Maybe nobody had a look on it, like these 3 others. I added their links on the
qemu-devel archives.
Implement ACPI specs 3.0, 4.7.2.5
Add support for VDI images
ipc endianness an
* Blue Swirl <[EMAIL PROTECTED]> [070719 20:46]:
> On 7/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Unhandled Exception 0x0007
> > PC = 0xffd0a55c NPC = 0xffd09374
> > Stopping execution
> >
> > So this is my report, I hope it can be of some use. I'll try to boot sparc
> > ve
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/07/20 15:54:27
Modified files:
linux-user : syscall.c syscall_defs.h
Log message:
Fix statfs(64) syscall wrapper, by Andreas Schwab.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu
I just want to report, that today I tried to launch debian 3.1 r2 sparc
net install CD for both the stable 0.9.0 and the last CVS snapshot.
While stable threw an error at me, CVS snapshot booted debian nicely and
installed on disk image. It even discovered internet access by DHCP, so
there is a
This patches residual data structures for OHW Prep.
ftp://ftp.software.ibm.com/rs6000/technology/spec/RESIDUAL.PS has been used as
reference document here. Now the Vital product data shows correctly with guest
Linux lsresidual utility.(instead of segmentation fault before patching). Also
memory
> Maybe write_long should handle unaligned addresses?
Possibly. But something is wrong.
Unaligned accesses should be done with unaligned-l@ ( addr -- quad )
instead of [EMAIL PROTECTED]
So either the pointer was calculated wrong or Solaris does not care
about alignment in l@
If you change it,
On Friday 20 July 2007, 姚春林 wrote:
> > Can you try using the other nic types? I'm most interested in the
> > results with the rtl8139 model.
>
> I have used rtl8139 the first time.Does not work.
>
> I think the etherboot is OK. because I can use it to boot from vmware.
> and the ethereal captured t
18 matches
Mail list logo
