Dear List, I try to start a guest instance on hardware node-2 and the image is located on hardware node-1. The plan is to do live migration between the two nodes in later steps. For this, I configured a NFS server on node-1 dom0 which provides the image and I mount the filesytem on dom0 node-2. I found out, that booting the instance remotley on node-2 using disk = [''file:/xen/XenGuest1.img,xvda1,w'', ''file:/xen/XenGuest1.swap,xvda2,w''] in the cfg file is not working, because I have to use ''tap:aio:'' instead of ''file:'' I can boot the instance locally on node-1 using the ''file:'' configuration, but not remotely on node-2. If I do, I get the error during the boot process on node-2: ''Device 51714 (vbd) could not be connected losetup /dev/loop failed'' I was not able to find out what is going on there or to fix this (there are enough free loop devices). Accordingly, I changed the cfg file to: disk = [''tap:aio:/xen/XenGuest1.img,xvda1,w'', ''tap:aio:/xen/XenGuest1.swap,xvda2,w''] But now, I cannot boot it locally and also not remotley. The boot process hangs with the Error: XENBUS: Waiting for devices to initialise: 295s... Can anyone please give me advice? Thank you!!! -- Se _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2011-09-13 at 16:42 +0200, Sebastian Biedermann wrote:> Dear List, > > I try to start a guest instance on hardware node-2 and the image is > located on hardware node-1. > The plan is to do live migration between the two nodes in later steps. > For this, I configured a NFS server on node-1 dom0 which provides the > image and I mount the filesytem on dom0 node-2. > > I found out, that booting the instance remotley on node-2 using > > disk = [''file:/xen/XenGuest1.img,xvda1,w'', ''file:/xen/XenGuest1.swap,xvda2,w''] > > in the cfg file is not working, because I have to use ''tap:aio:'' instead > of ''file:'' > > I can boot the instance locally on node-1 using the ''file:'' > configuration, but not remotely on node-2. > If I do, I get the error during the boot process on node-2: ''Device > 51714 (vbd) could not be connected losetup /dev/loop failed'' > I was not able to find out what is going on there or to fix this (there > are enough free loop devices). > > Accordingly, I changed the cfg file to: > > disk = [''tap:aio:/xen/XenGuest1.img,xvda1,w'', ''tap:aio:/xen/XenGuest1.swap,xvda2,w''] > > But now, I cannot boot it locally and also not remotley. The boot > process hangs with the Error: > > XENBUS: Waiting for devices to initialise: 295s... > > Can anyone please give me advice? > Thank you!!! >Try adding the following to /etc/modprobe.conf : options loop max_loop=256 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Try adding the following to /etc/modprobe.conf : > > options loop max_loop=256 > >That will take care of the file:/ issue... you ran out of loopback devices. As for the tap:aio issue I am unsure, but if it works with file:/ you can at least test migration between the two. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2011-09-13 at 16:42 +0200, Sebastian Biedermann wrote:>> Dear List, >> >> I try to start a guest instance on hardware node-2 and the image is >> located on hardware node-1. >> The plan is to do live migration between the two nodes in later steps. >> For this, I configured a NFS server on node-1 dom0 which provides the >> image and I mount the filesytem on dom0 node-2. >> >> I found out, that booting the instance remotley on node-2 using >> >> disk = [''file:/xen/XenGuest1.img,xvda1,w'', ''file:/xen/XenGuest1.swap,xvda2,w''] >> >> in the cfg file is not working, because I have to use ''tap:aio:'' instead >> of ''file:'' >> >> I can boot the instance locally on node-1 using the ''file:'' >> configuration, but not remotely on node-2. >> If I do, I get the error during the boot process on node-2: ''Device >> 51714 (vbd) could not be connected losetup /dev/loop failed'' >> I was not able to find out what is going on there or to fix this (there >> are enough free loop devices). >> >> Accordingly, I changed the cfg file to: >> >> disk = [''tap:aio:/xen/XenGuest1.img,xvda1,w'', ''tap:aio:/xen/XenGuest1.swap,xvda2,w''] >> >> But now, I cannot boot it locally and also not remotley. The boot >> process hangs with the Error: >> >> XENBUS: Waiting for devices to initialise: 295s... >> >> Can anyone please give me advice? >> Thank you!!! >> > Try adding the following to /etc/modprobe.conf : > > options loop max_loop=256 > >Unfortunately, this is not working. I increased the number of loop devices, I get the same error on node-2: toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen toor@node-2:/$ cd /xen toor@node-2:/xen$ ls disk.img my.lenny.cfg swap.img toor@node-2:/xen$ sudo xm create my.lenny.cfg -c Using config file "./my.lenny.cfg". toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. losetup /dev/loop0 /xen/disk.img failed -- Se _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Unfortunately, this is not working. I increased the number of loop > devices, I get the same error on node-2: > > toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen > toor@node-2:/$ cd /xen > toor@node-2:/xen$ ls > disk.img my.lenny.cfg swap.img > toor@node-2:/xen$ sudo xm create my.lenny.cfg -c > Using config file "./my.lenny.cfg". > toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. > losetup /dev/loop0 /xen/disk.img failed > >Did you reboot? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> Unfortunately, this is not working. I increased the number of loop >> devices, I get the same error on node-2: >> >> toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen >> toor@node-2:/$ cd /xen >> toor@node-2:/xen$ ls >> disk.img my.lenny.cfg swap.img >> toor@node-2:/xen$ sudo xm create my.lenny.cfg -c >> Using config file "./my.lenny.cfg". >> toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. >> losetup /dev/loop0 /xen/disk.img failed >> >> > Did you reboot?Yes.. -- Se _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Do have sure that the /dev/loop there is on server ? On Tue, Sep 13, 2011 at 12:37 PM, Sebastian Biedermann < biedermann@seceng.informatik.tu-darmstadt.de> wrote:> Unfortunately, this is not working. I increased the number of loop >>> devices, I get the same error on node-2: >>> >>> toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen >>> toor@node-2:/$ cd /xen >>> toor@node-2:/xen$ ls >>> disk.img my.lenny.cfg swap.img >>> toor@node-2:/xen$ sudo xm create my.lenny.cfg -c >>> Using config file "./my.lenny.cfg". >>> toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. >>> losetup /dev/loop0 /xen/disk.img failed >>> >>> >>> Did you reboot? >> > > Yes.. > > -- > Se > > > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/**xen-users<http://lists.xensource.com/xen-users> >-- *Bruno Steven - Administrador de sistemas* *LPIC-2 / MCSA-Windows 2003 / CompTIA Security+ * _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2011-09-13 at 17:37 +0200, Sebastian Biedermann wrote:> >> Unfortunately, this is not working. I increased the number of loop > >> devices, I get the same error on node-2: > >> > >> toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen > >> toor@node-2:/$ cd /xen > >> toor@node-2:/xen$ ls > >> disk.img my.lenny.cfg swap.img > >> toor@node-2:/xen$ sudo xm create my.lenny.cfg -c > >> Using config file "./my.lenny.cfg". > >> toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. > >> losetup /dev/loop0 /xen/disk.img failed > >> > >> > > Did you reboot? > > Yes..Hmm, the only other suggestion I have for increasing loopbacks is adding the following to your kernel boot line (not xen kernel, but system kernel): max_loop=256 But that isn''t necessary in my setup on CentOS... what distro is your dom0? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2011-09-13 at 17:37 +0200, Sebastian Biedermann wrote:> >> Unfortunately, this is not working. I increased the number of loop > >> devices, I get the same error on node-2: > >> > >> toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen > >> toor@node-2:/$ cd /xen > >> toor@node-2:/xen$ ls > >> disk.img my.lenny.cfg swap.img > >> toor@node-2:/xen$ sudo xm create my.lenny.cfg -c > >> Using config file "./my.lenny.cfg". > >> toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. > >> losetup /dev/loop0 /xen/disk.img failed > >> > >> > > Did you rebootAlso, on node2, do you have read+write permissions on the NFS share? Are you able to create a file in that directory? I just read through your original email and was going down the wrong path. My apologies. Tait _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2011-09-13 at 17:37 +0200, Sebastian Biedermann wrote:>>>> Unfortunately, this is not working. I increased the number of loop >>>> devices, I get the same error on node-2: >>>> >>>> toor@node-2:/xen$ sudo mount 192.168.0.2:/xen /xen >>>> toor@node-2:/$ cd /xen >>>> toor@node-2:/xen$ ls >>>> disk.img my.lenny.cfg swap.img >>>> toor@node-2:/xen$ sudo xm create my.lenny.cfg -c >>>> Using config file "./my.lenny.cfg". >>>> toor@node-2:/xen$ Error: Device 51714 (vbd) could not be connected. >>>> losetup /dev/loop0 /xen/disk.img failed >>>> >>>> >>> Did you reboot > > Also, on node2, do you have read+write permissions on the NFS share? Are > you able to create a file in that directory? > > I just read through your original email and was going down the wrong > path. My apologies. > > TaitNow I can boot the instance on node-2, I didnt had NFS root write privileges which I could get with the ''no_root_squash'' option in the /etc/exports file. Thank you for that hint! But the migration is still not working... it is just timing out.. toor@node-1:/xen$ sudo xm migrate 71 192.168.0.3 -l Error: timed out the xend.log file says: [2011-09-14 10:27:31 1679] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 34 71 0 0 1 [2011-09-14 10:27:31 1679] INFO (XendCheckpoint:423) /usr/lib/xen/bin/xc_save: symbol lookup error: /usr/lib/xen/bin/xc_save: undefined symbol: xs_suspend_evtchn_port [2011-09-14 10:27:31 1679] ERROR (XendCheckpoint:178) Save failed on domain my.lenny (71) - resuming. Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 146, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 409, in forkHelper raise XendError("%s failed: popen failed" % string.join(cmd)) XendError: /usr/lib/xen/bin/xc_save 34 71 0 0 1 failed: popen failed [2011-09-14 10:27:31 1679] DEBUG (XendDomainInfo:3117) XendDomainInfo.resumeDomain(71) [2011-09-14 10:27:34 1679] ERROR (xmlrpclib2:178) Internal error handling xend.domain.migrate Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/xen/util/xmlrpclib2.py", line 131, in _marshaled_dispatch response = self._dispatch(method, params) File "/usr/lib/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch return func(*params) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 1366, in domain_migrate self._domain_migrate(dominfo, dst, live, port, node) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 1458, in _domain_migrate dsterr = sock.recv(1024) timeout: timed out The port 8002 is open on both hosts, connections are possible... the xen config is configured.. I use exactly the same software versions on both hosts.. any ideas? Thank you! -- Se _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Now I can boot the instance on node-2, I didnt had NFS root write > privileges which I could get with > the ''no_root_squash'' option in the /etc/exports file. Thank you for that > hint! > > But the migration is still not working... it is just timing out.. > > toor@node-1:/xen$ sudo xm migrate 71 192.168.0.3 -l > Error: timed out > > the xend.log file says: > > [2011-09-14 10:27:31 1679] DEBUG (XendCheckpoint:124) [xc_save]: > /usr/lib/xen/bin/xc_save 34 71 0 0 1 > [2011-09-14 10:27:31 1679] INFO (XendCheckpoint:423) > /usr/lib/xen/bin/xc_save: symbol lookup error: /usr/lib/xen/bin/xc_save: > undefined symbol: xs_suspend_evtchn_port > [2011-09-14 10:27:31 1679] ERROR (XendCheckpoint:178) Save failed on > domain my.lenny (71) - resuming. > Traceback (most recent call last): > File > "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", > line 146, in save > forkHelper(cmd, fd, saveInputHandler, False) > File > "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", > line 409, in forkHelper > raise XendError("%s failed: popen failed" % string.join(cmd)) > XendError: /usr/lib/xen/bin/xc_save 34 71 0 0 1 failed: popen failed > [2011-09-14 10:27:31 1679] DEBUG (XendDomainInfo:3117) > XendDomainInfo.resumeDomain(71) > [2011-09-14 10:27:34 1679] ERROR (xmlrpclib2:178) Internal error > handling xend.domain.migrate > Traceback (most recent call last): > File "/usr/local/lib/python2.6/dist-packages/xen/util/xmlrpclib2.py", > line 131, in _marshaled_dispatch > response = self._dispatch(method, params) > File "/usr/lib/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch > return func(*params) > File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", > line 1366, in domain_migrate > self._domain_migrate(dominfo, dst, live, port, node) > File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", > line 1458, in _domain_migrate > dsterr = sock.recv(1024) > timeout: timed out > > > The port 8002 is open on both hosts, connections are possible... the xen > config is configured.. > I use exactly the same software versions on both hosts.. > > any ideas? > > Thank you! >I''m assuming you have the ports open in iptables, can you post your xend-config.sxp? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users