From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
m.a.young@durham.ac.u, olaf@aepfle.de, wei.liu2@citrix.com,
marmarek@invisiblethingslab.com, xen-devel@lists.xensource.com
Subject: Re: Install of Xen 4.8 on Fedora 25 makes the box unbootable.. which is due to /var/run/xen being created, instead of /run/xen
Date: Thu, 16 Feb 2017 08:03:35 +0100 [thread overview]
Message-ID: <3b98543b-a39a-feeb-9abc-a30579b6ac13@suse.com> (raw)
In-Reply-To: <e16f6489-05fd-ac05-e1dc-cb80dec521c4@oracle.com>
On 15/02/17 22:10, Boris Ostrovsky wrote:
> On 02/15/2017 03:51 PM, Konrad Rzeszutek Wilk wrote:
>> Hey,
>>
>> Credit goes to Boris (CC-ed) for figuring out how to fix this.
>>
>> I was doing:
>>
>> ./configure --prefix=/usr --enable-systemd
>> make -j8
>> cd dist;./install.sh;)
>> reboot
>>
>> and to my surprise it would hang on
>> Starting Terminate Plymouth Boot Screen"...
>>
>> with a bunch of 'FAILED'.
>>
>>
>> What I hadn't realized is that Fedora has removed the
>> /var/run and is now using /run. But the dist/install
>> has the /var/run directory (dist/install/var/run/) in it -
>> and that seems to make everything blow up as it erase
>> the original symlink:
>>
>> [konrad@x230 /]$ ls -al /var/run
>> lrwxrwxrwx. 1 root root 6 Oct 5 02:08 /var/run -> ../run
>>
>> with its own directory which has nothing to do with /run - and
>> which only has 'xen' and 'xenstored' in it (albeit at bootup things
>> do seem to be created there - but they are not in sync with things in
>> /run).
>>
>>
>> The "Fix" is to boot with 'init=/bin/bash' on Linux command line and do:
>>
>> mount / -o remount,rw
>> rm -rf /var/run
>> mkdir /run/xen
>> mkdir /run/xenstored
>> ln -sf /run /var/run
>>
>> And then everything works again.
>>
>> A bit of light builds shows that RELEASE-4.7.0
>> does not have an dist/install/var/run but
>> RELEASE-4.8.0 and higher does.
>>
>> And I am not exactly sure which commit does this and
>> how to go around to auto-detect this?
>
> I *think* this started happening after
> https://lists.xenproject.org/archives/html/xen-devel/2016-08/msg00372.html
I thought using:
./configure --prefix=/usr --enable-systemd XEN_RUN_DIR=/run/xen
XEN_RUN_STORED=/run/xenstored
would solve this issue, but obviously those settings don't make it into
config/Paths.mk
I suggest adding something like "--rundir=..." to the possible configure
parameters defaulting to /var/run and set XEN_RUN_DIR to $(rundir)/xen
and XEN_RUN_STORED to $(rundir)/xenstored.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-16 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:51 Install of Xen 4.8 on Fedora 25 makes the box unbootable.. which is due to /var/run/xen being created, instead of /run/xen Konrad Rzeszutek Wilk
2017-02-15 21:10 ` Boris Ostrovsky
2017-02-16 7:03 ` Juergen Gross [this message]
2017-02-16 7:52 ` Olaf Hering
2017-02-16 7:58 ` Juergen Gross
2017-02-16 8:03 ` Olaf Hering
2017-02-16 8:05 ` Olaf Hering
2017-02-16 9:26 ` M A Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b98543b-a39a-feeb-9abc-a30579b6ac13@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.u \
--cc=marmarek@invisiblethingslab.com \
--cc=olaf@aepfle.de \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).