Wensheng Wang
2005-Nov-06 07:30 UTC
[Xen-devel] could not reboot domU in latest xen-unstable
With lastest unstable, I can no longer reboot domU( either within the
domU itself or using "xm shutdown -R").
xm create and destroy is working fine.
After I reboot a domU and do "xm list" a few times, it seems hang, but
after more than 1 minute the prompt came back but with only domain-0,
domU didn''t get rebooted.
The xend.log show following errors:
----------------------------------------------------------------------
[2005-11-06 02:06:21 xend.XendDomainInfo] ERROR (XendDomainInfo:158)
Domain construction failed
Traceback (most recent call last):
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 152, in
create
vm.initDomain()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1109, in
initDomain
self.createDevices()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1222, in
createDevices
self.createDevice(n, c)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 893, in
createDevice
return self.getDeviceController(deviceClass).createDevice(devconfig)
File "/usr/lib/python/xen/xend/server/DevController.py", line 66, in
createDevice
raise VmError( ("Device %s (%s) could not be connected. "
VmError: Device 2049 (vbd) could not be connected. Hotplug scripts not working
[2005-11-06 02:06:21 xend.XendDomainInfo] DEBUG (XendDomainInfo:1156)
XendDomainInfo.destroy: domid=8
[2005-11-06 02:06:21 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.destroyDomain(8)
[2005-11-06 02:06:22 xend.XendDomainInfo] ERROR (XendDomainInfo:1306)
Failed to restart domain 7.
Traceback (most recent call last):
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1299, in
restart
new_dom = xd.domain_create(config)
File "/usr/lib/python/xen/xend/XendDomain.py", line 215, in
domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 152, in
create
vm.initDomain()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1109, in
initDomain
self.createDevices()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1222, in
createDevices
self.createDevice(n, c)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 893, in
createDevice
return self.getDeviceController(deviceClass).createDevice(devconfig)
File "/usr/lib/python/xen/xend/server/DevController.py", line 66, in
createDevice
raise VmError( ("Device %s (%s) could not be connected. "
VmError: Device 2049 (vbd) could not be connected. Hotplug scripts not working
[2005-11-06 02:06:22 xend] ERROR (xswatch:50) read_watch failed
Traceback (most recent call last):
File "/usr/lib/python/xen/xend/xenstore/xswatch.py", line 48, in
watchMain
watch.fn(*watch.args, **watch.kwargs)
File "/usr/lib/python/xen/xend/XendDomain.py", line 112, in
onReleaseDomain
self.refresh()
File "/usr/lib/python/xen/xend/XendDomain.py", line 176, in refresh
d.update(info)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 849, in
update
self.refreshShutdown(info)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 781, in
refreshShutdown
self.maybeRestart(restart_reason)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 801, in
maybeRestart
{"destroy" : self.destroy,
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1312, in
restart
new_dom.removeVm(''xend/restart_in_progress'')
UnboundLocalError: local variable ''new_dom'' referenced before
assignment
[2005-11-06 02:06:22 xend] ERROR (xswatch:50) read_watch failed
Traceback (most recent call last):
File "/usr/lib/python/xen/xend/xenstore/xswatch.py", line 48, in
watchMain
watch.fn(*watch.args, **watch.kwargs)
File "/usr/lib/python/xen/xend/server/DevController.py", line 267, in
hotplugStatus
status = self.readBackend(devid, HOTPLUG_STATUS_NODE)
File "/usr/lib/python/xen/xend/server/DevController.py", line 201, in
readBackend
return xstransact.Read(backpath, *args)
File "/usr/lib/python/xen/xend/xenstore/xstransact.py", line 225, in
Read
t = cls(path)
File "/usr/lib/python/xen/xend/xenstore/xstransact.py", line 17, in
__init__
self.path = path.rstrip("/")
AttributeError: ''NoneType'' object has no attribute
''rstrip''
----------------------------------------------------------------------------------
Did I do anything wrong or indeed hotplug script is broken?
Thanks
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ewan Mellor
2005-Nov-06 09:22 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
On Sun, Nov 06, 2005 at 01:30:20AM -0600, Wensheng Wang wrote:> With lastest unstable, I can no longer reboot domU( either within the > domU itself or using "xm shutdown -R"). > xm create and destroy is working fine. > > After I reboot a domU and do "xm list" a few times, it seems hang, but > after more than 1 minute the prompt came back but with only domain-0, > domU didn''t get rebooted.The primary problem is that your hotplug scripts seem not to be working. Do you see any evidence that they have stalled or bailed out early? There might be something in your /var/log/debug, /var/log/messages, or /var/log/syslog, or you might see processes hanging around. You are the only person experiencing this that I know of, so you may have to do a little hunting around to figure out what the real problem is. The seconday problem you have is that Xend is behaving badly when this first error occurs, and I shall look into that. Thanks for your bug report, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor
2005-Nov-06 11:02 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
On Sun, Nov 06, 2005 at 09:22:18AM +0000, Ewan Mellor wrote:> On Sun, Nov 06, 2005 at 01:30:20AM -0600, Wensheng Wang wrote: > > The seconday problem you have is that Xend is behaving badly when this first > error occurs, and I shall look into that.I''ve assigned this secondary problem #384. I''ll let you investigate the primary problem a little further before filing it. Cheers, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Wensheng Wang
2005-Nov-07 06:34 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
Hi, Ewan, Thank for for the help. I looked at my /var/log/message The last line when the xend unable to restart domain is: Nov 7 00:08:07 m8 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/2/2049/type failed. I attached part of xend.log file, the timeline in that log file is: 23:57:47 machine booted 00:05:21 xm create fc4 00:06:07 xm shutdown -R fc4 1minute after, I did a "xm list", it hangs, another minute later, the prompt came back showing only domain-0 I also find if I interrupt that "xm list" after domU reboot, then do a "xend restart", the domainU will shown paused. When I unpause it, it will be in "r" state forever, even though in reality it doesn''t exist anymore. My base system is fedora core 4. gcc version is 4.01(20050727). A side note is I copied /usr/lib/python/xen to /usr/lib/python2.4/site-packages/ (the default python package location on my system) to get rid of "unable to read memory/target" warning( I think it just warning, it doesn''t seems to affecting anything). Though I don''t think this has anything to do with the problem I have. I hope I can provide more detail, but I don''t know whereelse to look, If you give me some pointer I can get more information. thanks Wensheng Wang On 11/6/05, Ewan Mellor <ewan@xensource.com> wrote:> On Sun, Nov 06, 2005 at 09:22:18AM +0000, Ewan Mellor wrote: > > > On Sun, Nov 06, 2005 at 01:30:20AM -0600, Wensheng Wang wrote: > > > > The seconday problem you have is that Xend is behaving badly when this first > > error occurs, and I shall look into that. > > I''ve assigned this secondary problem #384. I''ll let you investigate the > primary problem a little further before filing it. > > Cheers, > > Ewan. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Toens Bueker
2005-Nov-07 19:17 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
Ewan Mellor <ewan@xensource.com> wrote:>> With lastest unstable, I can no longer reboot domU( either within the >> domU itself or using "xm shutdown -R"). >> xm create and destroy is working fine. >> >> After I reboot a domU and do "xm list" a few times, it seems hang, but >> after more than 1 minute the prompt came back but with only domain-0, >> domU didn''t get rebooted.[...]> You are the only person experiencing this that I know of, so you may have to > do a little hunting around to figure out what the real problem is.<aol> Me too. </aol> system : Linux host : gretel release : 2.6.12.6-xen0 version : #3 SMP Fri Nov 4 21:17:01 CET 2005 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2665 hw_caps : bfebfbff:00000000:00000000:00000080:00004400 memory : 2047 free_memory : 1763 xen_major : 3 xen_minor : 0 xen_extra : -devel xen_caps : xen_3.0_x86_32 xen_params : virt_start=0xfc000000 xen_changeset : Thu Nov 3 09:58:45 2005 +0100 7611:289b73a5ace7 cc_compiler : gcc-Version 3.3.5 (Debian 1:3.3.5-13) cc_compile_by : toens cc_compile_domain : domain.de cc_compile_date : Do Nov 3 18:49:02 CET 2005 Package: hotplug Status: install ok installed Priority: standard Section: admin Installed-Size: 380 Maintainer: Fumitoshi UKAI <ukai@debian.or.jp> Architecture: all Version: 0.0.20040329-25 by Töns -- There is no safe distance. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor
2005-Nov-08 11:39 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
On Mon, Nov 07, 2005 at 12:34:20AM -0600, Wensheng Wang wrote:> Hi, Ewan, > Thank for for the help. > > I looked at my /var/log/message > The last line when the xend unable to restart domain is: > Nov 7 00:08:07 m8 logger: /etc/xen/scripts/block: xenstore-read > backend/vbd/2/2049/type failed. > > I attached part of xend.log file, the timeline in that log file is: > 23:57:47 machine booted > 00:05:21 xm create fc4 > 00:06:07 xm shutdown -R fc4 > 1minute after, I did a "xm list", it hangs, another minute later, the > prompt came back showing only domain-0This was assigned bug #387, and is now fixed, as of changeset 7651:7e3faea076ec. Cheers, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Wensheng Wang
2005-Nov-09 00:52 UTC
Re: [Xen-devel] could not reboot domU in latest xen-unstable
That works, thank you for fixing it. Today I noticed another case of this when I tried to create a domU: Device 0 (vif) could not be connected. Hotplug scripts not working I got it when I don''t specify vif in my domU config file or when I specify but incorrectly had a xen-br0(should be xenbr0) in vif line. If I correctly specify vif, that errer goes away. Wensheng Wang On 11/8/05, Ewan Mellor <ewan@xensource.com> wrote:> On Mon, Nov 07, 2005 at 12:34:20AM -0600, Wensheng Wang wrote: > > > Hi, Ewan, > > Thank for for the help. > > > > I looked at my /var/log/message > > The last line when the xend unable to restart domain is: > > Nov 7 00:08:07 m8 logger: /etc/xen/scripts/block: xenstore-read > > backend/vbd/2/2049/type failed. > > > > I attached part of xend.log file, the timeline in that log file is: > > 23:57:47 machine booted > > 00:05:21 xm create fc4 > > 00:06:07 xm shutdown -R fc4 > > 1minute after, I did a "xm list", it hangs, another minute later, the > > prompt came back showing only domain-0 > > This was assigned bug #387, and is now fixed, as of changeset > 7651:7e3faea076ec. > > Cheers, > > Ewan. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel