<div dir="ltr">The Mint14 image is working fine. Three months ago the Mint14 image would crash. I will report these finding on the qemu board. I ust the Mint14 image to create USB boot images that allow me to Juniper VPN RDP to my work PC's using a usb flash. </div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 15, 2013 at 6:47 AM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 03/13/2013 08:34 PM, John Baldwin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A significant amount of patches were installed recently on a my lab<br>
CentOS 6.3 64bit Host. Many "cr" patches installed which I believe<br>
contain what will be part of the soon to release CentOS 6.4. Booting<br>
from Virtual CD images Mint13 32bit Mate install crashes with a qemu<br>
dump. The Mint 14 32 bit mate image boots up with no issues. Doing a<br>
strings on the core dump show the following code:<br>
/lib64/ld-linux-x86-64.so.2<br>
{)V]U| .gdbinit<br>
Recursive internal problem.<br>
Is this a known issue. I can provide more debug info if this would be<br>
worth<br>
checking out<br>
<br>
John Baldwin Sr. Unix Systems Administrator, Clearwater, FL<br>
</blockquote>
<br></div></div>
bisecting to give specific versions of the component causing the regression will help helping you.<br>
in general, sounds like a qemu issue, worth taking to qemu mailing list maybe<br>
<br>
</blockquote></div><br></div>