similar to: Re: qemu-0.9.0 with initial tap interface

Hi @all I want to load the precompile kqemu modul on my solaris 5.10 3/05, but this dont work. MAKE --- -bash-3.00# make install cp kqemu-solaris-i386 kqemu /usr/sbin/install -f /usr/kernel/drv -m 755 -u root -g sys kqemu new owner is root kqemu installed as /usr/kernel/drv/kqemu cp kqemu-solaris-x86_64 kqemu /usr/sbin/install -f /usr/kernel/drv/amd64 -m 755 -u root -g sys kqemu new owner is

It seems that VCPU system time isn''t monotonic (using 3.0.4). It seems it might be correlated to when a VCPU is switched across real CPUs but I haven''t conclusively proved that. But e.g.: { old = { time = { version = 0x4ec pad0 = 0xe8e0 tsc_timestamp = 0x22cc8398b7194 system_time =

There seems to be a rash of posts lately where people are resetting or rebooting without getting any data, so I thought I''d post a quick overview on collecting crash dumps. If you think you''ve got a hang problem with ZFS and you want to gather data for someone to look at, then here are a few steps you should take. If you already know all about gathering crash dumps on

There is a rather serious race with copyout() and process termination in -stable. sysctl_kern_proc() loops through the allproc list writing the results to user memory. If it stalls during the copyout (e.g. the user memory has to take a vm_fault) and the process is ripped out from under it it will go looping into never never land. The solution is very simple, simply

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

Hello DTracers, The CPU caps project (http://www.opensolaris.org/os/project/rm/rctls/cpu-caps/) introduces kernel "wait queues" where threads may be placed to enforce caps. I would like to make this visible through DTrace and to add two new probes to the sched provider with the following semantics: cpucaps-sleep Probe that fires immediately before the current thread is placed on a

On 24 February 2015 at 09:01, Maarten Lankhorst <maarten.lankhorst at ubuntu.com> wrote: > While I've closed off most races in a previous patch, a small race still existed > where importing then unreffing cound cause an invalid bo. Add a test for this case. > > Racing sequence fixed: > > - thread 1 releases bo, refcount drops to zero, blocks on acquiring nvdev->lock.

On 25-02-15 15:14, Emil Velikov wrote: > On 24 February 2015 at 09:01, Maarten Lankhorst > <maarten.lankhorst at ubuntu.com> wrote: >> While I've closed off most races in a previous patch, a small race still existed >> where importing then unreffing cound cause an invalid bo. Add a test for this case. >> >> Racing sequence fixed: >> >> - thread 1

Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {

Hello CentOS Docs People! I recently used the Amavisd howto to setup a couple of mailservers, which saved me from hours of searching online and reading novels of documentation. Since Ned is taking a little break from the Amavisd page, I would like to help contribute. There were a few things I'd like to add, like GTUBE/EICAR testing and SELinux config lines. My wiki username is WilliamFong.

Signed-off-by: Maarten Lankhorst <maarten.lankhorst at ubuntu.com> --- xf86atomic.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/xf86atomic.h b/xf86atomic.h index 8c4b696..17fb088 100644 --- a/xf86atomic.h +++ b/xf86atomic.h @@ -49,6 +49,7 @@ typedef struct { # define atomic_read(x) ((x)->atomic) # define atomic_set(x, val) ((x)->atomic = (val)) # define atomic_inc(x)

Hello CentOS / RedHat / IBM folks! I am wondering if I can get a communication channel opened with someone who can affect changes win upstream RHEL? I don't have support accounts with RHEL, and use CentOS almost exclusively. I did have a direct email conversation with Mr. Daniel Walsh regarding these problems, but his answer was to create custom policy to allow what's being denied, as

I'm failing to understand how getrusage() works, which is a bit perplexing, because it doesn't seem like it would be terribly complicated. I've attached the code. My aim is to verify that I can use getrusage() to do (admittedly crude) instrumentation of which functions in my program are allocating lots of memory[1]. So I figure I can call getrusage() at various points and look at

Has anyone gotten this working? It seems it is a toolkit to allow guest OSes to have native speed OpenGL rendering. It might it be a good inclusion for Indiana. (To enable people to test it out in a VM.) http://www.cs.toronto.edu/~andreslc/vmgl/ --Brian P.S - The site said it is running on OpenSolaris _______________________________________________ indiana-discuss mailing list

While I've closed off most races in a previous patch, a small race still existed where importing then unreffing cound cause an invalid bo. Add a test for this case. Racing sequence fixed: - thread 1 releases bo, refcount drops to zero, blocks on acquiring nvdev->lock. - thread 2 increases refcount to 1. - thread 2 decreases refcount to zero, blocks on acquiring nvdev->lock. At this

I''m trying to debug a problem that requires I print the dirty pages (v_pages) list. Any suggestions? This message posted from opensolaris.org

http://bugs.freedesktop.org/show_bug.cgi?id=26756 Summary: Cannot alter brightness as normal user Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

[Initial version of this message originally sent to zfs-interest by mistake. Sorry if this appears anywhere as a duplicate.] I was noodling around with creating a backup script for my home system, and I ran into a problem that I''m having a little trouble diagnosing. Has anyone seen anything like this or have any debug advice? I did a "zfs create -r" to set a snapshot on all

what the heck is # ls -li /usr/\@LongLink 3 ---------- 1 root wheel 111 Jan 1 1970 /usr/@LongLink randy