WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Zombie VM?

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Zombie VM?
From: Nils Toedtmann <xen-devel@xxxxxxxxxxxxxxxxxx>
Date: Tue, 12 Apr 2005 12:08:23 +0200
Delivery-date: Tue, 12 Apr 2005 10:08:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I did a "xm create freebsd" and got this:

  [root@ripley ~]# xm list
  Name              Id  Mem(MB)  CPU  State  Time(s)  Console
  Domain-0           0       92    0  r----   3018.1        
  Domain-20         20       64    1  --p--      0.0        
  freebsd           20       63    1  r----  31491.5    9620
  [...]

I have no "Domain-20" configured! I'm pretty sure i did not type in "xm
create freebsd" twice, but even if, and even if the freebsd kernel is
very buggy - there should never be two VMs with the same id, right?
Looks like a bug in xend? I booted the freebsd VM several times before,
and i cannot remember this effect, but maybe i just didn't notice it.

The machine is still in this state because you may want me to run some
tests (unpausing Domain-20?). All other VMs run fine (except freebsd
going beserk again, but that's probably not xen's fault).

Here is /var/log/xend.log:

  [2005-04-12 00:35:39 xend] DEBUG (XendDomainInfo:720) init_domain>
Created domain=20 name=freebsd memory=64
  [2005-04-12 00:35:39 xend] INFO (console:94) Created console id=26
domain=20 port=9620
  [2005-04-12 00:35:39 xend] DEBUG (XendDomainInfo:1130) Creating vbd
dom=20 uname=file:/home/xen/images/freebsd-5.3-xendemo-2.0.5.test.slice
  [2005-04-12 00:35:39 xend] DEBUG (blkif:63) exception looking up
device number for hda1: [Errno 2] No such file or directory: '/dev/hda1'
  [2005-04-12 00:35:39 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 20 0>
  [2005-04-12 00:35:39 xend] DEBUG (XendDomainInfo:1130) Creating vbd
dom=20 uname=file:/home/xen/images/freebsd-hda2.fs
  [2005-04-12 00:35:39 xend] DEBUG (blkif:63) exception looking up
device number for hda2: [Errno 2] No such file or directory: '/dev/hda2'
  [2005-04-12 00:35:39 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 20 0>
  [2005-04-12 00:35:39 xend] DEBUG (XendDomainInfo:1107) Creating vif
dom=20 vif=0 mac=FE:FD:00:DE:AD:11
  [2005-04-12 00:35:39 xend] INFO (XendRoot:112) EVENT>
xend.console.create [26, 20, 9620]
  [2005-04-12 00:35:39 xend] INFO (XendRoot:112) EVENT>
xend.domain.create ['Domain-20', '20']
  [2005-04-12 00:35:39 xend] INFO (XendRoot:112) EVENT>
xend.domain.create ['freebsd', '20']
  [2005-04-12 00:35:40 xend] INFO (XendRoot:112) EVENT>
xend.domain.unpause ['freebsd', '20']
  [2005-04-12 00:35:41 xend] DEBUG (blkif:203) Connecting blkif to event
channel <BlkifBackendInterface 20 0> ports=28:4

Where does that "EVENT> xend.domain.create ['Domain-20', '20']" suddenly
come from?

The "exception looking up device number for hda" is not critical, that's
normal with udev on dom0.

/nils.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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