search for: _identical_

Hello World! (In particular, that part of it ouside the USA and Canada) I have (with official sanction of the organisation concerned) a LEGAL site for the distribution of crypt and Kerberos code. The secure code (crypt) is _identical_ to the US code. It originated in South Africa and Australia, and has never been to the US, so it is totally kosher. The Kerberos (eBones actually) code stared out life like the secure stuff, but as the US code was worked on, the changes were tracked with code legally available outside the US, so t...

...cgi?id=198621 > > > > In short: there is no (live) migration support for nested VMX yet. So as > > soon as your guest is using VMX itself ("nVMX"), this is not expected to > > work. > > Actually, live migration with nVMX _does_ work insofar as you have > _identical_ CPUs on both source and destination — i.e. use the QEMU > '-cpu host' for the L1 guests. At least that's been the case in my > experience. FWIW, I frequently use that setup in my test environments. Correcting my erroneous statement above: For live migration to work in a nested...

..._bug.cgi?id=198621 >> >> In short: there is no (live) migration support for nested VMX yet. So as >> soon as your guest is using VMX itself ("nVMX"), this is not expected to >> work. > > Actually, live migration with nVMX _does_ work insofar as you have > _identical_ CPUs on both source and destination — i.e. use the QEMU > '-cpu host' for the L1 guests. At least that's been the case in my > experience. FWIW, I frequently use that setup in my test environments. > Your mixing use cases. While you talk about migrating a L2, this is about...

I don't have a copy of Dobson (1990) from which the glm.D93 example is taken in example("glm"), but I'm strongly suspecting that these are made-up data rather than real data; the means of the responses within each treatment are _identical_ (equal to 16 2/3), so two of the parameters are estimated as being zero (within machine tolerance). (At this moment I don't understand why the means rather than the geometric means being identical is what matters ...) This therefore feels like a somewhat strange (i.e. non-generic) example t...

...imilarly, you can't have one queue that has "ackcall=yes", and another with "ackcall=no". 3) I have the _exact_ same source version of CVS HEAD (from 2005/07/31) running on different servers (after a "cvs co", I tar the source so that I can be sure I'm running _identical_ versions). On one machine, when an Agent logs in, I can see it in the DB, "database show" shows a key of: //Agents/1001 : 721001@internal;1001 On another machine, the DB shows _nothing_, yet the AgentCallbackLogin application works correctly (logging agents in and out), and shows the...

On 07.02.2018 16:31, Kashyap Chamarthy wrote: > [Cc: KVM upstream list.] > > On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >> Hi everyone, >> >> I hope this is the correct list to discuss this issue; please feel >> free to redirect me otherwise. >> >> I have a nested virtualization setup that looks as follows: >> >> - Host:

...tps://bugzilla.kernel.org/show_bug.cgi?id=198621 > > In short: there is no (live) migration support for nested VMX yet. So as > soon as your guest is using VMX itself ("nVMX"), this is not expected to > work. Actually, live migration with nVMX _does_ work insofar as you have _identical_ CPUs on both source and destination — i.e. use the QEMU '-cpu host' for the L1 guests. At least that's been the case in my experience. FWIW, I frequently use that setup in my test environments. Just to be quadruple sure, I did the test: Migrate an L2 guest (with non-shared storage),...

I am having a problem with asterisk not being stable enough for production use. I have two cards, the digium TE406P, and the TE410P. The TE410P is the primary card that I am using but I would like to move to the TE406P for the echo cancellation and more flexibility of PCI slots available. General config info: 3 PRIs, configured as such: span=1,2,0,esf,b8zs span=2,0,0,esf,b8zs

So, strangely, I have two _identical_ dualproc xeon mobos (same bios/ipmi versions, they even share an enclosure, one is right side, other is left), each with different cpu/memory: Using 4.9.13 with vcpu limited to 4, early in the boot process, the one that _was_ booting before setting the xen vcpu args says: "[ 7.060720] smp...

Thanks everyone for the replies. After some experimentation, I found that the order in which the passes are specified matters: opt -O3 -profile-loader matmult.bc -o matmult.opt.bc (works) opt -profile-loader -O3 matmult.bc -o matmult.opt.bc (does not work) Also, I am able to avoid the inconsistency warning only for optimization levels -O3 and -O2. I get that warning when using -O1 and

i've released the first beta of my e-book converter-tool. you are invited to throw stones at it (and at me) if you like: > http://jaguarps.com "beta" is a compromise. i developed it on a mac, so that particular version is solid. but "alpha" would be a better label for the status of the windows and linux versions, so if you have one of _those_ machines, and you

Sad to say that I already tested 4.9.20-26 from your repo yesterday...it does look a little cleaner before it dies, but still dies. I have not tested it with the vcpu=4 wokaround, but I can tonight if you would like. Relevant bits below: Loading Xen 4.6.3-12.el7 ... Loading Linux 4.9.20-26.el7.x86_64 ... Loading initial ramdisk ... [ 0.000000] Linux version 4.9.20-26.el7.x86_64 (mockbuild@)

PATCH 1 ======= On my machine tc does not parse filter "sample" for the u32 filter. Eg: tc filter add dev eth2 parent 1:0 protocol ip prio 1 u32 ht 801: \ classid 1:3 \ sample ip protocol 1 0xff match ip protocol 1 0xff Illegal "sample" The reason is a missing memset. This patch fixes it. diff -Nur iproute-20051007.keep/tc/f_u32.c iproute-20051007/tc/f_u32.c