[Bug 227909] New: error "failed to create initial ramdisk" misleading
https://bugzilla.novell.com/show_bug.cgi?id=227909 Summary: error "failed to create initial ramdisk" misleading Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de A beginner with XEN selecting to install a VM using the OS installation media got confused by the message "faile to create initial ramdisk" when the wrong media was in the drive. Of cource the initial ramdisk could not be built, but the obvious reason is that the correct media was not found. Maybe add an additional check or progress indicator when bootstrapping VMs. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227909 lbendixs@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbendixs@novell.com AssignedTo|cgriffin@novell.com |carnold@novell.com ------- Comment #1 from lbendixs@novell.com 2006-12-12 08:37 MST ------- This looks like you were using yast2-vm (the yast Virtual Machine Manager) ... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227909 carnold@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|error "failed to create |Yast2-vm: error "failed to create initial |initial ramdisk" misleading |ramdisk" misleading -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227909 carnold@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|carnold@novell.com |ccoffing@novell.com Status|ASSIGNED |NEW ------- Comment #2 from carnold@novell.com 2007-01-17 10:36 MST ------- Reassigned to Chuck for consideration in the new management tool. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227909 ccoffing@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #3 from ccoffing@novell.com 2007-01-17 10:46 MST ------- We won't fix in yast2-vm, but this is fixed in the newer tool (xen-vm-install, part of the xen-tools package.) There is now a well-defined hierarchy of exceptions. In this case, if non-SUSE media were in the drive, you'd get one error; if the media was SUSE but didn't have kernel-xen and/or install-initrd you'd get a different error, etc. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227909 lbendixs@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com