This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] vif naming? also halting a VM

To: Derek Glidden <dglidden@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] vif naming? also halting a VM
From: Mike Wray <mike.wray@xxxxxxxxxx>
Date: Tue, 20 Jul 2004 16:40:41 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Jul 2004 16:44:29 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <0E59F0DF-D9B7-11D8-9EE6-000A95DBAEDE@xxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <07BD30EC-D912-11D8-86C4-000A95DBAEDE@xxxxxxxxxxxxxxx> <40FBCE80.8090607@xxxxxxxxxx> <0E59F0DF-D9B7-11D8-9EE6-000A95DBAEDE@xxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Derek Glidden wrote:

On Jul 19, 2004, at 9:37 AM, Mike Wray wrote:

Not at the moment, for the reasons above. Bear in mind though that the
domain name is passed to the vif control script - so if the domain name
includes the vmid you can recover it.

Ok, just checking. I want to try to write a script that brings up aliases and sets up iptables rules for NAT and such, and I wondered what the options for managing vif names were. Your rationale all makes perfect sense, so I won't argue. :)

Second, when I run "halt" in a VM, "xm list" shows the VM still hanging around:
# xm list
0    Domain-0              54    0  r----   2073.2
7    This is VM 1           0    1  ---s-     29.0
"xm shutdown" or "destroy" don't seem to have any effect. Is this normal?

This sort of problem seemed to have been cured a while ago.
What version of the code are you using?

That particular example was from code checked out sunday afternoon.

xend debug output shows "shutdown" and "destroy domain 7" or somesuch messages after the halt, yet "xm list" shows it still in state "s" afterward.

OK, I'll need some more info. Can you send the output from xend, and
also the output from 'xm list -l'?
Does this always happen or only with some domain configs?


This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>