xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: xen-unstable: Qemu upstream domUs not start on Wheezy
Date: Thu, 8 Mar 2012 01:24:44 -0800 (PST)	[thread overview]
Message-ID: <1331198684615-5546869.post@n5.nabble.com> (raw)
In-Reply-To: <1331042409.22559.85.camel@cthulhu.hellion.org.uk>


Ian Campbell-10 wrote
> 
> /var/run is a tmpfs these days, I think and its been reasonably common
> for distros to clear it out on boot more or less aggressively for some
> time.
> 
> I think the xencommons initscript should be made to mkdir /var/run/xen
> on every boot, or everything in Xen which needs it needs to be made to
> mkdir it as necessary (which would be a pain).
> 
> Can you knock up a patch to add the mkdir to the initscript please?
> 
> Ian.
> 
Patch done and sent:
http://xen.1045712.n5.nabble.com/PATCH-tools-hotplug-Linux-init-d-create-var-run-xen-if-not-exists-td5544288.html

--
View this message in context: http://xen.1045712.n5.nabble.com/xen-unstable-Qemu-upstream-domUs-not-start-on-Wheezy-tp5505409p5546869.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

      reply	other threads:[~2012-03-08  9:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 15:28 xen-unstable: Qemu upstream domUs not start on Wheezy Fantu
2012-02-22 17:01 ` Stefano Stabellini
2012-02-23  8:49   ` Fantu
2012-02-23  8:58     ` Ian Campbell
2012-02-23  9:04       ` Fantu
2012-02-23  9:06       ` Fantu
2012-02-24 10:50         ` Fantu
2012-02-24 12:45           ` Stefano Stabellini
2012-03-06 13:51             ` Fantu
2012-03-06 14:00               ` Ian Campbell
2012-03-08  9:24                 ` Fantu [this message]

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=1331198684615-5546869.post@n5.nabble.com \
    --to=fantonifabio@tiscali.it \
    --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).