Nils Toedtmann
2005-Mar-21 18:40 UTC
[Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
Dear list, after running several days with some domUs, i did a service xend stop service xend start The second failed, /var/log/xend-debug.log said xen.lowlevel.xu.PortError: Failed to map domain control interface Complete xend-debug.log is here: <http://nils.toedtmann.net/stuff/virtualization/xend-debug.log> Two events happened before and may have something to with this oops: python was updated (FC3 2.3.4-11 ==> 2.3.4-13.1), and a domU i rebooted got stuck (it shut down, but did not boot again). All other domains were still runnning and accessable via net. A reboot of the host solved the problem. It was xen-2.0-testing, probably from 2005/03/15, dom0=2.6.11.3, domU=2.6.11.4 (patched with a later xen-2.0-testing) What went wrong? /nils. -- there is no sig ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Nils Toedtmann
2005-Mar-21 19:56 UTC
[Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
Dear list, after running several days with some domUs, i did a service xend stop service xend start The second failed, /var/log/xend-debug.log said xen.lowlevel.xu.PortError: Failed to map domain control interface Complete xend-debug.log is here: <http://nils.toedtmann.net/stuff/virtualization/xend-debug.log> Two events happened before and may have something to with this oops: python was updated (FC3 2.3.4-11 ==> 2.3.4-13.1), and a domU i rebooted got stuck (it shut down, but did not boot again). All other domains were still runnning and accessable via net. A reboot of the host solved the problem. It was xen-2.0-testing, probably from 2005/03/15, dom0=2.6.11.3, domU=2.6.11.4 (patched with a later xen-2.0-testing) What went wrong? /nils. -- no sig ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2005-Mar-21 21:13 UTC
RE: [Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
> The second failed, /var/log/xend-debug.log said > > xen.lowlevel.xu.PortError: Failed to map domain control interface > > Complete xend-debug.log is here: > > <http://nils.toedtmann.net/stuff/virtualization/xend-debug.log> > > Two events happened before and may have something to with this oops: > python was updated (FC3 2.3.4-11 ==> 2.3.4-13.1), and a domU > i rebooted > got stuck (it shut down, but did not boot again).Not enough info in that log to debug things. Was the failed domain still shown as present on xm list? If you were running a debug build (with a serial line), we''d be able to find out more. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Edward Middleton
2005-Mar-24 02:12 UTC
Re: [Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
Ian Pratt wrote:>Not enough info in that log to debug things. > >Was the failed domain still shown as present on xm list? If you were >running a debug build (with a serial line), we''d be able to find out >more. >I am getting the same with the latest 2.0.5. I restarted nps1 domain form a console and that worked, then I tried to restart the dns domain from a console and it hung after the "Restarting system." message. # xm shutdown dns Error: Internal Server Error # xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 9522.8 dns 3 0 0 ---s- 5341.5 9603 nps1 2 127 0 -b--- 7.5 9602 I have attached the xend-debug.log Edward
Ian Pratt
2005-Mar-24 02:26 UTC
RE: [Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
> >Was the failed domain still shown as present on xm list? If you were > >running a debug build (with a serial line), we''d be able to find out > >more. > > > I am getting the same with the latest 2.0.5. I restarted > nps1 domain > form a console and that worked, then I tried to restart the > dns domain > from a console and it hung after the "Restarting system." message. > > # xm shutdown dns > Error: Internal Server Error > > # xm list > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 123 0 r---- 9522.8 > dns 3 0 0 ---s- 5341.5 9603 > nps1 2 127 0 -b--- 7.5 9602 > > I have attached the xend-debug.logThis is pretty odd. It would be really helpful if you could try running a debug build -- "make debug=y world". It''s possible that "xm dmesg" would then tell us something. Even better sould be to get a serial line on the machine, then hitting ''o'' would tell us what''s going on. BTW: Something that would be interesting to know is whether the vifX.0 for the domain (where X=3 in the above case) still exists in domain 0 if you do an "ifconfig vifX.0" Thanks, Ian ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Edward Middleton
2005-Apr-01 06:02 UTC
Re: [Xen-devel] xen.lowlevel.xu.PortError: Failed to map domain control interface
Ian Pratt wrote:>This is pretty odd. It would be really helpful if you could try running >a debug build -- "make debug=y world". It''s possible that "xm dmesg" >would then tell us something. > >I think my problems might have been operator error. After recompiling with debug support and rebooting I can''t get it to reproduce the error.>BTW: Something that would be interesting to know is whether the vifX.0 >for the domain (where X=3 in the above case) still exists in domain 0 if >you do an "ifconfig vifX.0" > >No it didn''t exist after the freeze. Edward _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel