 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] svm.c:83:d917 Bad instruction length 0
 We are seeing the same domain crash with a 32-bit win2008 guest under Solaris xen. I'll rebuild xen to dump out the insns in question... Trolle Selander wrote: The easiest (*cough*) way is usually to put in some code before the domain_crash(curr->domain) that dumps the bytes around the eip, but of course that requires that you rebuild xen from source. One fairly painless thing that you could do to at least get a hint of what might be going on is to set on_crash = 'preserve' in the VM configuration file. That way, after it's crashed, you can do an "xm debug-key v" and get some information about the last vmexit, which will at least tell us what type of instruction it was that caused the vmexit.On Tue, Aug 5, 2008 at 1:39 AM, James Harper <james.harper@xxxxxxxxxxxxxxxx <mailto:james.harper@xxxxxxxxxxxxxxxx>> wrote: -- ----------------------------------------------------- Russ Blaine | Solaris Kernel | russell.blaine@xxxxxxx _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |