search for: sn2

...o I assume that no need to take any snapshot etc.. and merge back in. * does it internally use snapshot ? Does this hook in to doing fsfreeze and unfreeze using guest agent and does it automagically ? I do not see any options here. * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates a new qcow2 sparse file. Thanks /Jd

...system around the snapshot event, similar to the > existing --quiesce flag of virDomainSnapshotCreateXML (in fact, > virDomainSnaphostCreateXML might even BE the interface we use to wire up > the qemu drive-backup command) > > > * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does > > it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates > > a new qcow2 sparse file. > > If I understand the qemu command correctly, you have three choices via > the 'sync' option: the entire disk (the snapshot is a flat image...

Hi!   I want to print the output all together with a single column name   s21<-c(1:1000); var21<-lapply(s21,function(x){    ns<-rnorm(78,8,9);    n<-length(ns);    Mn<-mean(ns)    Sn2<-var(ns)    return(cbind(x,Mn,Sn2)); }); var21 but my code is giving me somewhat like the following [[1]] x   Mn          Sn2   [1,] 1 7.86 10.56540 [[2]] x   Mn          Sn2   [1,] 2 8.11 7.685347 I want to print the mean and variance as x   Mn          Sn2 1 7.86 10.56540 2 8.11 7.685347...

...and gamma () on strictly positive numbers (always greater than zero). Here is a snippet of my code: k goes from 1 to a positive limit. S is always 100. Only positive values of n are allowed into the loop. if(n>0) { while(k<=lim) { sn<-(S-n);snfact<-gamma(sn); sn2<-(2-n+S);sn2gam<-gamma(sn2); num<-(ngam*sn2gam); nk2<-(2+k-(2*n)+S); nk2gam<-gamma(nk2); den<-(k*nk2gam); prob<-(num/den); sum<-(as.numeric((k*prob))+sum); k<-k+1; } } The error message received...

...lity to quiesce the file system around the snapshot event, similar to the existing --quiesce flag of virDomainSnapshotCreateXML (in fact, virDomainSnaphostCreateXML might even BE the interface we use to wire up the qemu drive-backup command) > * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does > it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates > a new qcow2 sparse file. If I understand the qemu command correctly, you have three choices via the 'sync' option: the entire disk (the snapshot is a flat image containing contents of ba...

...napshot event, similar to the >> existing --quiesce flag of virDomainSnapshotCreateXML (in fact, >> virDomainSnaphostCreateXML might even BE the interface we use to wire up >> the qemu drive-backup command) >> >>> * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does >>> it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates >>> a new qcow2 sparse file. >> If I understand the qemu command correctly, you have three choices via >> the 'sync' option: the entire disk (the snapshot is a fla...

...Source ------------------------------------------------ vda /home/ubuntu/vm-01.img hda /dev/sr0 snapshot-create-as --domain vm-01 snap1 --diskspec vda,file=/var/lib/libvirt/sn1.qcow2 --disk-only --atomic snapshot-create-as --domain vm-01 snap2 --diskspec vda,file=/var/lib/libvirt/sn2.qcow2 --disk-only --atomic virsh #snapshot-list vm-01 ------------------------------------------------------------ snap1 2015-12-07 11:51:51 -0800 disk-snapshot snap2 2015-12-07 11:52:28 -0800 disk-snapshot virsh # snapshot-list vm-01 --tree snap1 | +- snap2...

The following fit does not make sense to me, please, correct me if I have a logical error. > moddowsn Call: coxph(formula = Surv(start, stop, resp) ~ sn + matfac2, data = coxsn1, method = "efron") coef exp(coef) se(coef) z p sn2 0.0497 1.051 0.02030 2.450 1.4e-02 sn3 -0.0532 0.948 0.02038 -2.610 9.0e-03 sn4 -0.0410 0.960 0.01979 -2.073 3.8e-02 sn5 -0.0776 0.925 0.01954 -3.973 7.1e-05 sn6 -0.1133 0.893 0.01839 -6.161 7.2e-10 sn7 -0.1252 0.882 0.01846 -6.781...

...##| subnet 2 | +----------+ +------+ +------+ +----------+ \ / \ +------+ / \| rt 3 |/ +------+ the bandwidth of the links is as follows: sn1 - rt1 100mbit sn2 - rt2 100mbit rt1 - rt2 - rt3 10mbit now there are multiple flows from sn1 to sn2. if the load on the prefered link (rt1-rt2) is 80% or more i want to utilisize the rt1-rt3-rt2 route as well. but only in this case - not normaly. so i think ecmp with weights is not the solution to...

...incremental stuff happen? Does it require qcow2 files? Does it work with raw files? Does "--copy-storage-inc" require existing snapshots? Does "--copy-storage-inc" require existing snapshots which are in an external file so that there is a visible chain [base] <- [sn1] <- [sn2] Background: I am trying to understand what really happens, so I can use the tools for a reasonable fast failover between two servers with local storage. more Background: I have VMs and bare metal servers which do use expensive shared storages like NetApp, EMC² VNX, HP and others, but the shared...

What is the current state of Xen ia64 on SGI Altix? I see some Altix patches from sgi.com, I assume this means it is tested. Is it stable? Are there more appropriate mailing lists or documentation to query? Thankyou, Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...mode=" 0, 4 and 6. I've not been able to get better than 112MB/sec, which is the same as the non-bonded interfaces. My config files are: === cat /etc/sysconfig/network-scripts/ifcfg-{eth1,eth2,bond0} # SN1 HWADDR=00:30:48:fd:26:71 DEVICE=eth1 BOOTPROTO=none MASTER=bond0 SLAVE=yes # SN2 HWADDR=00:1B:21:87:80:CE DEVICE=eth2 BOOTPROTO=none MASTER=bond0 SLAVE=yes # Bonded interfaces for Storage Network DEVICE=bond0 IPADDR=192.168.21.80 NETMASK=255.255.255.0 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS="miimon=1000 mode=0" === I'm running benchmarks using iperf (....

...+ over full virtualization. However, when run without a hypervisor + the kernel is theoretically slower and slightly larger. + + +source "arch/ia64/xen/Kconfig" + +endif + choice prompt "System type" default IA64_GENERIC @@ -137,6 +164,7 @@ config IA64_GENERIC SGI-SN2 For SGI Altix systems SGI-UV For SGI UV systems Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/> + Xen-domU For xen domU system If you don't know what to do, choose "generic". @@ -187,6 +215,10 @@ config IA64_HP_SIM bool &quo...

...+ over full virtualization. However, when run without a hypervisor + the kernel is theoretically slower and slightly larger. + + +source "arch/ia64/xen/Kconfig" + +endif + choice prompt "System type" default IA64_GENERIC @@ -137,6 +164,7 @@ config IA64_GENERIC SGI-SN2 For SGI Altix systems SGI-UV For SGI UV systems Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/> + Xen-domU For xen domU system If you don't know what to do, choose "generic". @@ -187,6 +215,10 @@ config IA64_HP_SIM bool &quo...

Hi linux/ia64 developers. Few days before Eddie posted the mail for Linux/IA64 paravirtualization. But only a few responded partially because there was no reviewable patches. Here is the patches for xen/ia64 Linux paravirtualization. The goal is to merge IA64 xen Linux paravirtualization for both domU and dom0 eventually. However the first step is to merge domU portion. As you can see from the

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions which is necessary to

...gt;> #9f5]WMS7[euOV_!JW?H_Zq\GBG>ruUx'RX5Mt}y}h'n,W >>>> fFnvGI{)})6Cj3Bjk,3w/ zb$aHIGmHnoDijcX^NgtBx{b5f&6 OpCHeEN\c(6O(fpn6/0Dnq'LpI;`0-?Q76kPf^gYv9,Fy2MnlZ)-ji[Agczp%os$4Y}P};(~:)AmA%d77 YsXZ7~:G^(:YWc*F>RvrcU2/wt)TTi7oyZfFrB7ki|#"'{g:kk}N!f>Z% %^`SN2>* **** Command 'ffnvgi{)})6cj3bjk,3w/' not recognized. >>>> Q[a!RY[3CeJIBms6)iRL0tL6k}~ud9G[)KMsLks?!$PysPmi~ **** Command 'q[a!ry[3cejibms6)irl0tl6k}~ud9g[)kmslks?!$pyspmi~' not recognized. >>>> p(Lm0fx- **** Command 'p(lm0fx-' not recognized. &g...

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. Please review and comments. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor. - Add some helper functions