ether with xen4.2.1 : The Xp Blue Screen

109 views
Skip to first unread message

王乐

unread,
Aug 22, 2013, 6:32:55 AM8/22/13
to ether...@googlegroups.com
 I want to patch ether in xen4.2.1 and compiled  ether controller. After that I rebooted in ether, start the command sudo ./ether 1 systrace,
but the xp sp3 32bit was Blue Screen and shows "
A problem has been detected and windows has been shut down to prevent damage to your computer. "
 
I also refer to
https://code.google.com/p/mether/source/browse/trunk/?r=2#trunk%2Fether
and start the syscall trace command, and the Xp system had the same error.

Does anyone have any suggestions on how to fix this?

Thank you for your help,

王乐

unread,
Aug 25, 2013, 8:42:28 AM8/25/13
to ether...@googlegroups.com
It may relate to __vmwrite(GUEST_SYSENTER_EIP, new_eip);?

Artem D

unread,
Aug 25, 2013, 1:20:28 PM8/25/13
to ether...@googlegroups.com
Hi,

I am not sure if anyone else had tried porting ehther to Xen 4.2.1. There are many possibilities about what could be wrong. 

Here are some questions to answer:
- Are you getting vmexits for your faked sysenter_eip? Maybe the address you picked is a valid VA in the guest. Maybe there is some vm control setting that prevents vmexits on page faults. 

An option is to set sysenter_cs to an invalid segment, which will cause a vmexit and be more portable. 

- if you also have instruction tracing, is your guest in non-pae mode and does your shadow page table modification code work?

Finally, if you get it working I hope you release your code. Many people have asked about porting ether to a newer Xen, but no one has had the time to do it. An updated version would be very useful.

Arten
--
 
---
You received this message because you are subscribed to the Google Groups "ether-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ether-devel...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

王乐

unread,
Aug 26, 2013, 10:28:07 AM8/26/13
to ether...@googlegroups.com
Thanks very much for your reply!
(1) When I  start the syscall command, the domU  Blue Screen Immediately and reboot with another domid. I agree that some vm control setting that prevents vmexits on page faults because no printk in dmesg. The faked VA is 0xFFFFD0AE. I try set The CS later.
(2) When   instruction tracing in no-pae mode , the command  suspend  at xc_evtchn_pending function, Maybe there are some problems.
(3) I am very happy to share and discuss the code because my limited capacity, quickly I will copy some key codes, welcome to discuss and guide!
To unsubscribe from this group and stop receiving emails from it, send an email to ether-devel+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages