Re: Testing for upcoming FreeBSD 11.1 release
Hello Roger, tested 11.0-STABLE-amd64-20170510-r318134 on XenServer 6.5 SP1 with all patches, xe-guest-utilities installed using pkg. I did about 15 live migrations between our 3 hosts and I didn't see freezes and time issues. Regards, Christian -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Roger Pau Monné Sent: Friday, June 02, 2017 9:00 PM To: freebsd-xen@freebsd.org Subject: Testing for upcoming FreeBSD 11.1 release Hello, The stable/11 branch has entered code freeze as of today [0], in preparation for the 11.1 release. Sadly the 11.0 release contained some FreeBSD/Xen issues (ie: the migration bug related to the Xen timer), that where discovered after the release. In order to try to avoid this happening again in 11.1, can everyone please test that what's in the stable/11 branch or the upcoming BETA builds works in their environment/use case? Thanks, Roger. [0] https://www.freebsd.org/releases/11.1R/schedule.html ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: 11-RELEASE and live migration
> I'm able to see these glitches, as said the VM doesn't really hang, it just > gets > stuck for a long time (and I think that depends on the uptime differences > between the source and destination hosts). In the meantime, could you please > test if changing the timecounter from XENTIMER to any other (like HPET or > ACPI-fast) solves the issue? > > # sysctl -w kern.timecounter.hardware=ACPI-fast Hello Roger, I changed the timecounter from XENTIMER to ACPI-fast and then I did about 10 migrations between our 3 hosts. I always started the next migration a few seconds after the previous migration finished. The VM didn't stuck now and I didn't see the VGABios screen on the console. Regards, Christian ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: 11-RELEASE and live migration
Hello,
I cannot select the source host as destination when I migrate from XenCenter.
All 3 hosts use the same hardware. Disk backend for all VMs is iSCSI.
Regards,
Christian
> -Ursprüngliche Nachricht-
> Von: Roger Pau Monné [mailto:roger@citrix.com]
> Gesendet: Montag, 12. Dezember 2016 11:32
> An: Hoyer-Reuther, Christian; h...@dhcp-3-221.uk.xensource.com
> Cc: freebsd-xen@freebsd.org; owner-freebsd-...@freebsd.org
> Betreff: Re: 11-RELEASE and live migration
>
> On Thu, Dec 08, 2016 at 10:33:37AM +0100, Hoyer-Reuther, Christian wrote:
> > I did some tests and I see the problem too.
> >
> > XenServer 6.5 SP1 with almost all patches (3 hosts in pool), FreeBSD 11.0-
> RELEASE-p2, xe-guest-utilities-6.2.0_2 installed via pkg.
> >
> > First migration from host 3 to host 1 is ok.
> >
> > Some seconds later I start a new migration from host 1 to host 2 and when
> migration finishes (as seen in XenCenter) then the VM switches to the
> VGABios screen ("Plex86/Bochs VGABios (PCI) current-cvs 01 Sep 2016 ...
> cirrus-compatible VGA is detected"). The VM seem to hang and does not
> respond. In XenCenter I see that all the CPU's of the VM go up to 100
> percent.
> >
> > Then after 17 minutes the VGABios screen disappears and I see the console,
> the CPU usage as seen in XenCenter goes down. I logged in as root before I
> started the first migration and root is still logged in. So it was a hang
> and not a reboot.
> >
> > 20 minutes later I start a new migration from host 2 to host 3 and the
> problem occurs again.
> >
> > This problem does not exist with 10.3-RELEASE on the same hosts.
>
> Hello,
>
> So far I've only tested local migration (migration using the same host as
> source
> and destination), and that seems to work fine (I've done +50
> consecutive migrations with only 10s separation between them). Is there a
> change
> that you could also try to reproduce this with local migration?
>
> Are you using the same exact hardware on the source and the destination? Are
> you
> all using iSCSI as the disk backend for this VMs?
>
> Thanks, Roger.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?
Hello, with 11.0-RC1 I see the same problem. I wonder if I am the only one with this problem. Are you able to reproduce it? Regards, Christian > -Original Message- > From: Hoyer-Reuther, Christian > Sent: Friday, August 12, 2016 10:28 AM > To: 'Roger Pau Monné' > Cc: Wei Liu; freebsd-xen@freebsd.org > Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? > > Hm, could you give a try to 11.0-RC1 when it comes out? It should be out > > today or tomorrow (builds are already underway). > > > > Roger. > > No, I'm not booting with boot_verbose="YES". > > I will give 11.0-RC1 a try when it is available. > > Regards, > > Christian ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?
Hello, > -Original Message- > From: Roger Pau Monné [mailto:roger@citrix.com] > Sent: Friday, August 12, 2016 10:01 AM > To: Hoyer-Reuther, Christian > Cc: Wei Liu; freebsd-xen@freebsd.org > Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? > > On Thu, Aug 11, 2016 at 02:29:10PM +0200, Hoyer-Reuther, Christian wrote: > > Hello, > > > > sorry for the late response, but now I'm back from vacation and did some > new tests. > > > > I installed a new VM using the FreeBSD-11.0-ALPHA6-amd64-20160701-r302303- > disc1.iso, then updated to HEAD r303908 and installed xe-guest-utilities- > 6.2.0_2 from HEAD ports r420055. Xenguest_enable="YES" is set in > /etc/rc.conf. > > > > I tested VM migration from XenCenter (XenMotion). > > > > There are no more time issues after migration. > > > > I did 4 migrations and at 2 migrations I noticed the following problems: > > > > When the migration finishes then the VM console switches to the VGA BIOS > screen (Plex86/Bochs VGABios ...), the VM console freezes, the VM is not > reachable over network and in XenCenter I see the first 2 CPU's raising up > to 100 percent. Screenshots attached. > > Hm, not sure what's going on there, and why you seem to be the only one to > hit this issue. Are you maybe booting with boot_verbose="YES"? > > > Then after 10 minutes the CPU usage goes down, the VM console is > responsive again and the machine is reachable over network. > > Hm, could you give a try to 11.0-RC1 when it comes out? It should be out > today or tomorrow (builds are already underway). > > Roger. No, I'm not booting with boot_verbose="YES". I will give 11.0-RC1 a try when it is available. Regards, Christian ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
RE: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?
Hello, thanks for the update. And yes, please let me know when the new issues are fixed. I will test it then and report back the results. Regards, Christian > -Original Message- > From: Roger Pau Monné [mailto:roger@citrix.com] > Sent: Thursday, July 14, 2016 12:30 PM > To: Hoyer-Reuther, Christian > Cc: freebsd-xen@freebsd.org > Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? > > On Tue, Jul 12, 2016 at 02:04:12PM +0200, Hoyer-Reuther, Christian wrote: > > > > We run a XenServer 6.5 SP1 pool with all patches up to XS65ESP1033 on > Fujitsu Primergy RX300 S6 servers. My test VM is FreeBSD 10.3 with xe-guest- > utilities-6.2.0_2 and xen-guest-tools-4.6.1 installed. > > > > After live migration the VM's clock is also several seconds in future. > > Hello, > > I've done some fixes in HEAD some time ago, that are also present in 11. > Those have been tested by Karl, and seem to solve the situation (or at least > the skew is much smaller with those). Sadly migration in both 11 and HEAD > is currently broken due to other issues, so you cannot test it at the > moment. Once that's solved I will ping you so that you can test it. > > Roger. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?
Hello list, I know this is old but I discovered the same problem and found this thread but no newer information. --On Mon Nov 9 10:23:04 UTC 2015 Karl Pielorz wrote: > I've tested this on two pools now. The original production pool (Xeon > E3-1220 v3 @ 3.10GHz) has the issue. > > Our office / test pool (Xeon L5630 @ 2.13Ghz) also -has the issue-. Both > are setup pretty much identical (same storage solution, both running > FreeBSD 10.1/10.2-R with 'xe-guest-utilities' installed). Running or not > running NTP doesn't make a difference. > > Live migrates result in the domU gaining several seconds (thus breaking NTP > if it is running) else leaving the host 'running in the future' vs. both > external clocks, and NTP sync'd clocks on the xenserver. > > As it's easily reproducible I guess I'll file it as a bug... We run a XenServer 6.5 SP1 pool with all patches up to XS65ESP1033 on Fujitsu Primergy RX300 S6 servers. My test VM is FreeBSD 10.3 with xe-guest-utilities-6.2.0_2 and xen-guest-tools-4.6.1 installed. After live migration the VM's clock is also several seconds in future. I use "tinker panic 0" in /etc/ntp.conf as workaround. Then some minutes after the migration the time is in sync again. Here is some output from a peerstats log: ... VM running on "old" host 57581 41601.319 172.30.99.31 965a 0.000911290 0.000156970 0.437525532 0.79273 57581 41603.285 172.30.99.31 965a 0.000931010 0.000158095 0.187527895 0.87612 ... VM migrated to "new" host 57581 41675.500 172.30.99.31 965a -6.986332827 0.000539032 0.062950133 6.987199663 57581 41744.489 172.30.99.31 905a -6.98823 0.000480657 0.000739123 6.467141976 57581 41811.509 172.30.99.31 905a -6.982751485 0.000298934 0.000864689 5.902246019 57581 41879.519 172.30.99.31 905a -6.980983259 0.000466260 0.000933010 5.277805891 57581 41945.518 172.30.99.31 905a -6.979267346 0.000409787 0.000950354 4.569599170 57581 42014.502 172.30.99.31 905a -6.977464766 0.000497814 0.000979475 3.730107446 57581 42080.531 172.30.99.31 905a -6.975764545 0.000413500 0.000969749 2.636950596 57581 42148.485 172.30.99.31 905a -6.973984885 0.000336825 0.000977892 0.007845778 57581 42211.541 172.30.99.31 9024 0.036648577 0.000355228 7.937500599 0.00238 57581 42213.518 172.30.99.31 963a 0.037403812 0.000173852 3.937508397 0.000755235 ... VM still running on the "new" host, now synced Regards, Christian ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
