Date: Sun, 05 Apr 2009 07:14:35 +0200 From: Julian Stecklina <js@alien8.de> To: mister.olli@googlemail.com Cc: freebsd-xen@freebsd.org Subject: Re: We'd like to help with Xen Message-ID: <87zlevptqc.fsf@tabernacle.lan> In-Reply-To: <1238875381.2667.27.camel@phoenix.blechhirn.net> (Mister Olli's message of "Sat\, 04 Apr 2009 22\:03\:01 %2B0200") References: <49D6C910.8010409@prgmr.com> <20090404112736.GD31897@deviant.kiev.zoral.com.ua> <87myawbabl.fsf@tabernacle.lan> <1238875381.2667.27.camel@phoenix.blechhirn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mister Olli <mister.olli@googlemail.com> writes: > hi julian, > > On Sa, 2009-04-04 at 19:25 +0200, Julian Stecklina wrote: >> >> [snip] >> >> The time jumping problem may be a good candidate, as it is quite a >> showstopper for me and at least some other people. > > Do you have a para-virtualized domU? Or is it fully virtualized? > I'm asking cause I got my time problem fixed, and it may be good to sort > out if we have/had the same/similar kind of problem that can be fixed > the way it worked for me. I use a paravirtualized domU, because the hardware does not support VT/SVM. Next month I have some more time to investigate this again. Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87zlevptqc.fsf>