From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: xen-devel@lists.xen.org
Subject: Re: HVMs terminating as (null)
Date: Mon, 25 Nov 2013 11:02:44 +0000 [thread overview]
Message-ID: <52932E54.90800@citrix.com> (raw)
In-Reply-To: <52932CD6.20308@crc.id.au>
[-- Attachment #1.1: Type: text/plain, Size: 1874 bytes --]
On 25/11/13 10:56, Steven Haigh wrote:
> On 25/11/13 21:50, Sander Eikelenboom wrote:
>>
>> Monday, November 25, 2013, 11:36:05 AM, you wrote:
>>
>>> On Sat, 2013-11-23 at 17:38 +0100, Sander Eikelenboom wrote:
>>>> Would it be possible to leave the domainname to something else as
"(null)" when such a state occurs,
>>>> the xendomains script f.e. seems to interpret this literally and
bails out without shutting down
>>>> any other domains.
>>
>>> I guess it should be a one liner, so please submit a patch. Not sure
>>> what alternative string should be used, since you would want to avoid
>>> clashing with any potential real domain's name.
>>
>> I didn't immediately spot the place where it was set to "null".
>> Yes that's a problem, though domainnaming has more restrictions (like
using "0" (or any other number that is also a domain-id) as domainname)
in the "just don't do that" category.
>>
>>> From that PoV it might be better to teach xendomains to ignore such
>>> domains.
>>
>> From what i remember i also couldn't use "xl destroy" on such a
domain (though i probably should by using the domain number instead of
the name).
>> Perhaps the toolscripts should just uses the domain-id numbers
instead of names for anything except printk's and echoing to the user ?
>
> Correct - once a domain enters the (null) state, you cannot use 'xl
> destroy' to kill the domain. As in my first post, the domain ID still
> exists, but it cannot be used. Is this a toolset bug?
Not really - it is a current Xen limitation.
Once a domain enters this state, there is literally nothing the
toolstack can do to further kill the domain.
One solution to the problem is for the outstanding granted pages to
transfer ownership to Xen, which allows the rest of the domain can be
cleaned up. However, that would make it far less obvious when problems
like this do occur.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2703 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-25 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 16:14 HVMs terminating as (null) Steven Haigh
2013-11-23 16:18 ` Andrew Cooper
2013-11-23 16:38 ` Sander Eikelenboom
2013-11-25 10:36 ` Ian Campbell
2013-11-25 10:47 ` Steven Haigh
2013-11-25 10:50 ` Sander Eikelenboom
2013-11-25 10:56 ` Steven Haigh
2013-11-25 11:02 ` Ian Campbell
2013-11-25 11:02 ` Andrew Cooper [this message]
2013-11-25 11:08 ` Ian Campbell
2013-11-23 19:27 ` Olaf Hering
2013-11-23 19:38 ` Steven Haigh
2013-11-23 19:56 ` Steven Haigh
2013-11-23 20:03 ` Andrew Cooper
2013-11-23 20:09 ` Steven Haigh
2013-11-23 20:26 ` Andrew Cooper
2013-11-24 17:14 ` Wei Liu
2013-11-25 1:19 ` Steven Haigh
2013-11-25 11:07 ` Wei Liu
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=52932E54.90800@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=netwiz@crc.id.au \
--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.