Bug 114740

Summary:	Virtual machine installation (Xen) aborts
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	peter czanik <peter>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Critical
Priority:	P5 - None	CC:	jsrain, ma, misch, yunfeng.zhao
Version:	Beta 4
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 logs YaST2 logs, xen logs, /etc/xen y2log

Description peter czanik 2005-09-01 15:18:49 UTC

"Virtual machine installation (Xen)" aborts, when "next" is clicked:

Command: /sbin/yast2 vm &
/sbin/yast2: line 207:  8572 Aborted                 $ybindir/y2base $module
"$@" qt -geometry "$Y2_GEOMETRY" $Y2QT_ARGS

Comment 1 Michael Gross 2005-09-01 16:13:16 UTC

This is a YaST-problem, please read:

http://www.opensuse.de/index.php/Bug_Reporting_FAQ#YaST

and provide at least the logfile

Comment 2 peter czanik 2005-09-02 14:34:45 UTC

Created attachment 48605 [details]
YaST2 logs

Comment 3 peter czanik 2005-09-02 14:40:56 UTC

Logs attached. I'm not sure, how useful they are, as I did a lot of things from
YaST, it might be difficult to find.

But: I think, I found the problem: my installation source was 'local'. When I
changed to a http source, the crash disappeared. So, the 'next' button should
probably do some checks, before proceding, at least if a valid installation
source is provided.

Also: I have 3 installation sources: inst-source, inst-source-java and packman.
It has always found packman automatically instead of inst-source. But this
should go probably to a seperate enhancement request...

Comment 4 Christoph Thiel 2005-09-05 10:36:54 UTC

Raising severity to CRITICAL.

Comment 5 Michael Gross 2005-09-05 16:12:47 UTC

Please check if this bug is really `new' and therefore unassigned (or unaccepted).

Comment 6 Ladislav Slezák 2005-09-07 08:34:46 UTC

The last line in the log contains command which starts a new domain in xterm
window. Yast probably aborts at execution of that command.

No idea what could be wrong. I need more information. Could you please enable
debug logging before pressing [Next] button? Press Shift+F7 in GUI and turn
debug off. Then start the installation and attach the logs again.

You can also start the command manualy (as root) and attach the output, if there
is something useful.

Comment 7 peter czanik 2005-09-07 15:32:45 UTC

Created attachment 49080 [details]
YaST2 logs, xen logs, /etc/xen

Comment 8 Ladislav Slezák 2005-09-08 11:59:58 UTC

Hm, the new log contains:

2005-09-07 12:12:25 <0> czp(8655) [bash] ShellCommand.cc(shellcommand):31
shellcommand start
2005-09-07 12:14:27 <0> czp(10690) [bash] ShellCommand.cc(shellcommand):151 Exit
status is 0

So it seems that the VM started properly and the last line is:

2005-09-07 12:14:28 <1> czp(8655) [liby2] genericfrontend.cc(main):497 Finished
YaST2 component 'y2base'

So no abort as I can see, it's OK according to the log.

Please, could you attach the log when the module fails?

Comment 9 peter czanik 2005-09-08 15:16:26 UTC

Created attachment 49228 [details]
y2log

Comment 10 peter czanik 2005-09-08 15:20:59 UTC

I posted a new y2log (this one has the crash, as my first attachement as well).
It comes, when the source is a CD. If I choose a network reachable source, the
'next' button does not crash. That's why I suggested in comment #3, that the
'next' button should check for network reachable source.

Comment 11 Ladislav Slezák 2005-09-09 10:33:07 UTC

*** Bug 115802 has been marked as a duplicate of this bug. ***

Comment 12 Ladislav Slezák 2005-09-09 11:07:58 UTC

fixed in yast2-vm-2.12.4

Comment 13 Ladislav Slezák 2005-09-23 12:35:46 UTC

*** Bug 117685 has been marked as a duplicate of this bug. ***