[Bug 820885] New: virt-manager Xen VM install fails due to "No kernel was found." message
https://bugzilla.novell.com/show_bug.cgi?id=820885 https://bugzilla.novell.com/show_bug.cgi?id=820885#c0 Summary: virt-manager Xen VM install fails due to "No kernel was found." message Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: rschaffner@novell.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- When doing an opensuse Xen VM install on a Xen host running openSUSE 12.3 using virt-manager, the install fails after the first reboot with a "No kernel was found. The installation may have failed." message. It looks like the openSUSE Xen VM is trying to use the same temporary kernel file after the first reboot that it used for the install but that tmp file is no longer there. So the install fails. domainbuilder: detail: xc_dom_allocate: cmdline=" install=hd:/dev/xvdb ", features="(null)" libxl: debug: libxl_dom.c:379:libxl__build_pv: pv kernel mapped 0 path /tmp/kernel.TQnGKf domainbuilder: detail: xc_dom_kernel_file: filename="/tmp/kernel.TQnGKf" libxl: error: libxl_dom.c:391:libxl__build_pv: xc_dom_kernel_file failed: No such file or directory homevhst01:~ # rpm -qa | grep virt virt-manager-0.9.4-4.3.1.x86_64 python-virtinst-0.600.3-2.2.1.x86_64 virt-utils-1.1.9-6.1.1.x86_64 libvirt-1.0.2-1.3.1.x86_64 libvirt-client-1.0.2-1.3.1.x86_64 libvirt-python-1.0.2-1.3.1.x86_64 virt-viewer-0.5.4-4.1.1.x86_64 homevhst01:~ # rpm -qa | grep -i xen xen-kmp-desktop-4.2.1_12_k3.7.10_1.1-1.8.1.x86_64 kernel-xen-3.7.10-1.4.1.x86_64 xen-tools-4.2.1_12-1.8.1.x86_64 kernel-xen-3.7.10-1.1.1.x86_64 xen-doc-pdf-4.2.1_12-1.8.1.x86_64 xen-libs-4.2.1_12-1.8.1.x86_64 xen-4.2.1_12-1.8.1.x86_64 patterns-openSUSE-xen_server-12.3-7.10.1.x86_64 xen-doc-html-4.2.1_12-1.8.1.x86_64 homevhst01:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com