{"push_id":1094374792,"size":84,"distinct_size":1,"ref":"refs/heads/smbios","head":"8998f2c63a13086eae3cda19aa2234cfe3f3b6ea","before":"c1364d5ecffdb047251a1ee335433b1a95a01392","commits":[{"sha":"50fc4b4bddfd6612674a5dd63a314426cf13837f","author":{"email":"8d0c4f5442cf9498d238d9385d37043f3d369145@ukr.net","name":"Yuri Chornoivan"},"message":"Fix minor typos in messages\n\nSigned-off-by: Yuri Chornoivan <yurchor@ukr.net>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/50fc4b4bddfd6612674a5dd63a314426cf13837f"},{"sha":"52f1874602b76ac857630be5d91e7cd19948d1a1","author":{"email":"8c3f1b821d9adf233f787f1527ecaa1537ea24a2@redhat.com","name":"Daniel Veillard"},"message":"Release of libvirt-1.3.4\n\n* docs/news.html.in libvirt.spec.in: update for release\n* po/*.po* : regenerated","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/52f1874602b76ac857630be5d91e7cd19948d1a1"},{"sha":"c0730e4d1277f70d591c465ce8bcaf5a3b310830","author":{"email":"87558058f6f829e5ec976c8ef960720af4ff9c7d@redhat.com","name":"John Ferlan"},"message":"Post-release version bump to 1.3.5","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/c0730e4d1277f70d591c465ce8bcaf5a3b310830"},{"sha":"0c56d94318393a8295cc0613abb6097a6fd60002","author":{"email":"e82f23e74d43760279ebcc505dac4ae70d5627d0@redhat.com","name":"Martin Kletzander"},"message":"tools: Fix connect command\n\nThe man page says: \"(Re)-Connect to the hypervisor. When the shell is\nfirst started, this is automatically run with the URI parameter\nrequested by the \"-c\" option on the command line.\"  However, if you run:\n\n  virsh -c 'test://default' 'connect; uri'\n\nthe output will not be 'test://default'.  That's because the 'connect'\ncommand does not care about any virsh-only related settings and if it is\nrun without parameters, it connects with @uri == NULL.  Not only that\ndoesn't comply to what the man page describes, but it also doesn't make\nsense.  It also means you aren't able to reconnect to whatever you are\nconnected currently.\n\nSo let's fix that in both virsh and virt-admin add a test case for it.\n\nSigned-off-by: Martin Kletzander <mkletzan@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/0c56d94318393a8295cc0613abb6097a6fd60002"},{"sha":"435ee578a0e95c12404466ef30eec306879d3f74","author":{"email":"83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com","name":"Michal Privoznik"},"message":"Revert \"rpc: Fix slow volume download (virsh vol-download)\"\n\nThis reverts commit d9c9e138f22c48626f719f880920e04c639e0177.\n\nUnfortunately, things are going to be handled differently so this\ncommit must go.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/435ee578a0e95c12404466ef30eec306879d3f74"},{"sha":"18944b7aea46dc793f7c576321bd1247eaba4a19","author":{"email":"83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com","name":"Michal Privoznik"},"message":"virnetclientstream: Process stream messages later\n\nThere are two functions on the client that handle incoming stream\ndata.  The first one virNetClientStreamQueuePacket() is a low\nlevel function that just processes the incoming stream data from\nthe socket and stores it into an internal structure. This happens\nin the client event loop therefore the shorter the callbacks are,\nthe better. The second function virNetClientStreamRecvPacket()\nthen handles copying data from internal structure into a client\nprovided buffer.\nChange introduced in this commit makes just that: new queue for\nincoming stream packets is introduced. Then instead of copying\ndata into intermediate internal buffer and then copying them into\nuser buffer, incoming stream messages are queue into the queue\nand data is copied just once - in the upper layer function\nvirNetClientStreamRecvPacket(). In the end, there's just one\ncopying of data and therefore shorter event loop callback. This\nshould boost the performance which has proven to be the case in\nmy testing.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/18944b7aea46dc793f7c576321bd1247eaba4a19"},{"sha":"809d02ca363b265804542fadc095670c43d353fe","author":{"email":"83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com","name":"Michal Privoznik"},"message":"virStream{Recv,Send}All: Increase client buffer\n\nThese are wrappers over virStreamRecv and virStreamSend so that\nusers have to care about nothing but writing data into / reading\ndata from a sink (typically a file). Note, that these wrappers\nare used exclusively on client side as the daemon has slightly\ndifferent approach. Anyway, the wrappers allocate this buffer and\nuse it for intermediate data storage until the data is passed to\nstream to send, or to the client application. So far, we are\nusing 64KB buffer. This is enough, but suboptimal because server\ncan send messages up to VIR_NET_MESSAGE_LEGACY_PAYLOAD_MAX bytes\nbig (262120B, roughly 256KB). So if we make the buffer this big,\na single message containing the data is sent instead of four,\nwhich is current situation. This means lower overhead, because\neach message contains a header which needs to be processed, each\nmessage is processed roughly same amount of time regardless of\nits size, less bytes need to be sent through the wire, and so on.\nNote that since server will never sent us a stream message bigger\nthan VIR_NET_MESSAGE_LEGACY_PAYLOAD_MAX there's no point in\nsizing up the client buffer past this threshold.\n\nSigned-off-by: Michal Privoznik <mprivozn@redhat.com>","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/809d02ca363b265804542fadc095670c43d353fe"},{"sha":"a34faf33011c5c0d7b47ee0849bf1e11635e17c5","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: process: Refresh ejectable media tray state on VM start\n\nEmpty floppy drives start with tray in \"open\" state and libvirt did not\nrefresh it after startup. The code that inserts media into the tray then\nwaited until the tray was open before inserting the media and thus\nfloppies could not be inserted.\n\nResolves: https://bugzilla.redhat.com/show_bug.cgi?id=1326660","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/a34faf33011c5c0d7b47ee0849bf1e11635e17c5"},{"sha":"833ae6b4356934e7b779c4be01bd2bf051930dde","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: hotplug: Skip waiting for tray opening if qemu doesn't notify us\n\nIf qemu doesn't support DEVICE_TRAY_MOVED event the code that attempts\nto change media would attempt to re-eject the tray even if it wouldn't\nbe notified when the tray opened. Add a capability bit and skip retrying\nfor old qemus.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/833ae6b4356934e7b779c4be01bd2bf051930dde"},{"sha":"a84d604db535b0e2365a8faaa67d1d7ebe365cdf","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: domain: Fix error message in qemuDomainDiskChangeSupported\n\ndisk->dst represents the <target> element in the XML.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/a84d604db535b0e2365a8faaa67d1d7ebe365cdf"},{"sha":"3b3debfb7f70696e55642ed34be2848d8ba4b8b7","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: domain: Check few more fields for when changing disk source\n\nBoth disk->src->shared and disk->src->readonly can't be modified when\nchanging disk source for floppy and cdrom drives since both arguments\nare passed as arguments of the disk rather than the image in qemu.\n\nHistorically these fields have only two possible values since they are\nrepresented as XML thus we need to ignore if user did not provide them\nand thus we are treating them as false.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/3b3debfb7f70696e55642ed34be2848d8ba4b8b7"},{"sha":"662862ec5f20389fcc7c6f898630eb2a9c546b34","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: hotplug: Allow update of disk default snapshot location\n\nSince the field is internal to libvirt we can allow the users to modify\nit.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/662862ec5f20389fcc7c6f898630eb2a9c546b34"},{"sha":"e08479efcac3575fdb11d374fd4aa4f0cde6775d","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: perf: Don't ignore perf setup if allocation fails\n\nReject the VM startup if the perf event structure can't be allocated.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/e08479efcac3575fdb11d374fd4aa4f0cde6775d"},{"sha":"f7e7994b84fd32ca534b457915bb865a780966b3","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"util: perf: Use 'error' label in virPerfCmtEnable\n\nThe label is used only for the error path, thus rename cleanup.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/f7e7994b84fd32ca534b457915bb865a780966b3"},{"sha":"bb9a80f9fcaa443b6c7cb109833cad854f1c256c","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"util: perf: Adhere to coding style of error checks in virPerfEventEnable","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/bb9a80f9fcaa443b6c7cb109833cad854f1c256c"},{"sha":"e64e394223c564008dc46ad02f37a832906192b6","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"util: perf: Adhere to coding style of error checks in qemuDomainSetPerfEvents","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/e64e394223c564008dc46ad02f37a832906192b6"},{"sha":"edadd46c05b1eb93479a88017783bae648709bfa","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: process: Fix failure semantics for perf events\n\nFor strange reasons if a perf event type was not supported or failed to\nbe enabled at VM start libvirt would ignore the failure.\n\nOn the other hand on restart if the event could not be re-enabled\nlibvirt would fail to reconnect to the VM and kill it.\n\nBoth don't make really sense. Fix it by failing to start the VM if the\nevent is not supported and change the event to disabled if it can't be\nreconnected (unlikely).\n\nResolves: https://bugzilla.redhat.com/show_bug.cgi?id=1329045","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/edadd46c05b1eb93479a88017783bae648709bfa"},{"sha":"22e464744d895539fceb35506e6065bb11c8f623","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: process: Don't needlesly clear the perf events in qemuDomainPerfRestart\n\nAt that point the perf events struct should not be allocated so there's\nno use in clearing it.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/22e464744d895539fceb35506e6065bb11c8f623"},{"sha":"3fbc7b781c61506780f9902f964439b962cfb1a6","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: remove default case from few typecasted enums\n\nCommit 98c5c53d69b partially reverted the effort to use typecasted enums\nfor compiler notification. Turn it back.","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/3fbc7b781c61506780f9902f964439b962cfb1a6"},{"sha":"1cc2889f71bed7dd6f7d2064ebf3085c654565a7","author":{"email":"2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com","name":"Peter Krempa"},"message":"qemu: hotplug: Assume QEMU_CAPS_DEVICE in qemuDomainAttachUSBMassStorageDevice","distinct":false,"url":"https://api.github.com/repos/zippy2/libvirt/commits/1cc2889f71bed7dd6f7d2064ebf3085c654565a7"}]}