From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=58931 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OEJYc-0007lS-9j
	for qemu-devel@nongnu.org; Tue, 18 May 2010 05:58:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <pl@dlh.net>) id 1OEJYB-0006Sv-18
	for qemu-devel@nongnu.org; Tue, 18 May 2010 05:57:43 -0400
Received: from zion.dlh.net ([91.198.192.1]:38956 helo=mail.dlh.net)
	by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from <pl@dlh.net>)
	id 1OEJY9-0006QQ-D7
	for qemu-devel@nongnu.org; Tue, 18 May 2010 05:57:22 -0400
Message-ID: <4BF2647B.4090503@dlh.net>
Date: Tue, 18 May 2010 11:57:15 +0200
From: Peter Lieven <pl@dlh.net>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Suggested Parameters for SLES 10 64-bit
References: <4BF25A7A.1010305@dlh.net>
	<5F70B456-4DC8-4A05-A872-00259D6C9374@suse.de>
In-Reply-To: <5F70B456-4DC8-4A05-A872-00259D6C9374@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

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
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
RIP: 0010:[<ffffffff802dabf1>] <ffffffff802dabf1>{paranoid_restore+81}
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!



>> Has anyone experience with suitable kvm and/or kernel parameters to get
>> this stable?
>>     
>
> It should be reasonably stable already. The only issue I'm aware of is the missing kvm-clock, so don't expect your timekeeping inside the guest to be 100% sane.
>
>
> 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

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