Re: [Qemu-devel] Suggested Parameters for SLES 10 64-bit

[Peter Lieven <pl@dlh.net>]

Sorry, ommitted your questions. This particular system
is still runnung on

/kernel: /2.6.31-14-server, /bin: /qemu-kvm-0.12.2, /mod: /kvm-kmod-2.6.32.7

If there where any fixes improvements I can try on:

/kernel: /2.6.33.3, /bin: /qemu-kvm-0.12.4, /mod: /2.6.33.3

BR,
Peter

Alexander Graf wrote:
> On 18.05.2010, at 11:57, Peter Lieven wrote:
>
>   
>> Alexander Graf wrote:
>>     
>>> On 18.05.2010, at 11:14, Peter Lieven wrote:
>>>
>>>  
>>>       
>>>> Hi,
>>>>
>>>> we try to migrate some Suse Linux Enterprise 10 64-bit guests from abandoned
>>>> Virtual Iron by Iron Port to qemu-kvm 0.12.4. Unfortunately the guests are not
>>>> very stable by now. With ACPI they end up in a kernel panic at boot time and without
>>>> they occasionally hang during boot or shortly after.
>>>>    
>>>>         
>>> Could you please post the panics you get? What does hang during boot mean?
>>>  
>>>       
>> with acpi=off it hangs after starting powersaved
>>     
>>> The easiest way to get them is probably to start the guest with -serial stdio and pass "console=ttyS0" on the grub command line.
>>>
>>>  
>>>       
>> without acpi=off it hangs always with a lookup. one time it happened directly after initializing hpet0.
>> btw, is it safe to turn of hpet for linux guests in genereal?
>>
>> regarding missing kvm-clock. i made the experience that some guests crash after live migration
>> with clocksource=kvm_clock while they don't with clocksource=acpi_pm. this is off topic here,
>> but its also something i would like to debug with someone.
>>
>>
>> Starting cupsd                                                        done
>> Starting ZENworks Management Daemon                                   done
>> IA-32 Microcode Update Driver v1.14 unregistered
>> Starting INET services. (xinetd)                                      done
>> Checking/updating CPU microcode                                       done
>> NET: Registered protocol family 10
>> lo: Disabled Privacy Extensions
>> IPv6 over IPv4 tunneling driver
>> ..dead
>> Try to get initial date and time via NTP from 212.110.100.1           done
>> Starting network time protocol daemon (NTPD)                          done
>> Starting Name Service Cache Daemon                                    done
>> NetBackup SAN Client Fibre Transport daemon started.
>> Starting powersaved:                                                  done
>> Starting mail service (Postfix)
>> NMI Watchdog detected LOCKUP on CPU 0
>>     
>
> What host kernel are you running on? Or rather, what host kvm module version?
>
>   
>> CPU 0
>> Modules linked in: ipv6 button battery ac apparmor aamatch_pcre loop usbhid dm_mod 8139cp mii uhci_hcd e1000 i2c_piix4 usbcore ide_cd i2c_core cdrom parport_pc lp parport ext3 jbd sg sym53c8xx scsi_transport_spi edd fan thermal processor piix sd_mod scsi_mod ide_disk ide_core
>> Pid: 3134, comm: powersaved Not tainted 2.6.16.46-0.12-smp #1
>>     
>
> This looks old. The SP3 GM version is 2.6.16.60-0.54.5. This release is definitely out of support :(.
>
> After some searching I found the RPM. That's the SLES10 SP1 GM kernel version. I don't think anyone ever tested that one on kvm.
>
>   
>> RIP: 0010:[<ffffffff802dabf1>] <ffffffff802dabf1>{paranoid_restore+81}
>>     
>
> Yeah, great. That one's not helpful at all:
>
> 0xffffffff802dabf1 <paranoid_restore+81>:	iretq  
>
>
>   
>> RSP: 0000:ffffffff8041afd8  EFLAGS: 00010086
>> RAX: ffffffff88021d50 RBX: ffffffff88021e18 RCX: 00000000b4c562b6
>> RDX: 00000000000001f7 RSI: ffffffff88021e18 RDI: 00000000000001f7
>> RBP: 0000000000000000 R08: 00000000000004e2 R09: ffffffff80417d60
>> R10: 000000000000001f R11: ffffffff8800752c R12: ffffffff88021d00
>> R13: 00000000000004e2 R14: ffffffff80417dac R15: 0000000000000040
>> FS:  00002ae1d26ee760(0000) GS:ffffffff803be000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> CR2: 0000000000555b30 CR3: 0000000210fe9000 CR4: 00000000000006e0
>> Process powersaved (pid: 3134, threadinfo ffff810210ff2000, task ffff810211f83850)
>> Stack: ffffffff802dabf1 0000000000000010 0000000000010086 ffffffff8041afd8
>>      0000000000000000 0000000000000000 0000000000000000 0000000000000000
>>      0000000000000000 0000000000000000
>> Call Trace: <NMI> <ffffffff802dabf1>{paranoid_restore+81} <EOE>
>>      <ffffffff802dabf1>{paranoid_restore+81}
>>
>> Code: 48 cf 65 48 8b 0c 25 10 00 00 00 48 81 e9 d8 1f 00 00 8b 59
>> console shuts up ...
>> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>>     
>
> Please try out different values for -cpu. I think powersaved gets confused by the invalid CPU type we're emulating.
>
>
> Alex
>
>
>
>   


-- 
Mit freundlichen Grüßen/Kind Regards

Peter Lieven

..........................................................................................................

   KAMP Netzwerkdienste GmbH
   Vestische Str. 89-91 | 46117 Oberhausen
   Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
   mailto:pl@kamp.de | http://www.kamp.de

   Geschäftsführer: Heiner Lante | Michael Lante
   Amtsgericht Duisburg | HRB Nr. 12154
   USt-Id-Nr.: DE 120607556

.........................................................................................................