search for: webrevs

I''d like reviewers for: 6734731 vif-vnic instances can race against each other 6734123 xpvd-event logging is dismal The webrev is at http://dme.org/solaris/webrev/xvm-script-cleanup.

We have finished a beta version of the feature. A webrev for it can be found here: http://cr.illumos.org/~webrev/sensille/fits-send/ It adds a command ''zfs fits-send''. The resulting streams can currently only be received on btrfs, but more receivers will follow. It would be great if anyone interested could give it some testing and/or review. If there are no objections,

This came up as an RFE during the conference (I believe it''s been logged as "4012008: brendan() action needed for DTrace Toolkit".) As everyone here is aware, DTrace is not quite as user friendly as it could be. For the uninitiated, it can be confusing to run a DTrace script and not see the expected output. Brendan Gregg has addressed this in the DTrace Toolkit[1] by

I''ve implemented code to send out bogus gratuitous ARP packet from vna in order to fix CR 6701114. The webrev is at: http://jurassic.eng/net/consulte.prc/export/build/xvm-6701114/webrev Some backgroud information (see CR 6701114 for more detail): During live migration of an xVM domain from one dom0 to another, the VNIC will be moved from one switch port to another. But, the

Crossbow team, The following is of interest to the Crossbow project. Since a large chunk of these changes also exist in the Crossbow gate, the delivery of this wad will result in fewer lines of changes for Crossbow''s delivery. If someone on Crossbow could participate in this review, that would be a bonus (Eric Cheng made original changes in the Crossbow gate at some point last year).

.. evidently doesn''t work. GRUB reboots the machine moments after loading stage2, and doesn''t recognise the fstype when examining the disk loaded from an alernate source. This is with SX-151. Here''s hoping a future version (with grub2?) resolves this, as well as lets us boot from raidz. Just a note for the archives in case it helps someone else get back the afternoon

I believe that I have incorporated all of the feedback given (thanks!). Changes since the 2008-11-16 version include: - ksh style & coding standards compliance in test script (Roland) - "dof_init_debug == B_FALSE" vs. "!dof_init_debug" (Adam) The updated webrev is at: http://cr.opensolaris.org/~mgerdts/6750659-2008-12-03/ -- Mike Gerdts http://mgerdts.blogspot.com/

Hi, I have got an implementation of DTrace probes for NFS v3 client. Webrev of my change is at: http://cr.opensolaris.org/~danhua/webrev/ The provider and probes are described in attached proposal. Welcome comments! Regards, Danhua -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: proposal-nfsv3client.txt URL:

See the PSARC case for rationale: http://www.opensolaris.org/jive/thread.jspa?threadID=58816&tstart=30 Review notes: If you haven''t reviewed xVM changes before it''s a bit confusing. Basically the dirs ending in .hg/ are normal webrevs. The ones with other names are webrevs of a particular MQ patch added on top (for virt-install and xen repos). ''solaris-support.diff'' shows the difference between the old and new version of the ''solaris-support'' patch to virt-install. Reminder, you can find the...

Hi, Thanks for the comment for my nfsv3client probe implementation! I have made changes accordingly. Webrev: http://cr.opensolaris.org/~danhua/webrev/ To reduce the overhead, I use a local variable to save XID, rather than alloc memory space with kmem_zalloc(). According to the overhead caused by tsd_get() and tsd_set(), I did an experiment to measure it. In this experiment, I run a dtrace

Here''s my comments for the preliminary ZFS Crypto review. - Dan Webrev: http://cr.opensolaris.org/~darrenm/zfs-crypto-gate/webrev/ General comments: DEA-1 - SCCS keywords need to be removed DEA-2 - Copyright updated ------------------------------------------------------------------ usr/src/lib/libcryptoutil/common/keyfile.c pkcs11_read_data() This code in pkcs11_read_data() scares

https://bugzilla.redhat.com/show_bug.cgi?id=466681 just to be sure that some one in xvm-team notices that before any bits from xvm-gate are putback ;) Florian

Hi, Searched for similar errors and nothing came up. Anybody know what this is? When using aggregate stddev, and then trying to print it at END, using printa, I get this error: dtrace: processing aborted: Invalid return value from callback avg works fine. Tried on two recent builds of solaris (build 89 and build 94), on two difference sparc systems. Here''s a sample script:

(networking-discuss Bcc''ed) Good morning, The Crossbow team would like to invite you to participate in the project''s third and last phase of code review. The third phase of the review starts today, and will last for two weeks. It covers the following parts of the code: VLANs Link Aggregations Xen mac_datapath_setup All drivers

We recently had a strange NFS performance anomaly between a V880 running snv_124 and two NetApp filers. To investigate, a DTrace NFSv4 (and eventually NFSv3) client provider would been extremely helpful. Unfortunately, all I could find were a request for code review of a v3 client provider and another request for help developing a v4 provider. Nothing seems to have come from those initiatives,

Network frontends currently have no way to express the set of ethernet multicast groups that they are interested in. As a consequence we deliver all multicast traffic to them. A subsequent consequence is that network interfaces used in the IO domain typically end up in promiscuous mode, which is generally undesirable. I''d like to slightly extend the inter-domain protocol to allow

http://cr.opensolaris.org/~johnlev/xvm-vnc-chown/ Now Xvnc runs as the ''jack'' user on the live CD, the password file must be owned by jack for it to work. Note that a full fix for this would make this VNC service only exist on the live CD[1]. As a temporary measure, we just disable ourselves post-install. Process question: after putting back to pkg-gate, does this need

Hi, all I want to get some information of How xVM is integrated with Crossbow project. Do some buddies have those documents or blogs? Thanks --luke