James Harper wrote:
> Before you get to any of the stuff I wrote below, can you please check
> every logfile you can in Solaris for any useful messages?
>
>
Some partial suspicious log
This is on /var/adm/messages
============================
Nov 7 15:49:20 opensolaris xdb: [ID 945258 kern.notice] NOTICE:
xdb@9,768: unexpected otherend state change to 4!, when status is 0
Nov 7 15:49:50 opensolaris xdb: [ID 945258 kern.notice] NOTICE:
xdb@9,5632: unexpected otherend state change to 4!, when status is 0
This is on /var/log/xen/qemu-dm.1689.log
============================
Register xen platform.
Done register platform.
register acpi io
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
This is on /var/log/xen/xend-debug.log
============================
Failed allocation for dom 8: 1 extents of order 9
ERROR Internal error: Cannot allocate more 2M pages for HVM guest.
(16 = Device busy)
<< repeated several times >>
Failed allocation for dom 9: 1 extents of order 9
ERROR Internal error: Cannot allocate more 2M pages for HVM guest.
(16 = Device busy)
<< repeated several times >>
Failed allocation for dom 10: 1 extents of order 9
ERROR Internal error: Cannot allocate more 2M pages for HVM guest.
(16 = Device busy)
dom 8 is dom id when xennet crashed during install, 9 is when it reboots
and BSOD with 0x7E, 10 is current running domain which I'm collecting
dbgview.log from.
Everything seems normal on /var/log/xen/xpvd-event.log and xend.log
Regards,
Fajar
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home