[Xen-bugs] [Bug 1278] New: On 32E, XenU guest can not boot up after destorying a HVM guest.

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1278

           Summary: On 32E, XenU guest can not boot up after destorying a
                    HVM guest.
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): ia32 ia32e
Change Set: 17860  17878
Hardware: Clovertown



Bug detailed description:
--------------------------
Firstly we create a HVM guest on 32e host and destory it, then we try to create
one XenU guest, we can not see the boot steps, using "xm list" we can find
guest is running, but using "xm console" can not connect it.
when we destory guest using "xm destory", dom0 will hang with I/O error printed
as bug#1243
If disable VT-d(set iommu=0 in grub) on Dom0, also can reproduce this bug.

since Cset#17830 can not reproduce this bug, we report this new bug different
from bug#1243


ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: (BMDMA stat 0x24)
ata1.00: tag 0 cmd 0xca Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ATA: abnormal status 0xD8 on port 0x18C7
ATA: abnormal status 0xD8 on port 0x18C7
ATA: abnormal status 0xD8 on port 0x18C7
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ATA: abnormal status 0xD8 on port 0x18C7
ATA: abnormal status 0xD8 on port 0x18C7
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1.00: disabled
end_request: I/O error, dev sda, sector 69103
end_request: I/O error, dev sda, sector 54829908
Buffer I/O error on device sda5, logical block 0
lost page write due to I/O error on sda5
Buffer I/O error on device sda5, logical block 1
lost page write due to I/O error on sda5
end_request: I/O error, dev sda, sector 68985684
Buffer I/O error on device sda5, logical block 1769472
lost page write due to I/O error on sda5
end_request: I/O error, dev sda, sector 68985756


Reproduce steps:
----------------
1) create one HVM guest
2) destory this guest
3) try to create one XenU(32pae or 32e) guest, XenU guest can not boot up.
4) try to destory this XenU guest, serial output would print I/O error
infomation.



Basic root-causing log:
----------------------
------- Comment #1 From Xu, Dongxiao 2008-06-19 14:49:58 ------- 
This bug is caused by Xen C/S 17846, it is different from bug 1243. But I think
this one makes bug 1243 easy to be reproduced.

-- Dongxiao


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