? foo ? docs/APIchunk5.html ? docs/APIchunk6.html ? docs/apibuild.pyc ? tests/foo ? tests/sexpr2xmldata/sexpr2xml-fv-localtime.sexpr ? tests/sexpr2xmldata/sexpr2xml-fv-localtime.xml ? tests/sexpr2xmldata/sexpr2xml-fv-utc.sexpr ? tests/sexpr2xmldata/sexpr2xml-fv-utc.xml ? tests/xmconfigdata/test-fullvirt-localtime.cfg ? tests/xmconfigdata/test-fullvirt-localtime.xml ? tests/xmconfigdata/test-fullvirt-utc.cfg ? tests/xmconfigdata/test-fullvirt-utc.xml ? tests/xml2sexprdata/xml2sexpr-fv-localtime.sexpr ? tests/xml2sexprdata/xml2sexpr-fv-localtime.xml ? tests/xml2sexprdata/xml2sexpr-fv-utc.sexpr ? tests/xml2sexprdata/xml2sexpr-fv-utc.xml Index: docs/format.html =================================================================== RCS file: /data/cvs/libvirt/docs/format.html,v retrieving revision 1.24 diff -u -p -r1.24 format.html --- docs/format.html 29 Jun 2007 12:44:58 -0000 1.24 +++ docs/format.html 13 Jul 2007 15:58:49 -0000 @@ -117,6 +117,7 @@ systems:

<domain type='xen' i
      <acpi/>
      <apic/>
   </features>
+  <clock sync="localtime"/>
   <devices>
     <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
     <interface type='bridge'>
@@ -146,6 +147,11 @@ systems:

<domain type='xen' i
       
  • apic - enable IO APIC
  • acpi - enable ACPI bios
  • +
  • the optional <clock> element is used to specify + whether the emulated BIOS clock in the guest is synced to either + localtime or utc. In general Windows will + want localtime while all other operating systems will + want utc. The default is thus utc
  • the <os> block description is very different, first it indicates that the type is 'hvm' for hardware virtualization, then instead of a kernel, boot and command line arguments, it points to an os @@ -194,6 +200,7 @@ XML description is quite similar, here i <os> <type>hvm</type> </os> + <clock sync="localtime"/> <devices> <emulator>/home/user/usr/kvm-devel/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> @@ -206,6 +213,7 @@ XML description is quite similar, here i <graphics type='vnc' port='-1'/> </devices> </domain>
  • The specific points to note if using KVM are:

    +
  • the optional <clock> element is used to specify + whether the emulated BIOS clock in the guest is synced to either + localtime or utc. In general Windows will + want localtime while all other operating systems will + want utc. The default is thus utc
  • the <os> block description is very different, first it indicates that the type is 'hvm' for hardware virtualization, then instead of a kernel, boot and command line arguments, it points to an os @@ -832,6 +838,7 @@ XML description is quite similar, here i <os> <type>hvm</type> </os> + <clock sync="localtime"/> <devices> <emulator>/home/user/usr/kvm-devel/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> @@ -848,6 +855,7 @@ XML description is quite similar, here i

    The specific points to note if using KVM are: