From: xen@bugs.xenproject.org
To: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Processed: Re: [TestDay] Xen crash on boot
Date: Mon, 27 Jan 2014 17:30:02 +0000 [thread overview]
Message-ID: <control-reply-1390843802.11711@bugs.xenproject.org> (raw)
In-Reply-To: <CAFLBxZbF5-am6VhWKBD68hna2FxdrbK12f4CG0sA7gYbOyDfDA@mail.gmail.com>
Processing commands for xen@bugs.xenproject.org:
> create ^
Created new bug #37 rooted at `<1390244796.2322.6.camel@astar.houby.net>'
Title: `Re: [Xen-devel] [TestDay] Xen crash on boot'
> title it Disable IOMMU if no soutbridge
Set title for #37 to `Disable IOMMU if no soutbridge'
> thanks
Finished processing.
Modified/created Bugs:
- 37: http://bugs.xenproject.org/xen/bug/37 (new)
---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues
prev parent reply other threads:[~2014-01-27 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 19:06 [TestDay] Xen crash on boot Eric Houby
2014-01-21 9:31 ` [TestDay] Xen crash on boot in get_rte_index without no-amd-iommu-perdev-intremap Ian Campbell
2014-01-21 15:17 ` Eric Houby
2014-01-22 9:11 ` Jan Beulich
2014-01-21 9:32 ` [TestDay] Xen crash on boot Jan Beulich
2014-01-21 9:45 ` Ian Campbell
2014-01-21 10:39 ` Eric Houby
2014-01-21 21:38 ` Konrad Rzeszutek Wilk
2014-01-22 8:30 ` Jan Beulich
2014-01-23 5:40 ` Eric Houby
2014-01-23 11:16 ` Jan Beulich
2014-01-24 0:47 ` Eric Houby
2014-01-24 1:44 ` Andrew Cooper
2014-01-24 4:50 ` Eric Houby
2014-01-24 9:27 ` Jan Beulich
2014-01-24 8:34 ` Jan Beulich
2014-01-24 13:24 ` Jan Beulich
2014-01-26 1:10 ` Eric Houby
2014-02-06 16:44 ` Eric Houby
2014-02-06 16:51 ` Jan Beulich
2014-01-26 0:46 ` Eric Houby
2014-01-24 9:01 ` Jan Beulich
2014-01-26 0:59 ` Eric Houby
2014-01-27 17:14 ` George Dunlap
2014-01-27 17:30 ` xen [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=control-reply-1390843802.11711@bugs.xenproject.org \
--to=xen@bugs.xenproject.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.