Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-10-02 Thread Markus Hochholdinger
Hello, Am 25.09.2011 um 20:23 Uhr schrieb Ian Campbell i...@hellion.org.uk: On Sun, 2011-09-25 at 15:09 +0200, Markus Hochholdinger wrote: I can confirm that there are problems with the clock in PV domUs. [..] I'm wondering if I can set the former behavior of the domU clock to use the

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-09-25 Thread Markus Hochholdinger
Hello, I can confirm that there are problems with the clock in PV domUs. I've setups like as follows: * Debian lenny dom0s running Debian squeeze and Debian lenny domUs (PV) * Debian squeeze doms running Debian squeeze and Debian lenny domUs (PV) I only have clock/time problems with my squeeze

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-09-25 Thread Ian Campbell
On Sun, 2011-09-25 at 15:09 +0200, Markus Hochholdinger wrote: Hello, I can confirm that there are problems with the clock in PV domUs. I've setups like as follows: * Debian lenny dom0s running Debian squeeze and Debian lenny domUs (PV) * Debian squeeze doms running Debian squeeze and

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-02-18 Thread Olivier Hanesse
Hello, I am got this issue on several (10+) Xen 4.0 servers without HVM: linux-image-2.6.32-bpo.5-xen-amd64 2.6.32-29~bpo50+1 Linux 2.6.32 for 64-bit PCs, Xen dom0 suppor xen-hypervisor-4.0-amd644.0.1-1The Xen Hypervisor on AMD64 Each

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-01-04 Thread Mark Adams
Hi, No, unfortunately not. I just suffered it again aswell over the Christmas break. Let me know if you find any fix. Regards, Mark On Sun, Dec 26, 2010 at 12:50:26PM +0100, Moritz Muehlenhoff wrote: On Wed, Oct 06, 2010 at 12:05:18PM +0100, Mark Adams wrote: As this is when the clock

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2011-01-04 Thread Mark Adams
In addition, I received the below from James Song but when I queried what it changed he did not respond, so I haven't tried it.. added timer_mode =2 and tsc_mode = 1 and viridian=1 into your configure file. On Tue, Jan

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-12-26 Thread Moritz Muehlenhoff
On Wed, Oct 06, 2010 at 12:05:18PM +0100, Mark Adams wrote: As this is when the clock went from 18:00 to 18:50 and started the chain of events (restarted the 2008 domU). Any ideas why this log occurred? The TSC appeared to go backwards by a fairly significant amount, which has upset

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-10-06 Thread Mark Adams
Hi Ben, Thanks for your response. See my responses inline. On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote: On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-21 Severity: important Hi, Did you receive

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-10-06 Thread Ian Campbell
On Wed, 2010-10-06 at 09:33 +0100, Mark Adams wrote: Hi Ben, Thanks for your response. See my responses inline. On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote: On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version:

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-10-06 Thread Mark Adams
On Wed, Oct 06, 2010 at 11:47:05AM +0100, Ian Campbell wrote: On Wed, 2010-10-06 at 09:33 +0100, Mark Adams wrote: Hi Ben, Thanks for your response. See my responses inline. On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote: On Tue, 2010-10-05 at 09:31 +0100, Mark Adams

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-10-05 Thread Mark Adams
Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-21 Severity: important Hi, Did you receive this bug report? I hadn't received a bug ID even though receiving the copy of the original report. Likely because the address it was sent from originally was invalid. - Hi

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

2010-10-05 Thread Ben Hutchings
On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-21 Severity: important Hi, Did you receive this bug report? I hadn't received a bug ID even though receiving the copy of the original report. We don't have any other bug