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 1769] New: xl created hvm windows gets stuck after guest

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1769] New: xl created hvm windows gets stuck after guest reboot
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 27 Jun 2011 00:53:37 -0700
Delivery-date: Mon, 27 Jun 2011 00:53:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/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=1769

           Summary: xl created hvm windows gets stuck after guest reboot
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: zhalassy@xxxxxxxxxx


I have xen version 4.1.0, and my dom0 is a gentoo linux 64.

The domU is a windows with paravirtual drivers.
If the windows started with xm create, it works properly, and it can be halted,
rebooted without problems. However, if the windows started with xl create, it
still works till the next guest reboot, as the guest gets stuck, till i reboot
the whole machine. When this happens, the following symptoms can be
experienced:

# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  3829     2     r-----   6062.1

# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  2793     2     r-----    6069.8
(null)                                       1     0     1     --psrd    1310.4

# xl unpause 1

# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  2793     2     r-----    6075.1
(null)                                       1     0     1     ---srd    1310.4

# xl destroy 1
libxl: error: libxl_dm.c:747:libxl__destroy_device_model Couldn't find device
model's pid: No such file or directory
libxl: error: libxl.c:738:libxl_domain_destroy libxl__destroy_device_model
failed for 1

# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  2793     2     r-----    6075.7
(null)                                       1     0     1     --psrd    1310.4

# xm destroy 1
Error: 1
Usage: xm destroy <Domain>

Terminate a domain immediately.

# xl -v dump-core 1 domU.dump
xc: info: exceeded nr_pages (4) losing pages


-- 
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

<Prev in Thread] Current Thread [Next in Thread>