1. 07 6月, 2013 5 次提交
    • R
      Add support for VirtualBox 4.2 APIs · ab7110bf
      ryan woodsmall 提交于
      A few things have changed in the VirtualBox API - some small
      (capitalizations of things in function names like Ip to IP
      and Dhcp to DHCP) and some much larger (FindMedium is superceded
      by OpenMedium). The biggest change for the sake of this patch
      is the signature of CreateMachine is quite a bit different. Using
      the Oracle source as a guide, to spin up a VM with a given UUID,
      it looks like a text flag has to be passed in a new argument to
      CreateMachine. This flag is built in the VirtualBox 4.2 specific
      ifdefs and is kind of ugly but works. Additionally, there is now
      (unused) VM groups support in CreateMachine and the previous
      'osTypeId' arg is currently set to nsnull as in the Oracle code.
      
      The FindMedium to OpenMedium changes were more straightforward
      and are pretty clear. The rest of the vbox template changes are
      basically spelling/capitalization changes from the looks of things.
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      ab7110bf
    • M
      qemuDomainMigrateGraphicsRelocate: Use then new virSocketAddrIsWildcard · b72ba1da
      Michal Privoznik 提交于
      Since we have the new internal API to check for wildcard address,
      we can use it instead of parsing and formatting.
      b72ba1da
    • M
      virsocket: Introduce virSocketAddrIsWildcard · 68899436
      Michal Privoznik 提交于
      This internal API checks, if passed address is a wildcard address.
      68899436
    • J
      iscsi: pass hostnames to iscsiadm instead of resolving them · cbdb3c73
      Ján Tomko 提交于
      iscsiadm now supports specifying hostnames in the portal argument [1]
      
      Instead of resolving the hostname to a single IPv4 address, pass the
      hostname to isciadm, allowing IPv6 targets to work.
      
      [1] https://bugzilla.redhat.com/show_bug.cgi?id=624437
      cbdb3c73
    • O
      qemu: Report the offset from host UTC for RTC_CHANGE event · e31b5cf3
      Osier Yang 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=964177
      
      Though both libvirt and QEMU's document say RTC_CHANGE returns
      the offset from the host UTC, qemu actually returns the offset
      from the specified date instead when specific date is provided
      (-rtc base=$date).
      
      It's not safe for qemu to fix it in code, it worked like that
      for 3 years, changing it now may break other QEMU use cases.
      What qemu tries to do is to fix the document:
      
      http://lists.gnu.org/archive/html/qemu-devel/2013-05/msg04782.html
      
      And in libvirt side, instead of replying on the value from qemu,
      this converts the offset returned from qemu to the offset from
      host UTC, by:
      
        /*
         * a: the offset from qemu RTC_CHANGE event
         * b: The specified date (-rtc base=$date)
         * c: the host date when libvirt gets the RTC_CHANGE event
         * offset: What libvirt will report
         */
      
        offset = a + (b - c);
      
      The specified date (-rtc base=$date) is recorded in clock's def as
      an internal only member (may be useful to exposed outside?).
      
      Internal only XML tag "basetime" is introduced to not lose the
      guest's basetime after libvirt restarting/reloading:
      
      <clock offset='variable' adjustment='304' basis='utc' basetime='1370423588'/>
      e31b5cf3
  2. 06 6月, 2013 9 次提交
  3. 05 6月, 2013 12 次提交
  4. 04 6月, 2013 5 次提交
  5. 03 6月, 2013 9 次提交