search for: _destination_

Hi, Reading http://libvirt.org/hooks.html I'm wondering of the following implication is accurate: Under "QEMU guest migration" it says At the beginning of the migration, the qemu hook script on the _destination_ host is executed with the "start" operation. Above that, under "Specifics" Before a QEMU guest is started, the qemu hook script is called in two locations; if either location fails, the guest is not started. The first location, since 0.9.0, is before libvirt performs any...

..., I want to know if the _source_ is sparse, to know whether I have to bend over backwards to preallocate the destination"), then using that in qemu makes sense for my v2 patches. But for v1, my only justification was "when copying an image, I can skip holes in the source if I know the _destination_ already reads as zeroes", which only needed INIT_ZERO. Some of the nbdkit patches demonstrate the some-vs.-all nature of the two bits; for example, in the split plugin, I initialize h->init_sparse = false; h->init_zero = true; then in a loop over each file change h->init_sparse t...

...if the _source_ is > sparse, to know whether I have to bend over backwards to preallocate > the destination"), then using that in qemu makes sense for my v2 > patches. But for v1, my only justification was "when copying an > image, I can skip holes in the source if I know the _destination_ > already reads as zeroes", which only needed INIT_ZERO. > > Some of the nbdkit patches demonstrate the some-vs.-all nature of > the two bits; for example, in the split plugin, I initialize > h->init_sparse = false; h->init_zero = true; then in a loop over > each file...

...ng back out to the client on the Intranet. This problem will be true for generally classified traffic and P2P traffic. I would use tc filters in one direction if I could possibly distinguish P2P traffic from other types of traffic with them. Essentially, what I need to be able to do is match on _destination_ MAC address in the iptables POSTROUTING chain in the mangle table, but do this _before_ it goes through the tc packet classification. Ideally, what should happen is: ACK packets with no data payload always get classified in Priority Band 1 and the rest of their flow''s data gets classifi...

Chris, to put things in the right prespective, you should read (if you haven't done so already) the original paper describing the design behind batch mode. The design and implementation of this functionality goes back to a project called the Internet2 Distributed Storage Infrastructure (I2-DSI). As part of that project, the authors created a modified version of rsync (called rsync+)

I will be following up to this email with four separate threads each addressed to the appropriate single list, with proposed changes to: - the NBD protocol - qemu: both server and client - libnbd: client - nbdkit: server The feature in question adds a new optional NBD_INFO_ packet to the NBD_OPT_GO portion of handshake, adding up to 16 bits of information that the server can advertise to the