https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c1 --- Comment #1 from Mike Fabian 2008-10-29 05:12:02 MDT --- I start qemu like this: mfabian@magellan:/local2/qemu-images$ cat qemu-11.1-magellan.sh #!/bin/bash set -x NAME=${0##*/} NAME=${NAME%.sh} # aoss qemu-system-x86_64 # I want to test XIM *in* qemu, not outside of it: export XMODIFIERS=@im=local #-usb -usbdevice tablet qemu-system-x86_64 -no-quit -m 512 \ -cdrom /mounts/dist/install/openSUSE-11.1-Beta3/iso/openSUSE-11.1-Beta3-DVD-x86_64.iso \ -boot d \ -hda $NAME.img \ -monitor stdio \ -net nic,model=rtl8139 \ -net user,hostname=$NAME \ -vnc :5 \ $@ # -soundhw es1370 # -k en-us \ # -net tap # -net user,hostname=$NAME \ # -net nic,model=rtl8139 \ # `-boot [a|c|d|n]' # # Boot on floppy (a), hard disk (c), CD-ROM (d), or Etherboot (n). Hard # disk boot is the default. #/dist/install/openSUSE-11.0-Alpha1/openSUSE-11.0-Alpha1-GNOME-i386.iso \ mfabian@magellan:/local2/qemu-images$ -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c3 --- Comment #3 from Mike Fabian 2008-10-29 08:28:20 MDT --- I would like to attache YaST2 logs, but Control+Shift+Alt+x doesn’t give me an xterm anymore at this point and switching to the console doesn’t work either. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c4 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com, uli@novell.com, | |duwe@novell.com Summary|qemu: Installation hangs when the grup package |qemu: Installation hangs when the grub package |is installed |is installed --- Comment #4 from Stefan Hundhammer 2008-11-04 08:42:28 MST --- Normally I would have said that this might be something in the postinstall script of that package that hangs (maybe because YAST_IS_RUNNING not checked properly), but if switching to the console also doesn't work it might be something completely different. Mike, can this be reproduced? If yes: Does it always hang when that package is installed? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c5 Mike Fabian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mfabian@novell.com | --- Comment #5 from Mike Fabian 2008-11-06 08:19:25 MST --- I could reproduce it twice. It is very tedious to reproduce though because qemu without kvm is so slow. I don’t yet know whether it happens with kvm as well. In an attempt to reproduce it in a way which enables me to supply logfiles I tried: - start qemu as written in comment#1 but in linuxrc type install=ftp://dist.suse.de/install/SLP/openSUSE-11.1-Beta4/x86_64/DVD1 (hoping that this makes sure I have network available when I try to copy the logfiles out of qemu). - start an xterm early with Shift+Control+Alt+x and keep it to have it around when the problem occurs and I may not be able to start it anymore. Unfortunately I could not reproduce the same problem that way for some reason this network installation seems to behave differently. It proceeded until some point after the package installation, I don’t know exactly where because I used Korean this time to check some font problems and can’t read Korean. But I could get YaST2 log files at the point where the installation stopped (Will be attached in the next comment). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c7 --- Comment #7 from Mike Fabian 2008-11-06 08:24:46 MST --- The y2log file ends with: 2008-11-06 05:03:12 <1> qemu-11.1-magellan(3284) [YCP] bootloader/grub/misc.ycp:407 Running command /usr/sbin/fix_chs /dev/hda 2 2008-11-06 05:03:12 <1> qemu-11.1-magellan(3284) [YCP] bootloader/grub/misc.ycp:410 Command output: $["exit":127, "stderr":"sh: /usr/sbin/fix_chs: 그런 파일이나 디렉토리 가 없습니다\n", "stdout":""] 2008-11-06 05:03:12 <1> qemu-11.1-magellan(3284) [YCP] bootloader/routines/lib_iface.ycp:322 Updating bootloader configuration 2008-11-06 05:03:12 <1> qemu-11.1-magellan(3284) [wfm] Y2SystemFunction.cc(useRemote):129 'updateBootloader': switched to remote 2008-11-06 05:03:12 <1> qemu-11.1-magellan(3284) [wfm] Y2StdioFunction.cc(evaluateCall):137 Evaluating remote call to 'Bootloader_API::updateBootloader' 2008-11-06 05:03:13 <1> qemu-11.1-magellan(3284) [YCP] bootloader/routines/lib_iface.ycp:324 return value from updateBootloader: true 2008-11-06 05:03:13 <1> qemu-11.1-magellan(3284) [YCP] bootloader/routines/misc.ycp:1142 Installing to floppy: false 2008-11-06 05:03:13 <1> qemu-11.1-magellan(3284) [YCP] bootloader/routines/lib_iface.ycp:335 Initializing bootloader 2008-11-06 05:03:13 <1> qemu-11.1-magellan(3284) [wfm] Y2SystemFunction.cc(useRemote):129 'initializeBootloader': switched to remote 2008-11-06 05:03:13 <1> qemu-11.1-magellan(3284) [wfm] Y2StdioFunction.cc(evaluateCall):137 Evaluating remote call to 'Bootloader_API::initializeBootloader' mfabian@magellan:/local1/bnc/bnc439796/var/log/YaST2$ I.e. this might have something to do with grub as well. Anyway, I can neither complete a DVD nor a network installation of Beta4 in qemu (without kvm, don’t yet know what happens with kvm). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |juhliarik@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c11 Mike Fabian changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |teheo@novell.com --- Comment #11 from Mike Fabian 2008-11-06 08:50:35 MST --- Tejun, can you translate the above message? (I’ll try to reproduce the problem in English but this is unbelievable slow. I could try with kvm (and I will) but I don’t yet know whether it is reproducible with kvm). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c13 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mfabian@novell.com | --- Comment #13 from Lukas Ocilka 2008-11-06 09:27:32 MST --- Ah, in that case it has nothing in common with the bug, it's "kind of" harmless. Anyway, thanks for the translation ;) Good idea. BTW, that means it's probably not needed to provide new logs. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c15 Mike Fabian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mfabian@novell.com | --- Comment #15 from Mike Fabian 2008-11-06 09:50:59 MST --- I left it running overnight and it still hadn’t finished. I should have checked which process uses all the CPU time.

Doing an ssh installation might help (does it work with quemu) as someone else can log into the system later and check it.

I don’t know how to do that, this might be possible but would need a different network setup than the one I used for qemu in comment #1 (-net user). With "-net user" qemu has it’s own subnet protected by a firewall, I can ssh out of qemu but it is difficult to ssh in. I start it with -vnc :5 though, one can acess it graphically with "vncviewer magellan:5" then (Not running right now, I stopped it because it bogged down my machine so much). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=439796 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439796#c17 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mfabian@novell.com --- Comment #17 from Jozef Uhliarik 2008-11-07 03:28:13 MST --- I didn't find any problem with bootloader in yast log. settings seems to be valid and correct. I know that bootloader_finish is not perfect and running takes a lot of time :( but it seems that it works. please attach also yast logs from /mnt/var/log/YaST2 not only logs from inst-sys after that I can continue with analyse. -- 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.