Date: Tue, 2 Jun 2009 16:08:34 +0800 From: Adrian Chadd <adrian@freebsd.org> To: mister.olli@googlemail.com Cc: freebsd-xen@freebsd.org Subject: Re: Clock TOD issues (mostly) resolved? Message-ID: <d763ac660906020108x5bcc49b3t5f54e7f6c0a08249@mail.gmail.com> In-Reply-To: <1243928943.2351.5.camel@phoenix.blechhirn.net> References: <d763ac660905290645v331d3387x2549eda596b939b8@mail.gmail.com> <1243774686.12279.7.camel@phoenix.blechhirn.net> <d763ac660905310604l6a5e1887ne8f7bd4971784b79@mail.gmail.com> <1243928943.2351.5.camel@phoenix.blechhirn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Just create a PR for the copying issue and email me the PR number. Thanks, Adrian 2009/6/2 Mister Olli <mister.olli@googlemail.com>: > Hi, > >> > - scp'ing the kernel file to the dom0 instance hanged after transferin= g >> > =A0 =A0 =A0 =A0~ 1MB of data and did not finish. This now works perfec= t. I >> > =A0 =A0 =A0 =A0hadn't got the time to test larger network transfers. >> >> Good! > > Sorry on that, I just recognized that it's not fixed right now. Maybe > Most probable I've tested with the wrong kernel, since I have a r kernel > here to transfer my freshly build kernel to the host dom0. > I just tested with r193225 and it didn't work. Transfer always stops > after 2112kb of transfered data, no matter what kind of data I copy: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > template-8_CURRENT# scp /boot/kernel/kernel dante@10.30.1.15:/tmp > Password: > kernel =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 46% 2112KB 268.4KB/s - stalled -^CKilled by signal 2. > template-8_CURRENT# dd if=3D/dev/zero of=3D/tmp/more_data bs=3D1024k coun= t=3D512 > 512+0 records in > 512+0 records out > 536870912 bytes transferred in 27.200000 secs (19737901 bytes/sec) > template-8_CURRENT# scp /tmp/more_data dante@10.30.1.15:/tmp > Password: > more_data =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 0% 2112KB 662.8KB/s - stalled -^CKilled by signal 2. > template-8_CURRENT# > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Transfering smaller files (like SVN checkout) works like a charm within > the domU. > I also tested transfering 512MB of data from dom0 -> domU and it worked > as expected. > > >> >> > - clock jumps fully disappeared for me. I can do a complete 'make >> > =A0 =A0 =A0 =A0buildworld' without any interruptions due to the time j= ump, even >> > =A0 =A0 =A0 =A0when I'm not using ntpd within the domU. >> >> Good! The time will still drift a little until a hypervisor wall clock >> sync occurs (mostly due to a large enough change to the dom0 time); >> I'll investigate that later. I'm curious to know exactly how Linux >> DomU's manage to keep in lock-step with the dom0 time. > > Didn't recognize any heavy time drifts until now. I have less than 0.5 > after ~14 hours uptime. This is great :-) > > > Regards, > --- > Mr. Olli > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660906020108x5bcc49b3t5f54e7f6c0a08249>