fix libguestfs mount order when inspecting

variable `mounts` sorted value is
[
    ('/boot', '/dev/vda1'),
    ('/', '/dev/vda2'),
    ('/var', '/dev/vda5'),
    ('/home', '/dev/vda6'),
    ('/home/q', '/dev/vda7')
]
but `/boot` directory is in `/` partition.

Fixes: Bug #1210371
Change-Id: I3d9cd59237bc4fc277415104c9170d2e372a1c25
Cherry picked: a8613dd59383c150ac8762398838236759bad7b1
Windows instances require the timezone to be "localtime"

This was relatively simple to fix, assuming that the image used
to boot the windows instance has the os_type set to "windows".
The use of os_type in this manner is consistent with the
existing use in the Xen hypervisor driver.

DocImpact: if you're booting windows instances, then you need to
set the os_type image property in glance to "windows". Otherwise
your instances will have their clock timezone set to UTC, which
has unexpected side effects in windows.

Change-Id: Id6759a290ed25c9add97ac61bb7d165b3fb908b2
Closes-Bug: 1231254
(cherry picked from commit 280a336a07006b2c998719f2f9033d43289ec7ef)
fallocate image only when user has write access

Libvirt will change instance's ownership when the instance became power
off which will make nova-compute service unable to hard reboot instance
bacause the nova-compute service has not write access. This commit will
allocate space for image only the first time we create image.

Fixes bug: 1200113
Conflicts: nova/tests/test_imagebackend.py
Change-Id: Id81b09ade5f870665f5ffabab3cde144c6dec210
Cherry-picked: c246fb37e20197be27264a36515725233085df1d
Merge "Windows instances require the timezone to be "localtime"" into stable/grizzly
Exclude probelmatic boto versions

Change-Id: Ia3bd9a0b29975368d5d5faf779af8fc3dd790c38
Closes-Bug: #1237944
Merge "fallocate image only when user has write access" into stable/grizzly
Merge "fix libguestfs mount order when inspecting" into stable/grizzly
Merge remote-tracking branch 'upstream/stable/grizzly' into stable/grizzly