Michael,
Thank you for taking a look at this and creating the new bug for
changing the way libvirt virtualizes the hardware clock for Windows vs.
Linux. I believe this to be the root cause for the bug defined here
because of the way Windows handles DHCP renewals.
===DHCP===
As for DHCP, I am
===DHCP===
While I do agree that It would make sense to ping an IP before its lease
is deleted as a extra safety measure. This would not have help this
specific Windows issue as the IP is released by the instance.
--
You received this bug notification because you are a member of Ubuntu
Server
Michael,
Thank you for taking a look at this and creating the new bug for
changing the way libvirt virtualizes the hardware clock for Windows vs.
Linux. I believe this to be the root cause for the bug defined here
because of the way Windows handles DHCP renewals.
===DHCP===
As for DHCP, I am
===DHCP===
While I do agree that It would make sense to ping an IP before its lease
is deleted as a extra safety measure. This would not have help this
specific Windows issue as the IP is released by the instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hey Jay,
Funny you posted this. I was about to post the same. after a bunch of
testing and comparing how CLoudStack deals with the Hardware Clock for
Windows with how Openstack is configured by default we also noticed that
the Nova VM template uses a hardware clock with a UTC offset. This is a
Hey Jay,
Funny you posted this. I was about to post the same. after a bunch of
testing and comparing how CLoudStack deals with the Hardware Clock for
Windows with how Openstack is configured by default we also noticed that
the Nova VM template uses a hardware clock with a UTC offset. This is a
