[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Problems starting xfrd to migrate a domain


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Miguel Gómez <elmiguelonmakinon@xxxxxxxxx>
  • Date: Fri, 8 Jul 2005 11:31:16 +0200
  • Delivery-date: Fri, 08 Jul 2005 09:30:06 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=pxJbfWJ63QobCJkmPUcVO95Vb6a0eOJGfA38xoc5xFa7GsT6FpXOlBtuX+vWZ/zWCOFZ15XyXG3ZlkWAP59+8v3lc9J9DJXRWIR3DsxvzecKNp8GvpzaaD8/cNF3Eq5H0vquJ15Yc7VJABsjfgSYPbaSaO8Uv5Bbz1Q9zlN3HUU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

More information...

The /var/log/xend.log shows me some things:

#################################

[2005-07-08 10:16:55 xend] INFO (XendRoot:112) EVENT> xend.domain.create ['Domain-9', '9']
[2005-07-08 10:16:55 xend] DEBUG (XendDomain:384) domain_configure> id=9 config=['vm', ['name', 'ttylinux2'], ['memory', '8'
[2005-07-08 10:16:55 xend] INFO (console:94) Created console id=13 domain=9 port=9609
[2005-07-08 10:16:55 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=9 uname=file:/xen/vmttylinux2
[2005-07-08 10:16:55 xend] DEBUG (blkif:63) exception looking up device number for sda1: [Errno 2] No such file or directory
[2005-07-08 10:16:56 xend] DEBUG (blkif:155) Connecting blkif <BlkifBackendInterface 9 0>
[2005-07-08 10:16:56 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=9 vif=0 mac=aa:00:00:68:e8:12
[2005-07-08 10:16:56 xend] INFO (XendRoot:112) EVENT> xend.console.create [13, 9, 9609]
[2005-07-08 10:16:57 xend] INFO (XendRoot:112) EVENT> xend.domain.create ['ttylinux2', '9']
[2005-07-08 10:17:07 xend] DEBUG (XendDomain:244) XendDomain>reap> domain died name=ttylinux2 id=9
[2005-07-08 10:17:07 xend] INFO (XendDomain:564) Destroying domain: name=ttylinux2
[2005-07-08 10:17:07 xend] DEBUG (XendDomainInfo:665) Destroying vifs for domain 9
[2005-07-08 10:17:07 xend] DEBUG (netif:305) Destroying vif domain=9 vif=0
[2005-07-08 10:17:07 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain 9
[2005-07-08 10:17:07 xend] DEBUG (blkif:552) Destroying blkif domain=9
[2005-07-08 10:17:07 xend] DEBUG (blkif:408) Destroying vbd domain=9 idx=0
[2005-07-08 10:17:07 xend] DEBUG (XendDomainInfo:634) Closing console, domain 9
[2005-07-08 10:17:07 xend] DEBUG (XendDomainInfo:622) Closing channel to domain 9
[2005-07-08 10:17:07 xend] INFO (XendRoot:112) EVENT> xend.virq 4
[2005-07-08 10:17:07 xend] DEBUG (blkif:363) Unbinding vbd (type file) from /dev/loop0
[2005-07-08 10:17:07 xend] INFO (XendRoot:112) EVENT> xend.domain.exit ['ttylinux2', '9', 'crash']
[2005-07-08 10:17:07 xend] INFO (XendRoot:112) EVENT> xend.domain.destroy ['ttylinux2', '9']
[2005-07-08 10:17:08 xend] INFO (XendRoot:112) EVENT> xend.domain.died ['ttylinux2', '9']

#############################################

The more interesting lines are these ones:

[2005-07-08 10:16:55 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=9 uname=file:/xen/vmttylinux2
[2005-07-08 10:16:55 xend] DEBUG (blkif:63) exception looking up device number for sda1: [Errno 2] No such file or directory



I am using loop back devices to create my VMs, I have read somewhere that this can cause troubles when it's used with NFS. And thats what I am doing, but in "Live Migration Tutorial" by Michael McCabe, they use it without any problems.

 
There are two machines in my network: XENmaster and XENslave. XENmaster is running nfs-user-server, it exports a directory with (rw, sync, no_root_squash) parameters. That directory has the loop-back-devices in it. This is the VM's config file:

kernel = "/boot/vmlinuz-2.6.11-xenU"
memory = 8
name = "ttylinux2"
nics = 1
ip = "192.168.50.196"
disk = [ 'file:/xen/vmttylinux2,sda1,w' ]
root = "/dev/sda1 rw"
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.