WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 647] New: Creation of Mini-OS domain causes certain xm c

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 647] New: Creation of Mini-OS domain causes certain xm commands to hang
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 17 May 2006 08:19:18 -0700
Delivery-date: Wed, 17 May 2006 08:20:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=647

           Summary: Creation of Mini-OS domain causes certain xm commands to
                    hang
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: aravindh.puthiyaparambil@xxxxxxxxxx


I am seeing a strange issue while running Mini-OS on the changeset
9906:a95e677073c1. This is on both i386 and x86_64. The only difference being
on i386 if I stop printing to the console, this issue is not manifested. But
with x86_64 it happens all the time.

Bringing up Mini-OS for the first time causes xm to hang on certain commands
like "list, destroy". Other commands like "vcpu-list" continue to work. Once I
restart xend, the problem goes away and does not show up again. This happens
only on fresh boots.

I did a little tracing on "xm list". (xm log is at the bottom)

xm list ends up calling
xm/main.py: xm_list()->getDomains()->server.xend.domains(1)
This ends up in
xend/XendDomain.py: xen_domains() -> xc.domain_getinfo() This ends up in
lowlevel/xc/xc.c: pyxc_domain_getinfo()

Strange thing is that can see the last debug print in getDomains before it
called xen_domains() and the last print in xen_domains(). But I cannot see the
next print in getDomains(). Is a locking issue with "domains_lock" happening
somewhere? 

Could someone shed some light on this as to how I can move forward in debugging
this issue?

Thanks,
Aravindh Puthiyaparambil
Xen Development Team
Unisys

[2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:182)
XendDomainInfo.create([\047vm\047, [\047name\047, \047Mini-OS\047],
[\047memory\047, 32], [\047on_crash\047, \047destroy\047], [\047vcpus\047, 1],
[\047image\047, [\047linux\047, [\047kernel\047,
\047/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf\047]]]])
[2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:288)
parseConfig: config is [\047vm\047, [\047name\047, \047Mini-OS\047],
[\047memory\047, 32], [\047on_crash\047, \047destroy\047], [\047vcpus\047, 1],
[\047image\047, [\047linux\047, [\047kernel\047,
\047/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf\047]]]]
[2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:387)
parseConfig: result is {\047uuid\047: None, \047on_crash\047:
\047destroy\047, \047on_reboot\047: None, \047image\047: [\047linux\047,
[\047kernel\047,
\047/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf\047]],
\047on_poweroff\047: None, \047cpus\047: None, \047name\047:
\047Mini-OS\047, \047backend\047: [], \047vcpus\047: 1,
\047cpu_weight\047: None, \047vcpu_avail\047: None, \047memory\047: 32,
\047device\047: [], \047bootloader\047: None, \047cpu\047: None,
\047maxmem\047: None}
[2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1198)
XendDomainInfo.construct: None
[2006-05-01 15:25:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:1230)
XendDomainInfo.initDomain: 1 1.0
[2006-05-01 15:25:01 xend] DEBUG (balloon:126) Balloon: free 3705; need 33;
done.
[2006-05-01 15:25:01 xend] INFO (image:135) buildDomain os=linux dom=1
vcpus=1
[2006-05-01 15:25:01 xend] DEBUG (image:173) dom            = 1
[2006-05-01 15:25:01 xend] DEBUG (image:174) image          =
/root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf
[2006-05-01 15:25:01 xend] DEBUG (image:175) store_evtchn   = 1
[2006-05-01 15:25:01 xend] DEBUG (image:176) console_evtchn = 2
[2006-05-01 15:25:01 xend] DEBUG (image:177) cmdline        = 
[2006-05-01 15:25:01 xend] DEBUG (image:178) ramdisk        = 
[2006-05-01 15:25:01 xend] DEBUG (image:179) vcpus          = 1
[2006-05-01 15:25:01 xend] DEBUG (image:180) features       = 
[2006-05-01 15:25:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:696) Storing VM
details: {\047uuid\047:
\04724928c7b-47eb-97bf-1130-208c7acaf473\047, \047on_reboot\047:
\047restart\047, \047start_time\047: \0471146511501.16\047,
\047on_poweroff\047: \047destroy\047, \047name\047: \047Mini-OS\047,
\047vcpus\047: \0471\047, \047vcpu_avail\047: \0471\047, \047memory\047:
\04732\047, \047on_crash\047: \047destroy\047, \047image\047: \047(linux
(kernel /root/xen/xen-unstable.minios/extras/mini-os/mini-os.elf))\047,
\047maxmem\047: \04732\047}
[2006-05-01 15:25:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:721) Storing
domain details: {\047console/ring-ref\047: \0471280271\047,
\047console/port\047: \0472\047, \047name\047: \047Mini-OS\047,
\047console/limit\047: \0471048576\047, \047vm\047:
\047/vm/24928c7b-47eb-97bf-1130-208c7acaf473\047, \047domid\047:
\0471\047, \047cpu/0/availability\047: \047online\047,
\047memory/target\047: \04732768\047, \047store/ring-ref\047:
\047739584\047, \047store/port\047: \0471\047}
[2006-05-01 15:25:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:901)
XendDomainInfo.handleShutdownWatch
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices vif.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices usb.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices vbd.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices irq.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices pci.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices
ioports.
[2006-05-01 15:25:01 xend] DEBUG (DevController:143) Waiting for devices vtpm.
[2006-05-01 15:25:01 xend] INFO (XendDomain:365) Domain Mini-OS (1) unpaused.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs