search for: pivoting

I am using C code to create an S4 object based on Douglas Bates's example in his lecture notes on <http://www.ci.tuwien.ac.at/Conferences/DSC-2003/Tutorials/RExtensions/slide s.pdf> http://www.ci.tuwien.ac.at/Conferences/DSC-2003/Tutorials/RExtensions/slides .pdf e.g. SEXP La_DGE_dc(SEXP A) { SEXP aa = PROTECT(duplicate(A)); SEXP adims, pivot, val; int

Hi, Is it possible to "pivot" to a new image without doing blockcopy or blockpull? I know how to use snapshots and blockpull to create a new image and pivot to using it live, but what I would like to do is to have a VM switch from using imageA.qcow2 to image2.qcow2 while running. I don't see why this wouldn't be possible since some of the existing libvirt tools can do this when

I suggest adding a 'pivot' argument to qr.R, to obtain columns in the same order as the original x, so that a <- qr(x) qr.Q(a) %*% qr.R(a, pivot=TRUE) returns x. -------------------------------------------------- # File src/library/base/R/qr.R qr.R <- function(qr, complete = FALSE, pivot = FALSE) { # Args: # qr: a QR decomposition, produced by qr() # complete:

...a backing chain yet (even with the 'change-backing-file' QMP command, that is just rewriting contents of the qcow2 metadata, and not actually reopening the chain). The only way to pivot an image on a live guest is via blockcommit or blockcopy. And one of the reasons that this is so is that pivoting only makes sense if you can guarantee that both source and destination have the same guest-visible contents - but without some block job that synchronizes two images just prior to the pivot and then cleanly flushes all pending I/O at the point of the pivot, you can't make that guarantee for any...

Hi Friends, i'm new to R....I have data frame having columns X Y Z....I want to do pivot on this data frame....can any one help me on this... Thanks, Namit -- View this message in context: http://r.789695.n4.nabble.com/Create-a-Pivot-tp4637629.html Sent from the R help mailing list archive at Nabble.com.

I wonder if someone could explain how the following R idiom works (it's used in glm.fit). start <- coef start[fit$pivot] <- coef coef is a vector of coefficients, set by .Fortran("dqrls", ...). fit$pivot is a vector of integer indexes (indicating how dqrls permuted the columns of x). If coef has n elements, fit$pivot is a permutation of seq(1,5). start[fit$pivot]

...> (even with the 'change-backing-file' QMP command, that is just rewriting > contents of the qcow2 metadata, and not actually reopening the chain). > The only way to pivot an image on a live guest is via blockcommit or > blockcopy. And one of the reasons that this is so is that pivoting only > makes sense if you can guarantee that both source and destination have > the same guest-visible contents - but without some block job that > synchronizes two images just prior to the pivot and then cleanly flushes > all pending I/O at the point of the pivot, you can't make th...

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain

Hi guys, When performing live merge, in few cases, we see the following exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in wrapper return f(*a, **kw) File "/usr/share/vdsm/virt/vm.py", line 5278, in run self.tryPivot() File "/usr/share/vdsm/virt/vm.py", line 5247, in tryPivot ret =

...ith the 'change-backing-file' QMP command, that is just rewriting >> contents of the qcow2 metadata, and not actually reopening the chain). >> The only way to pivot an image on a live guest is via blockcommit or >> blockcopy. And one of the reasons that this is so is that pivoting only >> makes sense if you can guarantee that both source and destination have >> the same guest-visible contents - but without some block job that >> synchronizes two images just prior to the pivot and then cleanly flushes >> all pending I/O at the point of the pivot, you c...

Hello, I did a virsh snapshot-create-as --domain meta sn1 --diskspec vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only --atomic --no-metadata Then I successfully blockcommitted 2 disks: virsh blockcommit meta vda --active --verbose --pivot virsh blockcommit meta vdb --active --verbose --pivot But when doing virsh blockcommit meta vdc --active --verbose --pivot I got: Block commit:

...nly means it will disappear after the virtualisation session ends. > virsh dumpxml $dom > file > virsh undefine $dom > virsh blockcopy $dom /ssd/image.raw /hdd/image.raw \ > --wait --verbose --pivot > virsh define file I could not find anything about "pivot" or "pivoting"? What does --pivot do in this case? Thank you. -- Üdvözlettel / Best regards Horváth Gergely | gergely.horvath@inepex.com IneTrack - Nyomkövetés egyszerűen | Inepex Kft. Ügyfélszolgálat: support@inetrack.hu | +36 30 825 7646 | support.inetrack.hu Web: www.inetrack.hu | nyomkovetes-blog.h...

Hey guys, I tried to program quicksort like this but somethings wrong. please help >partition <- function(x, links, rechts){ > > i <- links > j <- rechts > t <- 0 > pivot <- sample(x[i:j],1) > > while(i <= j){ > > while(x[i] <= pivot){ > i = i+1} > > while(x[j] >= pivot){ > j = j-1} > > if( i

Hello, it happened with another VM: # virsh snapshot-create-as --domain rasa sn1 --diskspec vda,file=/var/lib/libvirt/images/rasa-sn1.qcow2 --disk-only --atomic --no-metadata # virsh blockcommit rasa vda --active --verbose --pivot Block commit: [100 %]error: failed to pivot job for disk vda error: block copy still active: disk 'vda' not ready for pivot yet # virsh domblklist rasa

The bug I submitted yesterday (It's not entered in the bug data base, so I have no ID for it) included a suggested fix that is not correct. It worked for the examples I gave because there was no pivoting in fact, or only pivot permutations that were idempotent. A correction that works in general on the examples I gave makes these two changes in qr.coef(): ## coef[qr$pivot, ] <- .Call("qr_coef_cmplx", qr, y, PACKAGE = "base")[1:p] coef[qr$pivot,] <- .Ca...

On Wed, Dec 28, 2016 at 01:26:12PM +0200, Ala Hino wrote: > Hi guys, > > When performing live merge, in few cases, we see the following exception: [...] > libvirtError: block copy still active: disk 'vdb' not ready for pivot yet You can see if the block operation is still in progress or not by doing: `sudo virsh blockjob vm1 vdb --info`. > That exception observed in

On Wednesday 07 January 2015 09:46:09 Eric Blake wrote: > On 01/07/2015 07:19 AM, Thomas Stein wrote: > > Hello. > > > > I'm seeing this error while doing a backup of a VM. > > > > + virsh blockcommit kaltura vda --active --verbose --pivot > > Block Commit: [100 %]error: failed to pivot job for disk vda > > error: internal error: unable to execute

...ation 3 fails. This should not happen any more, since there's code in virsh [1] which waits for the completion event from libvirtd, which is fired only when the job is actually ready to be pivoted. This code has a lot of fallback options in case when libvirtd is old or so. At any rate, manual pivoting later should help. Also probably updating to a more recent version. In case you are using a farily recent version, it's possible that there are still bugs though. Peter [1]: commit 7408403560f7d054da75acaab855a95c51a92e2b Author: Peter Krempa <pkrempa@redhat.com> Date: Mon Jul 13 17...

Hello one and all. Got a problem with libvirt 6.2.0 and qemu 5.0.0. virsh blockcommit mymachine vda --active --verbose --pivot works until it shows [100%] but it never actually pivots. It just sits there. Is this a known issue with 6.2.0 and i should try 6.3.0? For now i switched back to qemu 4.2.0 and this seems to solve the issue too. Any hints? Ahoi! t.

Can somebody tell me how to do the equivalent of a pivot table in R ? For example, if I have : var1 var2 var3 a x 10 b y 20 a z 10 b z 20 a z 10 b z 20 I could have : x y z a 1 0 2 b 0 1 2 where entries in the table are counts of var3.