** Changed in: nova Status: Fix Committed => Fix Released ** Changed in: nova Milestone: None => havana-rc1
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1231254 Title: Windows instances need timezone to be localtime Status in OpenStack Compute (Nova): Fix Released Status in OpenStack Compute (nova) folsom series: In Progress Status in OpenStack Compute (nova) grizzly series: In Progress Bug description: (This bug report is forked off from 1026621). I'm sorry to hear you're having pain with Windows instances. Unfortunately I don't know a lot about windows, but it sounds as though if we could change the bios timezone for Windows instances to the timezone of the compute node that would alleviate your issue. Is that correct? Looking at the code, each instance has an os_type field, which is inherited from the image the instance is based off (there is an image property called os_type). Xen expects this value to be "windows" for windows instances. So, libvirt could do the same thing here and treat the timezone for instances with os_type == "windows" differently. I'm going to create a new bug to track this windows issue, so that I can leave this bug focussed on the DHCP timeout issue. This isn't because Windows is less important as a guest, but because I don't want it to be missed in the DHCP discussion that's happening here. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1231254/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp