1. 02 5月, 2016 5 次提交
    • P
      qemu: process: Refresh ejectable media tray state on VM start · a34faf33
      Peter Krempa 提交于
      Empty floppy drives start with tray in "open" state and libvirt did not
      refresh it after startup. The code that inserts media into the tray then
      waited until the tray was open before inserting the media and thus
      floppies could not be inserted.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1326660
      a34faf33
    • M
      virStream{Recv,Send}All: Increase client buffer · 809d02ca
      Michal Privoznik 提交于
      These are wrappers over virStreamRecv and virStreamSend so that
      users have to care about nothing but writing data into / reading
      data from a sink (typically a file). Note, that these wrappers
      are used exclusively on client side as the daemon has slightly
      different approach. Anyway, the wrappers allocate this buffer and
      use it for intermediate data storage until the data is passed to
      stream to send, or to the client application. So far, we are
      using 64KB buffer. This is enough, but suboptimal because server
      can send messages up to VIR_NET_MESSAGE_LEGACY_PAYLOAD_MAX bytes
      big (262120B, roughly 256KB). So if we make the buffer this big,
      a single message containing the data is sent instead of four,
      which is current situation. This means lower overhead, because
      each message contains a header which needs to be processed, each
      message is processed roughly same amount of time regardless of
      its size, less bytes need to be sent through the wire, and so on.
      Note that since server will never sent us a stream message bigger
      than VIR_NET_MESSAGE_LEGACY_PAYLOAD_MAX there's no point in
      sizing up the client buffer past this threshold.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      809d02ca
    • M
      virnetclientstream: Process stream messages later · 18944b7a
      Michal Privoznik 提交于
      There are two functions on the client that handle incoming stream
      data.  The first one virNetClientStreamQueuePacket() is a low
      level function that just processes the incoming stream data from
      the socket and stores it into an internal structure. This happens
      in the client event loop therefore the shorter the callbacks are,
      the better. The second function virNetClientStreamRecvPacket()
      then handles copying data from internal structure into a client
      provided buffer.
      Change introduced in this commit makes just that: new queue for
      incoming stream packets is introduced. Then instead of copying
      data into intermediate internal buffer and then copying them into
      user buffer, incoming stream messages are queue into the queue
      and data is copied just once - in the upper layer function
      virNetClientStreamRecvPacket(). In the end, there's just one
      copying of data and therefore shorter event loop callback. This
      should boost the performance which has proven to be the case in
      my testing.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      18944b7a
    • M
      Revert "rpc: Fix slow volume download (virsh vol-download)" · 435ee578
      Michal Privoznik 提交于
      This reverts commit d9c9e138.
      
      Unfortunately, things are going to be handled differently so this
      commit must go.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      435ee578
    • M
      tools: Fix connect command · 0c56d943
      Martin Kletzander 提交于
      The man page says: "(Re)-Connect to the hypervisor. When the shell is
      first started, this is automatically run with the URI parameter
      requested by the "-c" option on the command line."  However, if you run:
      
        virsh -c 'test://default' 'connect; uri'
      
      the output will not be 'test://default'.  That's because the 'connect'
      command does not care about any virsh-only related settings and if it is
      run without parameters, it connects with @uri == NULL.  Not only that
      doesn't comply to what the man page describes, but it also doesn't make
      sense.  It also means you aren't able to reconnect to whatever you are
      connected currently.
      
      So let's fix that in both virsh and virt-admin add a test case for it.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      0c56d943
  2. 01 5月, 2016 2 次提交
  3. 30 4月, 2016 4 次提交
    • Y
      Fix minor typos in messages · 50fc4b4b
      Yuri Chornoivan 提交于
      Signed-off-by: NYuri Chornoivan <yurchor@ukr.net>
      50fc4b4b
    • L
      Revert "qemu domain allow to set ip address, peer address and route" · 9b643ae8
      Laine Stump 提交于
      This reverts commit 6e244c65, which
      added support to qemu for the "peer" attribute in domain interface <ip>
      elements.
      
      It's being removed temporarily for the release of libvirt 1.3.4
      because the feature doesn't work, and there are concerns that it may
      need to be modified in an externally visible manner which could create
      backward compatibility problems.
      
       Conflicts:
         tests/qemuxml2argvmock.c - a mock of virNetDevSetOnline() was added
         which may be assumed by other tests added since the original commit,
         so it isn't being reverted.
      9b643ae8
    • L
      Revert "lxc domain allow to set peer address" · 70aa318b
      Laine Stump 提交于
      This reverts commit afee47d0, which
      added support to lxc for the "peer" attribute in domain interface <ip>
      elements.
      
      It's being removed temporarily for the release of libvirt 1.3.4
      because the feature doesn't work, and there are concerns that it may
      need to be modified in an externally visible manner which could create
      backward compatibility problems.
      70aa318b
    • L
      Revert "libvirt domain xml allow to set peer address" · 1d14b13f
      Laine Stump 提交于
      This reverts commit 690969af, which
      added the domain config parts to support a "peer" attribute in domain
      interface <ip> elements.
      
      It's being removed temporarily for the release of libvirt 1.3.4
      because the feature doesn't work, and there are concerns that it may
      need to be modified in an externally visible manner which could create
      backward compatibility problems.
      1d14b13f
  4. 29 4月, 2016 3 次提交
    • B
      rpc: Don't leak fd via CreateXMLWithFiles · 5ba48584
      Ben Gray 提交于
      FD passing APIs like CreateXMLWithFiles or OpenGraphicsFD will leak
      file descriptors. The user passes in an fd, which is dup()'d in
      virNetClientProgramCall. The new fd is what is transfered to the
      server virNetClientIOWriteMessage.
      
      Once all the fds have been written though, the parent msg->fds list
      is immediately free'd, so the individual fds are never closed.
      
      This closes each FD as its send to the server, so all fds have been
      closed by the time msg->fds is free'd.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1159766
      5ba48584
    • M
      vz: fix disk enumeration · cdbbb93a
      Mikhail Feoktistov 提交于
      If we want to delete all disks for container or vm
      we should make a loop from 0 to NumberOfDisks and always
      use zero index in PrlVmCfg_GetHardDisk to get disk handle.
      When we delete first disk after that numbers of other disks
      will be changed, start from 0 to NumberOfDisks-1.
      That's why we should always use zero index.
      cdbbb93a
    • N
      virsh: Fix support for 64 migration options · 4d28d093
      Nikolay Shirokovskiy 提交于
      Add ULL suffix to all related operands of << or shift will give
      all zeros instead of correct mask.
      Signed-off-by: NNikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>
      4d28d093
  5. 28 4月, 2016 3 次提交
  6. 27 4月, 2016 3 次提交
  7. 26 4月, 2016 20 次提交