[SOLVED] 'bug no 502849 on Debian amd64 is solved but how do I use it I faced
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
'bug no 502849 on Debian amd64 is solved but how do I use it I faced
Today morning I found my xen crashed I was using Debian lenny amd64 bit
2.6.26-2-xen-amd64 and xen-3.2.1
Xen had crashed
even though I try to restart it gave error
[code]
server:~# xm list
Error: Unable to connect to xend: No such file or directory. Is xend running?
server:~# /etc/init.d/xend start
Starting XEN control daemon: xendFATAL: Could not create tdb file
/var/lib/xenstored/tdb: Input/output error
failed!
[/server]
This link http://lists.xensource.com/archives/.../msg00969.html
says it is usual
but I am unable to understand what to do I am using Debian Lenny and xen-3.2
I digged a bit more looked at /var/log/messages and found
an error [ 0.377064] map irq failed
it was repeated at many places in the file.After reboot xen fails to start.
linux-image-2.6.26-1-xen-amd64: unable to handle kernel paging request
and this problem is only in amd64 kernels.
reading the mailing list archives it appears using sid is the only
solution they mentioned.I am not clear with now.
If what I have found which I most probably seem to be correct but is
there any thing else I need to check before I reach this conclusion?
How can I solve this problem I am using lenny.
> Also, even though /lib/tls was renamed to /lib/tls.disabled, we still
> see the tls performance warning message during boot.
This is normal for certain builds of Linux - it's because "nash" (or
some other component used by the "initrd") are using statically linked
libraries that use TLS.
... why do you believe that discussion has anything to do with your problem?
Thu, 11 Dec 2008 the dev confirms that there was a bug in the x64 lenny kernel which prevented it running in the hypervisor - and the fix was "pending". That was years ago - the fix is out.
So... again: what makes you think this bug report has anything to do with your problem?
Hi thanks for your reply.I read the link you gave me and it helped me to learn more.I am always welcome to read such nice links.I will appreciate if you can share some more.
Now coming to my problem actually xend daemon is not starting so I have googled those messages.I still do not have any clue as what had happened.
I copy pasted the error messages from log and came across that.My hard disk showed 0 free space so I reached at that conclusion.I saw that /var/xen/lib/save consumed all the space with respective DomU's
yes the disk was full at the time I gave this message.
Code:
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomain.py", line 1134, in domain_restore_fd
return XendCheckpoint.restore(self, fd, paused=paused)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 239, in restore
forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 361, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen-3.2-1/bin/xc_restore 4 4 1 2 0 0 0 failed
This is exact error I got.I checked above Python scripts but could not diagnose.
The error message tells you the problem - xend could not start because it could not create the xenstore.... ergo: there was not enough space to create the xenstore.
Solution: free up some space.
I did freed it up and 2.3 GB is free but it this message is still there.
I was running VMs on a Xen machine until yesterday.Some how the system did not had any memory and all free space was missing.So I free 6 GB.I have 420 GB separate for VMs.
6GB is free on Dom0.
When ever I am trying to start xend after I boot in
deleted all xml files in directories /var/lib/xend
as above link says xend was able to start.
So it seems that XML files in directories in /var/lib/xend were creating problem.
I have the backup of the above xml files in some temporary location.
I was able to see xend running xm info is giving output.
But voilla I ran into another problem
Code:
server:~# xm create /etc/xen/domu1.cfg
Using config file "/etc/xen/domu1.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I finally have solved the problem I put back the xml files which I had removed from /var/lib/xend directories rebooted and voilla every thing seems to work perfectly fine.
I am very very surprised.I do not have any logica answer to this some one who is reading this thread and has understood please reply.
Your initial problem seems to have been solved by recreating the VM. This action was next on my list, but I wanted to have the answer to some questions before doing it.
This created another problem because you had previously erased the hotplug scripts, amongst other things, - restoring the deleted files solved that.
Removing them earlier forced a reconfiguration which solved the previous problem but created the one this thread is about when you restarted. Basically, you have reconfigured a big chunk of xen.
As with the fixed bug you thought was important (see thread title) it is very important to read through descriptions when you are looking for solutions. It's hard, but it gets easier with practise and avoids the confusion you have been experiencing.
Your initial problem seems to have been solved by recreating the VM.
I did not recreated any VM.
Quote:
Originally Posted by Simon Bridge
This action was next on my list, but I wanted to have the answer to some questions before doing it.
Please do ask it may help some one else and I also want to go to root cause of the problem.
Quote:
Originally Posted by Simon Bridge
This created another problem because you had previously erased the hotplug scripts, amongst other things, - restoring the deleted files solved that.
But even before I got all Doms back I was able to start xend which is where the problem had started.
Quote:
Originally Posted by Simon Bridge
Removing them earlier forced a reconfiguration which solved the previous problem but created the one this thread is about when you restarted.
Basically, you have reconfigured a big chunk of xen.
I got some portion of this not the last line.
Quote:
Originally Posted by Simon Bridge
As with the fixed bug you thought was important (see thread title) it is very important to read through descriptions when you are looking for solutions. It's hard, but it gets easier with practise and avoids the confusion you have been experiencing.
After posting above message I have now checked the folder again /var/lib/xend/state
two files cpu.xml and host.xml are newly created I am seeing.
In the above process I have described when I moved xml files from /var/lib/xend/state to other place and restarted xend both the files cpu.xml and host.xml are created again and I could compare the old files and see that old files were corrupted and they were cause of this entire error.
But why does xend need them and how at the time I was doing /etc/init.d/xend start they were being created or needed ?Where can I read that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
