<div>UPDATE</div><div><br></div><div>
I was able to finally get the console connected. This is the only thing that happens before the DomU crashes:
</div><div><br></div><div>Using <class 'grub.GrubConf.GrubConfigFile'> to parse /boot/grub/grub.conf</div>
<div><div>[root@xm3]#</div><div><br></div><div>Here is the /boot/grub/grub.conf from my supermicro server:</div><div><br></div><div><div># grub.conf generated by anaconda</div><div>#</div><div># Note that you do not have to rerun grub after making changes to this file</div><div># NOTICE: You have a /boot partition. This means that</div><div># all kernel and initrd paths are relative to /boot/, eg.</div><div># root (hd0,2)</div><div># kernel /vmlinuz-version ro root=/dev/md1</div><div># initrd /initrd-[generic-]version.img</div><div>#boot=/dev/sdb</div><div>default=0</div><div>timeout=5</div><div>splashimage=(hd0,2)/grub/splash.xpm.gz</div><div>hiddenmenu</div><div>title CentOS (3.5.4-2.el6xen.x86_64)</div><div> root (hd0,2)</div><div> kernel /xen.gz dom0_mem=1024M cpufreq=xen dom0_max_vcpus=4 dom0_vcpus_pin</div><div> module /vmlinuz-3.5.4-2.el6xen.x86_64 ro root=UUID=c1e20d4f-2c51-436d-b1d7-b9024482d5ce rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us rd_MD_UUID=586bdbaf:6a424617:7f257043:fd4ba025 rd_MD_UUID=7410ab1f:e7a157c6:c334ce62:18dd2fc9 SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 rhgb quiet</div><div> module /initramfs-3.5.4-2.el6xen.x86_64.img</div></div><div><br></div><div><br></div><div>Also I noticed that this new server micro server is running a newer version of xen. I was not paying attention and the mirror was updated. </div><div><br></div><div>Working server is running:</div><div><div>xen-libs-4.1.3-2.el6.x86_64</div><div>xen-4.1.3-2.el6.x86_64</div><div>kernel-xen-3.5.4-2.x86_64</div><div>xen-runtime-4.1.3-2.el6.x86_64</div><div>kernel-xen-3.5.4-1.x86_64</div><div>kernel-xen-release-6-3.noarch</div><div>xen-licenses-4.1.3-2.el6.x86_64</div><div>xen-hypervisor-4.1.3-2.el6.x86_64</div></div><div><br></div><div>Non-working:</div><div><div>xen-runtime-4.2.0-1.el6.x86_64</div><div>kernel-xen-3.5.4-2.x86_64</div><div>xen-licenses-4.2.0-1.el6.x86_64</div><div>xen-hypervisor-4.2.0-1.el6.x86_64</div><div>xen-4.2.0-1.el6.x86_64</div><div>kernel-xen-release-6-3.noarch</div><div>xen-libs-4.2.0-1.el6.x86_64</div></div><div><br></div><div>Hope this helps shed any light on this. </div><div><br></div><div>-- </div><div>Joe Fialkowski</div><div>ZoomCloud.net</div><div><br></div></div>
<p style="color: #A0A0A8;">On Wednesday, September 26, 2012 at 10:29 PM, Joe Fialkowski wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<div>
Hello kernel-xen readers,
</div><div><br></div><div>I am new to this list, but I appreciate everything you folks have done for all things Xen and hope to help out in anyway I can. </div><div><br></div><div>I have been using Xen for a few months now and am running the 3.5.4-2 xen kernel on CentOS 6.3. Everything has been working great but I have hit an issue that I am hoping the support from this list can help me overcome. </div><div><br></div><div>Here is the issue:</div><div><br></div><div>I have 3 Servers. Two are HP DL120 G7's with Xeon E3-1230V2 Processors, and hardware raid. The Other server is a super micro with the same CPU spec's but software raid. </div><div><br></div><div>I have Xen PV Images for CentOS 6, Debian 6, Ubuntu 12.04 and Fedora 17. These images work great on DomU's on the HP hardware. However on the super micro server, my Ubuntu and Fedora Images will not boot. They crash almost immediately and I cannot even get a console connected in time (even using xm start -c). </div><div><br></div><div>I am wondering if it has something to do with the hosts partitioning. On the HP hardware it sees /dev/sda for the drive, however on the Supermicro since its software raid, its /dev/md0 which is a raid 1 mirror of sub and sdc. </div><div><br></div><div>I am not sure if that makes a difference or not, I am really shooting in the dark. It may also be worth mentioning I am using SolusVM to provision VPS's across the cluster of Servers. </div><div><br></div><div>Any insight you can share is greatly appreciated. </div>
<div><div><br></div><div>Kind Regards,</div><div><br></div><div>-- </div><div>Joe Fialkowski</div><div><a href="mailto:Joe@ZoomCloud.net">Joe@ZoomCloud.net</a></div><div><br></div></div>
</div><div><div>_______________________________________________</div><div>kernel-xen mailing list</div><div><a href="mailto:kernel-xen@lists.wireless.org.au">kernel-xen@lists.wireless.org.au</a></div><div><a href="https://lists.wireless.org.au/mailman/listinfo/kernel-xen">https://lists.wireless.org.au/mailman/listinfo/kernel-xen</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>