That means that Xen ran 'pygrub' to extract the kernel & initrd from the
primary disk, but was unable to find a MBR, or grub config or kernel.
Most likely cause is that the previous OS install was not successful
and thus didn't install grub/MBR in the guest.
Dan
Thanks Dan, for your suggest
Veerendra wrote:
Now when I am running virsh using the valgrind it is listing fine!!
But when I am trying to run virsh alone it is dumping the core again.
Attaching the valgrind.log file also.
Does anyone knows why this is behaving as above ?
And the virsh start for my domu1, which is
Daniel Veillard wrote:
I still don't understand how you could get there (remote code
while using xen:///) and why this could crash, except for a previous
memory corruption.
Please run the same command under valgrind and report,
thanks,
Daniel
Now when I am running virsh using the valgrind it
Daniel,
Thanks for the quick reply, It didn't stop at the break
Will this help ?
Rerun under gdb control, as I'm unable to find where this may occur just
from the tack strace given. __virConfReadFile only calls virConfError
which does not call strerror, put a breakpoint in __virConfReadFile a
()
I have installed the following rpms from libvirt.org/libvirt
# rpm -qa | grep virt
libvirt-devel-0.3.3-1
libvirt-0.3.3-1
libvirt-debuginfo-0.3.3-1//
*
With Regards
Veerendra C*
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
