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@lists.xensource.com
ReportedBy: zhalassy@loginet.hu
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@lists.xensource.com
http://lists.xensource.com/xen-bugs
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@lists.xensource.com
ReportedBy: zhalassy@loginet.hu
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@lists.xensource.com
http://lists.xensource.com/xen-bugs