From: xen@bugs.xenproject.org
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Subject: Processed: Re: [xl restore and migrating problem - hardware compatibility]
Date: Wed, 28 Dec 2016 15:00:02 +0000 [thread overview]
Message-ID: <control-reply-1482937202.9318@bugs.xenproject.org> (raw)
In-Reply-To: <f61005fa-891a-0ce9-be40-371d4e9fe817@arm.com>
Processing commands for xen@bugs.xenproject.org:
> create ^
Created new bug #56 rooted at `<a182bc22-6954-5adb-8872-56bf531eaadc@citrix.com>'
Title: `Re: [Xen-devel] [xl restore and migrating problem - hardware compatibility]'
> severity it blocker
Change severity for #56 to `blocker'
> affects it 4.6, 4.7, 4.8
Bug #56 affects `4.6, 4.7, 4.8'
Command failed: Unable to find tag affects:4.6, 4.7, 4.8 at /srv/xen-devel-bugs/share/perl/5.14.2/Emesinae/Bug.pm line 127, <GEN1> line 3.
Stop processing here.
Modified/created Bugs:
- 56: http://bugs.xenproject.org/xen/bug/56 (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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-28 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 16:32 [xl restore and migrating problem - hardware compatibility] Ing. Ricardo Brisighelli
2016-12-23 17:00 ` Andrew Cooper
2016-12-23 17:16 ` Andrew Cooper
2016-12-23 22:56 ` Ing. Ricardo Brisighelli
2016-12-23 23:22 ` Andrew Cooper
2016-12-24 13:24 ` Ing. Ricardo Brisighelli
2016-12-26 20:43 ` Doug Goldstein
2016-12-28 14:50 ` Julien Grall
2017-01-04 11:00 ` Wei Liu
2016-12-28 14:58 ` Julien Grall
2016-12-28 15:00 ` 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-1482937202.9318@bugs.xenproject.org \
--to=xen@bugs.xenproject.org \
--cc=julien.grall@arm.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 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).