10:22 a.m.
Hi,
I need to import a bunch of VM's (about 50) from kvm to ovirt, will be
using virt-v2v and rest api for bulk import.
However, after import new VM's gets GMT-12 timezone and no way to change
it - and that's bothering me, as fsck inside VMs keeps complaining at
timestamps in future each time vm gets shutdown/startup, selinux
relabelling occurs, etc.
I've read about bug with default timezone
(https://bugzilla.redhat.com/show_bug.cgi?id=873795), but I don't have
time to wait for 3.3.0 to release...
Is there any api calls or any other way to set timezone for VM during
import?
--
Yuriy Demchenko
3:53 p.m.
On 06/07/2013 10:22 AM, Yuriy Demchenko wrote:
Hi,
I need to import a bunch of VM's (about 50) from kvm to ovirt, will be
using virt-v2v and rest api for bulk import.
However, after import new VM's gets GMT-12 timezone and no way to change
it - and that's bothering me, as fsck inside VMs keeps complaining at
timestamps in future each time vm gets shutdown/startup, selinux
relabelling occurs, etc.
I've read about bug with default timezone
(https://bugzilla.redhat.com/show_bug.cgi?id=873795), but I don't have
time to wait for 3.3.0 to release...
Is there any api calls or any other way to set timezone for VM during
import?
you can try to fix the OVF prior to import, or update it via the API
prior to the first launch?
5:05 p.m.
On 06/07/2013 10:22 AM, Yuriy Demchenko wrote:
>
> Hi,
>
> I need to import a bunch of VM's (about 50) from kvm to ovirt, will be
> using virt-v2v and rest api for bulk import.
> However, after import new VM's gets GMT-12 timezone and no way to change
> it - and that's bothering me, as fsck inside VMs keeps complaining at
> timestamps in future each time vm gets shutdown/startup, selinux
> relabelling occurs, etc.
> I've read about bug with default timezone
> (https://bugzilla.redhat.com/show_bug.cgi?id=873795), but I don't have
> time to wait for 3.3.0 to release...
> Is there any api calls or any other way to set timezone for VM during
> import?
Based on what I did for my Winxp vm with same problem
http://lists.ovirt.org/pipermail/users/2013-May/014307.html
perhaps you can set a post import job to connect to the db and change
the utc_diff value in vm_dynamic table to the requested value for your
VMs
HIH,
Gianluca
9:37 a.m.
Ah, yea - I've read your thread. Was confused that you sad engine didn't
honoured your changes in db, so didn't tried it myself in first place.
Now tried that myself - it worked :) Though 'utc_diff' for my VM's were
'null' allready, but changing 'time_zone' in 'vm_static' did the
job.
Thanks for help, my problem solved!
Yuriy Demchenko
On 06/07/2013 06:05 PM, Gianluca Cecchi wrote:
Based on what I did for my Winxp vm with same problem
http://lists.ovirt.org/pipermail/users/2013-May/014307.html
perhaps you can set a post import job to connect to the db and change
the utc_diff value in vm_dynamic table to the requested value for your
VMs
4184
days inactive
4187
days old
3 comments
3 participants
participants (3)
-
Gianluca Cecchi -
Itamar Heim -
Yuriy Demchenko