Re: [Xen-devel] Xen 4.5 Development Update (RC4)
Tuesday, December 23, 2014, 4:10:12 PM, you wrote: On 19/12/2014 18:14, Konrad Rzeszutek Wilk wrote: On Fri, Dec 19, 2014 at 03:19:44PM +, Andrew Cooper wrote: There will be another full nightly test happening tonight (based on c/s 7e88c23 libxl: Tell qemu to use raw format when using a tapdisk), and some stress and scale tests if time allows. Yeey! thank you for getting to this! Results are in from the latest nighties, and looking good. No identifiable differences between Xen 4.4 and 4.5 There are also no identified differences in the scale and performance tests. ~Andrew Hi Andrew, Was this from a debug=y or debug=n build for both versions ? -- Sander ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On 26/12/2014 12:20, Sander Eikelenboom wrote: Tuesday, December 23, 2014, 4:10:12 PM, you wrote: On 19/12/2014 18:14, Konrad Rzeszutek Wilk wrote: On Fri, Dec 19, 2014 at 03:19:44PM +, Andrew Cooper wrote: There will be another full nightly test happening tonight (based on c/s 7e88c23 libxl: Tell qemu to use raw format when using a tapdisk), and some stress and scale tests if time allows. Yeey! thank you for getting to this! Results are in from the latest nighties, and looking good. No identifiable differences between Xen 4.4 and 4.5 There are also no identified differences in the scale and performance tests. ~Andrew Hi Andrew, Was this from a debug=y or debug=n build for both versions ? Both for both sets of tests. XenServer, as of 6.5, contains both a debug and non-debug hypervisor, built from identical source. In trunk, the debug hypervisor is used by default. Tests such as performance tests explicitly switch to the non-debug hypervisor as part of their setup. ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On Tue, Dec 23, 2014 at 03:10:12PM +, Andrew Cooper wrote: On 19/12/2014 18:14, Konrad Rzeszutek Wilk wrote: On Fri, Dec 19, 2014 at 03:19:44PM +, Andrew Cooper wrote: There will be another full nightly test happening tonight (based on c/s 7e88c23 libxl: Tell qemu to use raw format when using a tapdisk), and some stress and scale tests if time allows. Yeey! thank you for getting to this! Results are in from the latest nighties, and looking good. No identifiable differences between Xen 4.4 and 4.5 Yeey! Thank you for testing that. There are also no identified differences in the scale and performance tests. That is good and also .. a bit surprising. We did have features to take advantage of huge boxes. Are these tests mostly the normal set of 'guest workload'? ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On 19/12/2014 18:14, Konrad Rzeszutek Wilk wrote: On Fri, Dec 19, 2014 at 03:19:44PM +, Andrew Cooper wrote: There will be another full nightly test happening tonight (based on c/s 7e88c23 libxl: Tell qemu to use raw format when using a tapdisk), and some stress and scale tests if time allows. Yeey! thank you for getting to this! Results are in from the latest nighties, and looking good. No identifiable differences between Xen 4.4 and 4.5 There are also no identified differences in the scale and performance tests. ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
Hi all,
in preparation for the release we need to update some wiki pages, as well as
in-tree docs
First of all, any new features for which any of you have written new wiki pages
should be marked with [[Category:Xen 4.5]]. Either do this, or reply with URLs
to pages and I will do so
Otherwise, I created boilerplate pages for various pages and tracked the status
on http://wiki.xenproject.org/wiki/Category:Xen_4.5
@Russell: you may want to update the XM to XL pages or create a new one and add
your video
== The following pages need to be reviewed and updated ==
* {{NotDone}} [[Linux PVH]]:
** Add PVH Dom0 information
** Review/correct the '''Things that are broken''' section
** Review/correct the '''Items that have not been tested extensively or at
all'''
* {{NotDone}} [[Xen ARM with Virtualization Extensions]]
** supported platforms need to be updated and
** all platforms that are supported in 4.5 tagged appropriately with
[[Category:Xen 4.5]]
== Lars will fix ==
* {{NotDone}} [[Xen Project 4.5 Acknowledgements]]
** Lars will do this.
* {{NotDone}} [[Xen Project 4.5 Feature List]]
** Lars will copy from the blog announcement when ready (Sarah is currently
making some final changes)
== For Konrad and others ==
* {{NotDone}} [[Xen Project Release Features]] - main 4.5 features need to be
added.
Please reply to the thread and I will add that page.
** The key changes normally are changes to scalability/memory/etc. limits -
maybe Jan(x86) and Ian(ARM) can look let me know of changes
** Also new platforms, changes to experimental features, etc.
** Probably the new scheduler should be added - is there a wiki page?
** Any other major new features that are worth highlighting? I can go through
the press release and the release note
* {{NotDone}} [[Xen Project 4.5 Release Notes]] - needs to be created
** http://wiki.xenproject.org/wiki/Xen_Project_4.4_Release_Notes were pretty
lightweight
** I think we should keep it that way. We should probably mainly focus on known
issues
@Konrad: what's your view?
== Missing pages ==
* {{NotDone}} [[Xen Project 4.5 Man Pages]]
** need to clone [[Xen Project 4.4 Man Pages]] and point to the correct branch
when the 4.5 branch has been created
** if there are new documented features in in-tree docs then add them
** if there are irrelevant features such as XM, remove links to docs (probably
the docs should be removed from the git tree also)
Cheers
Lars
On 16 Dec 2014, at 16:13, konrad.w...@oracle.com wrote:
Xen 4.5-rc4 was out on Monday (Dec 15th). This is the last RC and then
we have the General Release on Jan 7th!
Details for the test-day are at
http://wiki.xen.org/wiki/Xen_4.5_RC4_test_instructions
In terms of bugs, we have:
#11 qxl hypervisor support
#13 Re: [Xen-devel] man page example: xm block-attach
#18 xl improve support for migration over non-sshlike tunnels
#19 xl migrate transport improvements
#22 xl does not support specifying virtual function for passthrough device
#23 Remove arbitrary LIBXL_MAXMEM_CONSTANT from libxl, see what breaks
#24 xl missing support for encrypted VNC
#27 Re: [Xen-devel] xend vs xl with pci=['bdf'] wherein the 'bdf' are not
owned by pciback or pcistub will still launch.
#28 support PCI hole resize in qemu-xen
[ 'mmio_hole' fix it, but the ultimate way is to fix it in QEMU]
#30 libxl should implement non-suspend-cancel based resume path
#36 credit2 only uses one runqueue instead of one runq per socket
#38 Implement VT-d large pages so we can avoid sharing between EPT
#40 linux pvops: fpu corruption due to incorrect assumptions
#42 linux, S3 resume of PVHVM fails - missing call to xen_arch_post_suspend?
#43 30s delay loading xenfb driver on some systems
#44 Security policy ambiguities - XSA-108 process post-mortem
#45 arm: domain 0 disables clocks which are in fact being used
#46 qemu-upstream: limitation on 4 emulated NICs prevents guest from starting
unless PV override is used.
= Timeline =
We wer planning on a 9-month release cycle - but it is more like an
10 month. Based on that, below are the estimated dates:
* Feature Freeze: 24th September 2014
* First RC: 24th October [Friday!]
* RC2: Nov 11th
* RC2 Test-day: Nov 13th
* RC3: Dec 3rd.
* RC3 Test-day: Dec 4th
* RC4: Dec 15th
WE ARE HERE ===
* RC4 Test-day: Dec 17th
Release Date: Jan 7th.
The RCs and release will of course depend on stability and bugs, and
will therefore be fairly unpredictable.
Bug-fixes, if Acked-by by maintainer, can go anytime before the First
RC. Later on we will need to figure out the risk of regression/reward
to eliminate the possiblity of a bug introducing another bug.
= Prognosis =
The states are: none - fair - ok - good - done
none - nothing yet
fair - still working on it, patches are prototypes or RFC
ok - patches posted, acting on review
good - some last minute pieces
done - all done, might have bugs
= Bug Fixes =
Bug fixes
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On 16/12/14 20:49, Konrad Rzeszutek Wilk wrote: On Tue, Dec 16, 2014 at 05:43:08PM +, Andrew Cooper wrote: On 16/12/14 16:13, konrad.w...@oracle.com wrote: Xen 4.5-rc4 was out on Monday (Dec 15th). This is the last RC and then we have the General Release on Jan 7th! Details for the test-day are at http://wiki.xen.org/wiki/Xen_4.5_RC4_test_instructions In terms of bugs, we have: From the XenServer testing. Thank you for doing this testing! * Fail to reliably boot on IBM Flex x222 blades, apparent regression from 4.4 I have declared this a latent BIOS bug, and not a regression from 4.4. Across regular reboots, the exact positions of the ACPI tables, and the e820 layout is unstable. The first consistent difference between 4.4 and 4.5 is that 4.4 reports 1 MBR signature while 4.5 reports 0. This is because the int $0x13, ah=2 call is returning differently. I can get the call to return differently (and correctly for 4.5) by simply making the boot trampoline larger (with my debugging routines but not being called). This sounds very familiar, but I can't place where I saw mention of a similar issue. * VM fail to resume on upgrade from Xen 4.5 This is the issue I am currently looking into. Currently, all the upgrade from older XenServer tests are failing due to VMs crashing on resume. I have not yet identified whether this is a XenServer issue or Ugh. I have got to the bottom of this, and it it turns out to be a legacy - migration v2 conversion bug which only surfaced now because Xen-4.5 is more strict than Xen-4.4. HVM_PARAM_PAE_ENABLED is sent out-of-band in legacy, but passed to xc_domain_restore(), which does a set_param(), unconnected with any contents of the stream. Migration v2 saves and restores it properly, but the legacy - v2 conversion neglected to combine the out-of-band information. No VMs blew up because all versions of Xen at that point were not correctly auditing updates to cr4 against the domain cpuid policy. Xen-4.5 now does, causing #GP faults on cr4 writes for guests which had PAE enabled before migrate. I shall be fixing this in the migration v2 series, and also looking for any other obvious out-of-band information which needs injecting into a converted stream. With this fixed(^W hacked around for now), I have identified and solved all discrepancies XenServer testing has noticed between Xen-4.4 and Xen-4.5 so far. There will be another full nightly test happening tonight (based on c/s 7e88c23 libxl: Tell qemu to use raw format when using a tapdisk), and some stress and scale tests if time allows. ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
On 19.12.14 at 15:52, lars.kurth@gmail.com wrote: ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes Iirc scalability changes on the x86 side were mostly (if not exclusively) in terms of performance improvements (in some cases getting bigger guests out of not booting at all state). Jan ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
Hi Lars, 2014-12-19 9:52 GMT-05:00 Lars Kurth lars.kurth@gmail.com: Hi all, Please reply to the thread and I will add that page. ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes ** Also new platforms, changes to experimental features, etc. ** Probably the new scheduler should be added - is there a wiki page? The new scheduler (rtds) does not have a wiki page right now, but it has an outside page to explain how it is designed and how it works at https://sites.google.com/site/realtimexen/getting-started. I can add a wiki page very quickly today based on the pages on https://sites.google.com/site/realtimexen/ . Is that ok? Thanks, Meng -- --- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
On 19 Dec 2014, at 15:55, Meng Xu xumengpa...@gmail.com wrote: Hi Lars, 2014-12-19 9:52 GMT-05:00 Lars Kurth lars.kurth@gmail.com: Hi all, Please reply to the thread and I will add that page. ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes ** Also new platforms, changes to experimental features, etc. ** Probably the new scheduler should be added - is there a wiki page? The new scheduler (rtds) does not have a wiki page right now, but it has an outside page to explain how it is designed and how it works at https://sites.google.com/site/realtimexen/getting-started. I can add a wiki page very quickly today based on the pages on https://sites.google.com/site/realtimexen/ . Is that ok? That would be perfect. Lars___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
On Fri, 2014-12-19 at 10:55 -0500, Meng Xu wrote: 2014-12-19 9:52 GMT-05:00 Lars Kurth lars.kurth@gmail.com: Hi all, Please reply to the thread and I will add that page. ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes ** Also new platforms, changes to experimental features, etc. ** Probably the new scheduler should be added - is there a wiki page? The new scheduler (rtds) does not have a wiki page right now, but it has an outside page to explain how it is designed and how it works at https://sites.google.com/site/realtimexen/getting-started. I can add a wiki page very quickly today based on the pages on https://sites.google.com/site/realtimexen/ . That would be great! :-) Is that ok? I think it is ok. Just make sure, when you do that, that you properly adapt the information and make them match what actually have been upstreamed (so command option names, limits of the implementation, etc.) Also, you should put in the wiki page a WARN about the fact that the scheduler has been included as an experimental and in-development feature. Share here a link when you're done, so we can go having a look. :-) Thanks and Regards, Dario -- This happens because I choose it to happen! (Raistlin Majere) - Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
Hi Lars and Dario, 2014-12-19 11:15 GMT-05:00 Dario Faggioli dario.faggi...@citrix.com: On Fri, 2014-12-19 at 10:55 -0500, Meng Xu wrote: 2014-12-19 9:52 GMT-05:00 Lars Kurth lars.kurth@gmail.com: Hi all, Please reply to the thread and I will add that page. ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes ** Also new platforms, changes to experimental features, etc. ** Probably the new scheduler should be added - is there a wiki page? The new scheduler (rtds) does not have a wiki page right now, but it has an outside page to explain how it is designed and how it works at https://sites.google.com/site/realtimexen/getting-started. I can add a wiki page very quickly today based on the pages on https://sites.google.com/site/realtimexen/ . That would be great! :-) Is that ok? I think it is ok. Just make sure, when you do that, that you properly adapt the information and make them match what actually have been upstreamed (so command option names, limits of the implementation, etc.) Also, you should put in the wiki page a WARN about the fact that the scheduler has been included as an experimental and in-development feature. Share here a link when you're done, so we can go having a look. :-) I have finished the wiki page. Here is the link: http://wiki.xenproject.org/wiki/User:Pennpanda I followed the Credit scheduler's wiki page to complete the RTDS'. (I'm not sure how to add a title for that page as Credit scheduler does. :-( ) Please let me know if you have any question. Thank you very much! :-) Best, Meng -- --- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
On 19 Dec 2014, at 17:10, Meng Xu xumengpa...@gmail.com wrote: I have finished the wiki page. Here is the link: http://wiki.xenproject.org/wiki/User:Pennpanda I followed the Credit scheduler's wiki page to complete the RTDS'. (I'm not sure how to add a title for that page as Credit scheduler does. :-( ) Please let me know if you have any question. Thank you Meng: I will move the content to a page called RTDS-Based-Scheduler of there are no objections Lars___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
On Fri, Dec 19, 2014 at 03:30:23PM +, Jan Beulich wrote: On 19.12.14 at 15:52, lars.kurth@gmail.com wrote: ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes Iirc scalability changes on the x86 side were mostly (if not exclusively) in terms of performance improvements (in some cases getting bigger guests out of not booting at all state). Hmm, wasn't there improvements to allow more VMs per host aswell.. ? which would be worth mentioning.. xenstored related stuff iirc. -- Pasi Jan ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4) - Documentation Updates
Lars, @Russell: you may want to update the XM to XL pages or create a new one and add your video I've updated the existing Wiki pages. I've also created an unpublished entry in the Video section of the XenProject.org website. Should we publish that now, or wait until release? Russ On Fri, Dec 19, 2014 at 2:55 PM, Pasi Kärkkäinen pa...@iki.fi wrote: On Fri, Dec 19, 2014 at 03:30:23PM +, Jan Beulich wrote: On 19.12.14 at 15:52, lars.kurth@gmail.com wrote: ** The key changes normally are changes to scalability/memory/etc. limits - maybe Jan(x86) and Ian(ARM) can look let me know of changes Iirc scalability changes on the x86 side were mostly (if not exclusively) in terms of performance improvements (in some cases getting bigger guests out of not booting at all state). Hmm, wasn't there improvements to allow more VMs per host aswell.. ? which would be worth mentioning.. xenstored related stuff iirc. -- Pasi Jan ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On Wed, Dec 17, 2014 at 08:55:10AM +0100, Olaf Hering wrote: On Tue, Dec 16, Konrad Rzeszutek Wilk wrote: On Tue, Dec 16, 2014 at 05:34:51PM +0100, Olaf Hering wrote: On Tue, Dec 16, konrad.w...@oracle.com wrote: In terms of bugs, we have: ... systemd SELinux, but its not listed. Whats your plan with the failures you see? Should I continue to be concerned about that, or will all the be postponed to 4.6? I was under the impression you had some patches which would solve a majority of the issues? And after the discussion with Ian Jackson the way to exec was solved? No. What I did was to handle XENSTORED_TRACE which is just a bool to pass -T /log/file to xenstored. I think xenstored can not access the sockets if it was launched with a shell script as it is done now. No idea how to solve that. Maybe /usr/bin/env $XENSTORED could be a workaround for the SELinux socket access issue. But perhaps launching it via env or sh fails either way. And for the other - the SELinux context and how to figure this out - I thought (I will have to double-check it tomorrow) that I mentioned it might make sense to talk to the SELinux maintainers to see if they have any recommendation? For xen-4.5 the easy way would be to remove the context= option and let people who build from source and who want to use SELinux put the required options into /etc/fstab. This would also resolve the issue Anthony is seeing, his mount or kernel does not understand context= at all. No idea how he got into that state in his Arch Linux installation. And also remove the EnvionmentFile and such. Anyhow I've taken for spin these patches: tools/hotplug: add wrapper to start xenstored tools/hotplug: remove EnvironmentFile from xen-qemu-dom0-disk-backend.service tools/hotplug: use XENCONSOLED_TRACE in xenconsoled.service tools/hotplug: use xencommons as EnvironmentFile in xenconsoled.service tools/hotplug: xendomains.service depends on network tools/hotplug: remove XENSTORED_ROOTDIR from xenstored.service tools/hotplug: remove SELinux options from var-lib-xenstored.mount from you https://github.com/olafhering/xen.git staging-for-4.5.0 and they fixed the issues I saw. That is I can boot Fedora Core 21 with the sources being built out (plus said patches above) Olaf ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On Wed, Dec 17, 2014 at 02:41:50PM -0500, Konrad Rzeszutek Wilk wrote: On Wed, Dec 17, 2014 at 08:55:10AM +0100, Olaf Hering wrote: On Tue, Dec 16, Konrad Rzeszutek Wilk wrote: On Tue, Dec 16, 2014 at 05:34:51PM +0100, Olaf Hering wrote: On Tue, Dec 16, konrad.w...@oracle.com wrote: In terms of bugs, we have: ... systemd SELinux, but its not listed. Whats your plan with the failures you see? Should I continue to be concerned about that, or will all the be postponed to 4.6? I was under the impression you had some patches which would solve a majority of the issues? And after the discussion with Ian Jackson the way to exec was solved? No. What I did was to handle XENSTORED_TRACE which is just a bool to pass -T /log/file to xenstored. I think xenstored can not access the sockets if it was launched with a shell script as it is done now. No idea how to solve that. Maybe /usr/bin/env $XENSTORED could be a workaround for the SELinux socket access issue. But perhaps launching it via env or sh fails either way. And for the other - the SELinux context and how to figure this out - I thought (I will have to double-check it tomorrow) that I mentioned it might make sense to talk to the SELinux maintainers to see if they have any recommendation? For xen-4.5 the easy way would be to remove the context= option and let people who build from source and who want to use SELinux put the required options into /etc/fstab. This would also resolve the issue Anthony is seeing, his mount or kernel does not understand context= at all. No idea how he got into that state in his Arch Linux installation. And also remove the EnvionmentFile and such. Anyhow I've taken for spin these patches: tools/hotplug: add wrapper to start xenstored tools/hotplug: remove EnvironmentFile from xen-qemu-dom0-disk-backend.service tools/hotplug: use XENCONSOLED_TRACE in xenconsoled.service tools/hotplug: use xencommons as EnvironmentFile in xenconsoled.service tools/hotplug: xendomains.service depends on network tools/hotplug: remove XENSTORED_ROOTDIR from xenstored.service tools/hotplug: remove SELinux options from var-lib-xenstored.mount from you https://github.com/olafhering/xen.git staging-for-4.5.0 and they fixed the issues I saw. That is I can boot Fedora Core 21 with the sources being built out (plus said patches above) Hm, thought now I see: [root@l konrad]# systemctl status xenstored.service ● xenstored.service - The Xen xenstore Loaded: loaded (/usr/lib/systemd/system/xenstored.service; disabled) Active: failed (Result: timeout) since Wed 2014-12-17 16:39:35 EST; 2min 10s ago Process: 790 ExecStart=/usr/lib/xen/bin/xenstored.sh --no-fork (code=exited, status=0/SUCCESS) Process: 787 ExecStartPre=/bin/mkdir -p /var/run/xen (code=exited, status=0/SUCCESS) Process: 784 ExecStartPre=/bin/rm -f /var/lib/xenstored/tdb* (code=exited, status=0/SUCCESS) Process: 759 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS) Main PID: 790 (code=exited, status=0/SUCCESS) Dec 17 16:38:05 l.oracle.com xenstored.sh[790]: Xen Storage Daemon, version 1.0 Dec 17 16:39:35 l.oracle.com systemd[1]: xenstored.service start operation timed out. Terminating. Dec 17 16:39:35 l.oracle.com systemd[1]: Failed to start The Xen xenstore. Dec 17 16:39:35 l.oracle.com systemd[1]: Unit xenstored.service entered failed state. Dec 17 16:39:35 l.oracle.com systemd[1]: xenstored.service failed. [root@l konrad]# systemctl start xenstored.service [root@l ~]# ps -eff|grep xens root 2018 1993 0 16:41 pts/000:00:00 systemctl start xenstored.service root 2029 1 0 16:41 ?00:00:00 /usr/sbin/oxenstored --no-fork root 2034 1766 0 16:42 hvc0 00:00:00 grep --color=auto xens I think I have something misconfigured here.. Olaf ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On 16/12/14 16:13, konrad.w...@oracle.com wrote: Xen 4.5-rc4 was out on Monday (Dec 15th). This is the last RC and then we have the General Release on Jan 7th! Details for the test-day are at http://wiki.xen.org/wiki/Xen_4.5_RC4_test_instructions In terms of bugs, we have: From the XenServer testing. * Fail to reliably boot on IBM Flex x222 blades, apparent regression from 4.4 I have declared this a latent BIOS bug, and not a regression from 4.4. Across regular reboots, the exact positions of the ACPI tables, and the e820 layout is unstable. The first consistent difference between 4.4 and 4.5 is that 4.4 reports 1 MBR signature while 4.5 reports 0. This is because the int $0x13, ah=2 call is returning differently. I can get the call to return differently (and correctly for 4.5) by simply making the boot trampoline larger (with my debugging routines but not being called). * VM fail to resume on upgrade from Xen 4.5 This is the issue I am currently looking into. Currently, all the upgrade from older XenServer tests are failing due to VMs crashing on resume. I have not yet identified whether this is a XenServer issue or a Xen issue. Lifecycle operations on 4.5 itself are all fine including both suspend/resume and migrate. ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On Tue, Dec 16, 2014 at 05:34:51PM +0100, Olaf Hering wrote: On Tue, Dec 16, konrad.w...@oracle.com wrote: In terms of bugs, we have: ... systemd SELinux, but its not listed. Whats your plan with the failures you see? Should I continue to be concerned about that, or will all the be postponed to 4.6? I was under the impression you had some patches which would solve a majority of the issues? And after the discussion with Ian Jackson the way to exec was solved? And for the other - the SELinux context and how to figure this out - I thought (I will have to double-check it tomorrow) that I mentioned it might make sense to talk to the SELinux maintainers to see if they have any recommendation? Olaf ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Xen 4.5 Development Update (RC4)
On Tue, Dec 16, 2014 at 05:43:08PM +, Andrew Cooper wrote: On 16/12/14 16:13, konrad.w...@oracle.com wrote: Xen 4.5-rc4 was out on Monday (Dec 15th). This is the last RC and then we have the General Release on Jan 7th! Details for the test-day are at http://wiki.xen.org/wiki/Xen_4.5_RC4_test_instructions In terms of bugs, we have: From the XenServer testing. Thank you for doing this testing! * Fail to reliably boot on IBM Flex x222 blades, apparent regression from 4.4 I have declared this a latent BIOS bug, and not a regression from 4.4. Across regular reboots, the exact positions of the ACPI tables, and the e820 layout is unstable. The first consistent difference between 4.4 and 4.5 is that 4.4 reports 1 MBR signature while 4.5 reports 0. This is because the int $0x13, ah=2 call is returning differently. I can get the call to return differently (and correctly for 4.5) by simply making the boot trampoline larger (with my debugging routines but not being called). This sounds very familiar, but I can't place where I saw mention of a similar issue. * VM fail to resume on upgrade from Xen 4.5 This is the issue I am currently looking into. Currently, all the upgrade from older XenServer tests are failing due to VMs crashing on resume. I have not yet identified whether this is a XenServer issue or Ugh. a Xen issue. Lifecycle operations on 4.5 itself are all fine including both suspend/resume and migrate. ~Andrew ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
