From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: Re: [Qemu-devel] Suggested Parameters for SLES 10 64-bit Date: Tue, 18 May 2010 12:12:21 +0200 Message-ID: <4BF26805.8060008@dlh.net> References: <4BF25A7A.1010305@dlh.net> <5F70B456-4DC8-4A05-A872-00259D6C9374@suse.de> <4BF2647B.4090503@dlh.net> <17B889A5-5DC4-4651-8650-118E984DF711@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from zion.dlh.net ([91.198.192.1]:32957 "EHLO mail.dlh.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755706Ab0ERKM2 (ORCPT ); Tue, 18 May 2010 06:12:28 -0400 In-Reply-To: <17B889A5-5DC4-4651-8650-118E984DF711@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: hi alex, what 64-bit -cpu types do you suggest? when i boot the kernel with "nohpet" it simply hangs shortly after=20 powersaved... br, peter Alexander Graf wrote: > On 18.05.2010, at 11:57, Peter Lieven wrote: > > =20 >> Alexander Graf wrote: >> =20 >>> On 18.05.2010, at 11:14, Peter Lieven wrote: >>> >>> =20 >>> =20 >>>> 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 gu= ests are not >>>> very stable by now. With ACPI they end up in a kernel panic at boo= t time and without >>>> they occasionally hang during boot or shortly after. >>>> =20 >>>> =20 >>> Could you please post the panics you get? What does hang during boo= t mean? >>> =20 >>> =20 >> with acpi=3Doff it hangs after starting powersaved >> =20 >>> The easiest way to get them is probably to start the guest with -se= rial stdio and pass "console=3DttyS0" on the grub command line. >>> >>> =20 >>> =20 >> without acpi=3Doff it hangs always with a lookup. one time it happen= ed 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=3Dkvm_clock while they don't with clocksource=3Dacp= i_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 >> =20 > > What host kernel are you running on? Or rather, what host kvm module = version? > > =20 >> 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_c= ore cdrom parport_pc lp parport ext3 jbd sg sym53c8xx scsi_transport_sp= i 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 >> =20 > > 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. > > =20 >> RIP: 0010:[] {paranoid_restore+8= 1} >> =20 > > Yeah, great. That one's not helpful at all: > > 0xffffffff802dabf1 : iretq =20 > > > =20 >> 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:00000000= 00000000 >> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b >> CR2: 0000000000555b30 CR3: 0000000210fe9000 CR4: 00000000000006e0 >> Process powersaved (pid: 3134, threadinfo ffff810210ff2000, task fff= f810211f83850) >> Stack: ffffffff802dabf1 0000000000000010 0000000000010086 ffffffff80= 41afd8 >> 0000000000000000 0000000000000000 0000000000000000 000000000000= 0000 >> 0000000000000000 0000000000000000 >> Call Trace: {paranoid_restore+81} >> {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! >> =20 > > Please try out different values for -cpu. I think powersaved gets con= fused by the invalid CPU type we're emulating. > > > Alex > > > > =20 --=20 Mit freundlichen Gr=FC=DFen/Kind Regards Peter Lieven =2E....................................................................= =2E.................................... 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=E4ftsf=FChrer: Heiner Lante | Michael Lante Amtsgericht Duisburg | HRB Nr. 12154 USt-Id-Nr.: DE 120607556 =2E....................................................................= =2E...................................=20