Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 13:41 +0200, Gleb Natapov wrote:
> On Thu, Sep 16, 2010 at 07:37:55PM +0800, Alec Joseph Rivera wrote:
> > On Thu, 2010-09-16 at 13:32 +0200, Joerg Roedel wrote:
> > > On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> > > > On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> > > > 
> > > > Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> > > > time :-)
> > > > 
> > > > Thanks, will update the list when either comes.
> > > 
> > > Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> > > 32 bit hosts.
> > > 
> > 
> > Nice :-) woot woot... Will definite compile a test kernel asap.
> > 
> So your host is 32bit?
> 

Yes. It's Arch-based. I initially thought of installing a 64-bit kernel
when I saw the guest host status on kvm's home, but programs are
compiled 32-bit. I was put off thinking about binary compatibility.

Haven't tested such since my Debian days...

> --
>   Gleb.


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Joerg Roedel 
On Thu, Sep 16, 2010 at 03:35:17PM +0400, Michael Tokarev wrote:
> 16.09.2010 15:32, Joerg Roedel пишет:
> > On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> >> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> >>
> >> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> >> time :-)
> >>
> >> Thanks, will update the list when either comes.
> > 
> > Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> > 32 bit hosts.
> 
> What commit it is?
> 
> I swear I saw it in 2.6.32-stable somewhere.  Is it this one (2.6.32.12):

It is 16518d5ada690643453eb0aef3cc7841d3623c2d in latest linus/master
branch. It was merged between -rc3 and -rc4.

Joerg

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 07:37:55PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 13:32 +0200, Joerg Roedel wrote:
> > On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> > > On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> > > 
> > > Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> > > time :-)
> > > 
> > > Thanks, will update the list when either comes.
> > 
> > Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> > 32 bit hosts.
> > 
> 
> Nice :-) woot woot... Will definite compile a test kernel asap.
> 
So your host is 32bit?

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 03:35:17PM +0400, Michael Tokarev wrote:
> 16.09.2010 15:32, Joerg Roedel пишет:
> > On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> >> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> >>
> >> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> >> time :-)
> >>
> >> Thanks, will update the list when either comes.
> > 
> > Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> > 32 bit hosts.
> 
> What commit it is?
> 
> I swear I saw it in 2.6.32-stable somewhere.  Is it this one (2.6.32.12):
> 
it is 16518d5ada690643453eb0aef3cc7841d3623c2d, but the bug shouldn't be
present in 2.6.32.

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 13:32 +0200, Joerg Roedel wrote:
> On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> > On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> > 
> > Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> > time :-)
> > 
> > Thanks, will update the list when either comes.
> 
> Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> 32 bit hosts.
> 

Nice :-) woot woot... Will definite compile a test kernel asap.

>   Joerg
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Michael Tokarev 
16.09.2010 15:32, Joerg Roedel пишет:
> On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
>> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
>>
>> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
>> time :-)
>>
>> Thanks, will update the list when either comes.
> 
> Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
> 32 bit hosts.

What commit it is?

I swear I saw it in 2.6.32-stable somewhere.  Is it this one (2.6.32.12):

From: Gleb Natapov 
Date: Fri, 19 Mar 2010 15:47:31 +0100
Subject: KVM: x86 emulator: fix memory access during x86 emulation
To: sta...@kernel.org
Cc: Marcelo Tosatti , Avi Kivity , Gleb 
Natapov 
Message-ID: <1269010059-25309-4-git-send-email-stefan.ba...@canonical.com>


From: Gleb Natapov 

commit 1871c6020d7308afb99127bba51f04548e7ca84e upstream

Currently when x86 emulator needs to access memory, page walk is done with
broadest permission possible, so if emulated instruction was executed
by userspace process it can still access kernel memory. Fix that by
providing correct memory access to page walker during emulation.


/mjt
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Joerg Roedel 
On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> 
> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
> time :-)
> 
> Thanks, will update the list when either comes.

Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem on
32 bit hosts.

Joerg

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 07:13:03PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 12:14 +0200, Gleb Natapov wrote:
> > On Thu, Sep 16, 2010 at 06:11:36PM +0800, Alec Joseph Rivera wrote:
> > > On Thu, 2010-09-16 at 16:03 +0800, Alec Joseph Rivera wrote:
> > > > On Thu, 2010-09-16 at 09:56 +0200, Gleb Natapov wrote:
> > > > > On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> > > > > > On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > > > > > > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera 
> > > > > > > wrote:
> > > > > > > > > That should give us a clue on what's going wrong.
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > I did the steps you mentioned. Here's the gdb transcript:
> > > > > > > > 
> > > > > > > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > > > > > > What is k12_1009? Are you sure this is vmlinux?
> > > > > > > 
> > > > > > 
> > > > > > Hi Gleb:
> > > > > > 
> > > > > > Yes, k12_1009 is the kernel image that isolinux loads.
> > > > > > 
> > > > > > -- isolinux.cfg
> > > > > > 
> > > > > > > DEFAULT 1
> > > > > > > TIMEOUT 100
> > > > > > > PROMPT 1
> > > > > > > DISPLAY isolinux.txt
> > > > > > > LABEL 1
> > > > > > > KERNEL k12_1009
> > > > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > > > LABEL 2
> > > > > > > KERNEL k12_1009
> > > > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > > > BOOT_SUPPORT=1 
> > > > > > 
> > > > > > -- file test
> > > > > > > $ file k12_1009 
> > > > > > > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > > > > > > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, 
> > > > > > > swap_dev 0x1, Normal VGA
> > > > > > 
> > > > > This is bzImage, You need corresponding vmlinux bzImage was created
> > > > > from.
> > > > 
> > > > Oh I see. Thanks for pointing that out. Unfortunately, I don't think I
> > > > can get that image. Either I ask someone from Novell or IBM.
> > > > 
> > > > I'll try crawling the system's filesystem, maybe I can find it there...
> > > > Will keep you updated.
> > > > 
> > > 
> > > No vmlinux/z image found on cd or an installed system :-(
> > > 
> > > 
> > It may be hidden somewhere in debug rpm.
> > 
> 
> Sadly, Lotus Foundations doesn't supply the debug rpms :-(
> 
Looks like Alexander already found relevant rpm.

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 12:14 +0200, Gleb Natapov wrote:
> On Thu, Sep 16, 2010 at 06:11:36PM +0800, Alec Joseph Rivera wrote:
> > On Thu, 2010-09-16 at 16:03 +0800, Alec Joseph Rivera wrote:
> > > On Thu, 2010-09-16 at 09:56 +0200, Gleb Natapov wrote:
> > > > On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> > > > > On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > > > > > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > > > > > That should give us a clue on what's going wrong.
> > > > > > > > 
> > > > > > > 
> > > > > > > I did the steps you mentioned. Here's the gdb transcript:
> > > > > > > 
> > > > > > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > > > > > What is k12_1009? Are you sure this is vmlinux?
> > > > > > 
> > > > > 
> > > > > Hi Gleb:
> > > > > 
> > > > > Yes, k12_1009 is the kernel image that isolinux loads.
> > > > > 
> > > > > -- isolinux.cfg
> > > > > 
> > > > > > DEFAULT 1
> > > > > > TIMEOUT 100
> > > > > > PROMPT 1
> > > > > > DISPLAY isolinux.txt
> > > > > > LABEL 1
> > > > > > KERNEL k12_1009
> > > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > > LABEL 2
> > > > > > KERNEL k12_1009
> > > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > > BOOT_SUPPORT=1 
> > > > > 
> > > > > -- file test
> > > > > > $ file k12_1009 
> > > > > > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > > > > > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, 
> > > > > > swap_dev 0x1, Normal VGA
> > > > > 
> > > > This is bzImage, You need corresponding vmlinux bzImage was created
> > > > from.
> > > 
> > > Oh I see. Thanks for pointing that out. Unfortunately, I don't think I
> > > can get that image. Either I ask someone from Novell or IBM.
> > > 
> > > I'll try crawling the system's filesystem, maybe I can find it there...
> > > Will keep you updated.
> > > 
> > 
> > No vmlinux/z image found on cd or an installed system :-(
> > 
> > 
> It may be hidden somewhere in debug rpm.
> 

Sadly, Lotus Foundations doesn't supply the debug rpms :-(

> --
>   Gleb.


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> On Thu, Sep 16, 2010 at 12:27:29PM +0200, Alexander Graf wrote:
> > Alec Joseph Rivera wrote:
> > > Program received signal SIGINT, Interrupt.
> > > 0xc015405f in ?? ()
> > > (gdb) bt
> > > #0  0xc015405f in ?? ()
> > >   
> > 
> > 0xc015405a <__pte_alloc_kernel+82>:mov(%edi),%eax
> > 0xc015405c <__pte_alloc_kernel+84>:mov0x4(%edi),%edx
> > 0xc015405f <__pte_alloc_kernel+87>:lock cmpxchg8b (%edi)
> > 0xc0154063 <__pte_alloc_kernel+91>:jne0xc015405a
> > <__pte_alloc_kernel+82>
> 
> This looks like a bug I also have seen recently on 32 bit host-kvm. The
> instruction emulation for 'lock cmpxchg8b' was broken so that the rip
> was not advanced and the guest just iterated over this instruction again
> and again. I thought this was fixed with the latest kvm updates in
> 2.6.36.
> 

Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
time :-)

Thanks, will update the list when either comes.

>   Joerg
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Joerg Roedel 
On Thu, Sep 16, 2010 at 12:27:29PM +0200, Alexander Graf wrote:
> Alec Joseph Rivera wrote:
> > Program received signal SIGINT, Interrupt.
> > 0xc015405f in ?? ()
> > (gdb) bt
> > #0  0xc015405f in ?? ()
> >   
> 
> 0xc015405a <__pte_alloc_kernel+82>:mov(%edi),%eax
> 0xc015405c <__pte_alloc_kernel+84>:mov0x4(%edi),%edx
> 0xc015405f <__pte_alloc_kernel+87>:lock cmpxchg8b (%edi)
> 0xc0154063 <__pte_alloc_kernel+91>:jne0xc015405a
> <__pte_alloc_kernel+82>

This looks like a bug I also have seen recently on 32 bit host-kvm. The
instruction emulation for 'lock cmpxchg8b' was broken so that the rip
was not advanced and the guest just iterated over this instruction again
and again. I thought this was fixed with the latest kvm updates in
2.6.36.

Joerg

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alexander Graf 
Alec Joseph Rivera wrote:
> On Wed, 2010-09-15 at 20:15 +0200, Alexander Graf wrote:
>   
>> On 15.09.2010, at 20:07, Alec Joseph Rivera wrote:
>>
>> 
>>> On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
>>>   
 On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:

 
> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
>   
>> On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
>>
>> 
>>> Hi all:
>>>
>>> I'm Alec Joseph Rivera, from the Philippines and new on this list.
>>> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
>>> bootup. It stops right after:
>>>
>>> Checking if this processor honours the WP bit even in supervisor
>>> mode... Ok.
>>>
>>> There's no more output after that. My invocation line is:
>>>
>>> $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
>>>   
>> Your host is probably too new for this old guest. -cpu host directly 
>> passes through this host cpu's identifiers on which the guest might 
>> choke. Please try again without -cpu.
>>
>>
>> 
> Tried without -cpu, still hangs after the WP bit checking...
>
> $ qemu-kvm -m 1G -cdrom lfs.iso
>
> I was scanning the changelogs and read something about a
> -no-kernel-irqchip. The man page doesn't say anything about it but will
> try this one too..
>   
 Please try:

 $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio

 Then when it shows the bootloader, add "console=ttyS0" to the kernel 
 command line. That should give all the debugging output necessary.


 
>>> Already done this one too (I've read it from your conversations with a
>>> Peter guy if I'm not mistaken).
>>>
>>> It just stops with no panic messages right after the mentioned checking
>>> part, which made me dig after timers (bogomips calibration should be
>>> next I believe). But I've gotten nowhere so far...
>>>
>>> Also, there's no -no-kernel-irqchip parameter, must have been a typo for
>>> -no-kvm-irqchip.
>>>
>>> -- begin kernel messages
>>>   
 Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
 

Took me quite a while to find that kernel in the graveyard :). It's a
SLES10 SP1 kernel from the update repo at one specific point in time
(more updates came after that one).

 BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f400 (usable)
 BIOS-e820: 0009f400 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 3fffd000 (usable)
 BIOS-e820: 3fffd000 - 4000 (reserved)
 BIOS-e820: fffbc000 - 0001 (reserved)
 127MB HIGHMEM available.
 895MB LOWMEM available.
 found SMP MP-table at 000f8990
 DMI 2.4 present.
 Using APIC driver default
 ACPI: PM-Timer IO Port: 0xb008
 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
 Processor #0 15:11 APIC version 20
 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
 Processor #1 15:11 APIC version 20
 Overriding APIC driver with bigsmp
 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
 IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23
 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
 ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
 ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
 ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
 ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
 Enabling APIC mode:  Physflat.  Using 1 I/O APICs
 ACPI: HPET id: 0x8086a201 base: 0xfed0
 Using ACPI (MADT) for SMP configuration information
 Allocating PCI resources starting at 5000 (gap: 4000:bffbc000)
 Built 1 zonelists
 Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram 
 BOOT_IMAGE=k12_1009 console=ttyS0
 Enabling fast FPU save and restore... done.
 Enabling unmasked SIMD FPU exception support... done.
 Initializing CPU#0
 PID hash table entries: 4096 (order: 12, 65536 bytes)
 Console: colour VGA+ 80x25
 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
 Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
 Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
 890k data, 200k init, 131064k highmem)
 Checking if this processor honours the WP bit even in supervisor mode... 
 Ok.
 
>> Interesting. Mind to check if you find a the vmlinux binary for that kernel 
>> on the cd? Maybe it's hidden inside an rpm. Then you can use:
>>
>> $ qemu-kvm -s -cdrom ...
>> $ gdb  -ex 'target remote localhost:1234'
>>
>

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 06:11:36PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 16:03 +0800, Alec Joseph Rivera wrote:
> > On Thu, 2010-09-16 at 09:56 +0200, Gleb Natapov wrote:
> > > On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> > > > On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > > > > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > > > > That should give us a clue on what's going wrong.
> > > > > > > 
> > > > > > 
> > > > > > I did the steps you mentioned. Here's the gdb transcript:
> > > > > > 
> > > > > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > > > > What is k12_1009? Are you sure this is vmlinux?
> > > > > 
> > > > 
> > > > Hi Gleb:
> > > > 
> > > > Yes, k12_1009 is the kernel image that isolinux loads.
> > > > 
> > > > -- isolinux.cfg
> > > > 
> > > > > DEFAULT 1
> > > > > TIMEOUT 100
> > > > > PROMPT 1
> > > > > DISPLAY isolinux.txt
> > > > > LABEL 1
> > > > > KERNEL k12_1009
> > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > LABEL 2
> > > > > KERNEL k12_1009
> > > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > > BOOT_SUPPORT=1 
> > > > 
> > > > -- file test
> > > > > $ file k12_1009 
> > > > > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > > > > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, swap_dev 
> > > > > 0x1, Normal VGA
> > > > 
> > > This is bzImage, You need corresponding vmlinux bzImage was created
> > > from.
> > 
> > Oh I see. Thanks for pointing that out. Unfortunately, I don't think I
> > can get that image. Either I ask someone from Novell or IBM.
> > 
> > I'll try crawling the system's filesystem, maybe I can find it there...
> > Will keep you updated.
> > 
> 
> No vmlinux/z image found on cd or an installed system :-(
> 
> 
It may be hidden somewhere in debug rpm.

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 16:03 +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 09:56 +0200, Gleb Natapov wrote:
> > On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> > > On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > > > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > > > That should give us a clue on what's going wrong.
> > > > > > 
> > > > > 
> > > > > I did the steps you mentioned. Here's the gdb transcript:
> > > > > 
> > > > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > > > What is k12_1009? Are you sure this is vmlinux?
> > > > 
> > > 
> > > Hi Gleb:
> > > 
> > > Yes, k12_1009 is the kernel image that isolinux loads.
> > > 
> > > -- isolinux.cfg
> > > 
> > > > DEFAULT 1
> > > > TIMEOUT 100
> > > > PROMPT 1
> > > > DISPLAY isolinux.txt
> > > > LABEL 1
> > > > KERNEL k12_1009
> > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > LABEL 2
> > > > KERNEL k12_1009
> > > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > > BOOT_SUPPORT=1 
> > > 
> > > -- file test
> > > > $ file k12_1009 
> > > > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > > > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, swap_dev 
> > > > 0x1, Normal VGA
> > > 
> > This is bzImage, You need corresponding vmlinux bzImage was created
> > from.
> 
> Oh I see. Thanks for pointing that out. Unfortunately, I don't think I
> can get that image. Either I ask someone from Novell or IBM.
> 
> I'll try crawling the system's filesystem, maybe I can find it there...
> Will keep you updated.
> 

No vmlinux/z image found on cd or an installed system :-(


> > 
> > > > BTW what version on kvm/qemu are you using.
> > > > 
> > > 
> > > qemu's version is 0.12.5. modinfo kvm doesn't reveal any version string
> > > though, however the kernel is 2.6.35 from Arch.
> > > 
> > > Question: from what I've read so far kvm versions are of 'kvm-xx' where
> > > xx is a number, on sourceforge there is kvm-kmod-{kernel-version}, am I
> > > correct in assuming and saying then that my kvm version is 2.6.35?
> > > 
> > kvm-xx is deprecated. So when asked what kvm are you using you should
> > provide your kernel version like you did.
> > 
> > --
> > Gleb.
> 
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 16:32 +0800, Dave Young wrote:
> On Thu, Sep 16, 2010 at 4:17 PM, Alec Joseph Rivera  wrote:
> > On Wed, 2010-09-15 at 22:37 +0400, Michael Tokarev wrote:
> >> Alec Joseph Rivera wrote:
> >> []
> >> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k 
> >> >> reserved, 890k data, 200k init, 131064k highmem)
> >> >> Checking if this processor honours the WP bit even in supervisor 
> >> >> mode... Ok.
> >> > -- end
> >>
> >> Hm.  There was some error with earlier kernels and
> >> kvm that resulted in exactly this behavour.  Maybe
> >> even a (guest) kernel bug.. no?  My memory is vague
> >> in this area, but it tells there was something...
> >>
> >
> > Hi Michael:
> >
> > I suspect has something to do with loops (re: bogomips calibration) or
> > timers (re: calibration + pci probing). Will verify this when I get the
> > time to read the source.
> >
> > Maybe someone more familiar with this kernel area can shed some light on
> > the topic too...? :-) only if I'm not stretching too much..
> 
> boot with param lpj=xxx to avoid calibration
> 
> copy xxx value from your normal boot kernel messages

Hi Dave:

Crossing out calibration, added the lpj parameter (and combinations with
-no-hpet and -no-kvm-irqchip) but still hangs after WP bit checking.

> >
> >> /mjt
> >
> >
> > --
> > ---
> >
> >
> > Follow me:
> > http://twitter.com/agirivera
> > Invite as a
> > friend:
> > http://www.facebook.com/agirivera
> >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majord...@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> 
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Dave Young 
On Thu, Sep 16, 2010 at 4:17 PM, Alec Joseph Rivera  wrote:
> On Wed, 2010-09-15 at 22:37 +0400, Michael Tokarev wrote:
>> Alec Joseph Rivera wrote:
>> []
>> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
>> >> 890k data, 200k init, 131064k highmem)
>> >> Checking if this processor honours the WP bit even in supervisor mode... 
>> >> Ok.
>> > -- end
>>
>> Hm.  There was some error with earlier kernels and
>> kvm that resulted in exactly this behavour.  Maybe
>> even a (guest) kernel bug.. no?  My memory is vague
>> in this area, but it tells there was something...
>>
>
> Hi Michael:
>
> I suspect has something to do with loops (re: bogomips calibration) or
> timers (re: calibration + pci probing). Will verify this when I get the
> time to read the source.
>
> Maybe someone more familiar with this kernel area can shed some light on
> the topic too...? :-) only if I'm not stretching too much..

boot with param lpj=xxx to avoid calibration

copy xxx value from your normal boot kernel messages
>
>> /mjt
>
>
> --
> ---
>
>
> Follow me:
> http://twitter.com/agirivera
> Invite as a
> friend:
> http://www.facebook.com/agirivera
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Regards
dave
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Wed, 2010-09-15 at 22:37 +0400, Michael Tokarev wrote:
> Alec Joseph Rivera wrote:
> []
> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
> >> 890k data, 200k init, 131064k highmem)
> >> Checking if this processor honours the WP bit even in supervisor mode... 
> >> Ok.
> > -- end
> 
> Hm.  There was some error with earlier kernels and
> kvm that resulted in exactly this behavour.  Maybe
> even a (guest) kernel bug.. no?  My memory is vague
> in this area, but it tells there was something...
> 

Hi Michael:

I suspect has something to do with loops (re: bogomips calibration) or
timers (re: calibration + pci probing). Will verify this when I get the
time to read the source.

Maybe someone more familiar with this kernel area can shed some light on
the topic too...? :-) only if I'm not stretching too much..

> /mjt


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 09:56 +0200, Gleb Natapov wrote:
> On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> > On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > > That should give us a clue on what's going wrong.
> > > > > 
> > > > 
> > > > I did the steps you mentioned. Here's the gdb transcript:
> > > > 
> > > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > > What is k12_1009? Are you sure this is vmlinux?
> > > 
> > 
> > Hi Gleb:
> > 
> > Yes, k12_1009 is the kernel image that isolinux loads.
> > 
> > -- isolinux.cfg
> > 
> > > DEFAULT 1
> > > TIMEOUT 100
> > > PROMPT 1
> > > DISPLAY isolinux.txt
> > > LABEL 1
> > > KERNEL k12_1009
> > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > LABEL 2
> > > KERNEL k12_1009
> > > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > > BOOT_SUPPORT=1 
> > 
> > -- file test
> > > $ file k12_1009 
> > > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, swap_dev 0x1, 
> > > Normal VGA
> > 
> This is bzImage, You need corresponding vmlinux bzImage was created
> from.

Oh I see. Thanks for pointing that out. Unfortunately, I don't think I
can get that image. Either I ask someone from Novell or IBM.

I'll try crawling the system's filesystem, maybe I can find it there...
Will keep you updated.

> 
> > > BTW what version on kvm/qemu are you using.
> > > 
> > 
> > qemu's version is 0.12.5. modinfo kvm doesn't reveal any version string
> > though, however the kernel is 2.6.35 from Arch.
> > 
> > Question: from what I've read so far kvm versions are of 'kvm-xx' where
> > xx is a number, on sourceforge there is kvm-kmod-{kernel-version}, am I
> > correct in assuming and saying then that my kvm version is 2.6.35?
> > 
> kvm-xx is deprecated. So when asked what kvm are you using you should
> provide your kernel version like you did.
> 
> --
>   Gleb.


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 03:52:17PM +0800, Alec Joseph Rivera wrote:
> On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> > On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > > That should give us a clue on what's going wrong.
> > > > 
> > > 
> > > I did the steps you mentioned. Here's the gdb transcript:
> > > 
> > > $ gdb k12_1009 -ex 'target remote localhost:1234'
> > What is k12_1009? Are you sure this is vmlinux?
> > 
> 
> Hi Gleb:
> 
> Yes, k12_1009 is the kernel image that isolinux loads.
> 
> -- isolinux.cfg
> 
> > DEFAULT 1
> > TIMEOUT 100
> > PROMPT 1
> > DISPLAY isolinux.txt
> > LABEL 1
> > KERNEL k12_1009
> > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > LABEL 2
> > KERNEL k12_1009
> > APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> > BOOT_SUPPORT=1 
> 
> -- file test
> > $ file k12_1009 
> > k12_1009: Linux kernel x86 boot executable bzImage, version 
> > 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, swap_dev 0x1, 
> > Normal VGA
> 
This is bzImage, You need corresponding vmlinux bzImage was created
from.

> > BTW what version on kvm/qemu are you using.
> > 
> 
> qemu's version is 0.12.5. modinfo kvm doesn't reveal any version string
> though, however the kernel is 2.6.35 from Arch.
> 
> Question: from what I've read so far kvm versions are of 'kvm-xx' where
> xx is a number, on sourceforge there is kvm-kmod-{kernel-version}, am I
> correct in assuming and saying then that my kvm version is 2.6.35?
> 
kvm-xx is deprecated. So when asked what kvm are you using you should
provide your kernel version like you did.

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-16 Thread Alec Joseph Rivera 
On Thu, 2010-09-16 at 08:39 +0200, Gleb Natapov wrote:
> On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > > That should give us a clue on what's going wrong.
> > > 
> > 
> > I did the steps you mentioned. Here's the gdb transcript:
> > 
> > $ gdb k12_1009 -ex 'target remote localhost:1234'
> What is k12_1009? Are you sure this is vmlinux?
> 

Hi Gleb:

Yes, k12_1009 is the kernel image that isolinux loads.

-- isolinux.cfg

> DEFAULT 1
> TIMEOUT 100
> PROMPT 1
> DISPLAY isolinux.txt
> LABEL 1
> KERNEL k12_1009
> APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram 
> LABEL 2
> KERNEL k12_1009
> APPEND ramdisk_size=32768 initrd=initrd root=/dev/ram BOOT_SUPPORT=1 

-- file test
> $ file k12_1009 
> k12_1009: Linux kernel x86 boot executable bzImage, version 
> 2.6.16.54-0.2.5-bigsmp (ge...@b, RO-rootFS, root_dev 0x301, swap_dev 0x1, 
> Normal VGA

> BTW what version on kvm/qemu are you using.
> 

qemu's version is 0.12.5. modinfo kvm doesn't reveal any version string
though, however the kernel is 2.6.35 from Arch.

Question: from what I've read so far kvm versions are of 'kvm-xx' where
xx is a number, on sourceforge there is kvm-kmod-{kernel-version}, am I
correct in assuming and saying then that my kvm version is 2.6.35?

Thanks...

> --
>   Gleb.


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Gleb Natapov 
On Thu, Sep 16, 2010 at 09:55:38AM +0800, Alec Joseph Rivera wrote:
> > That should give us a clue on what's going wrong.
> > 
> 
> I did the steps you mentioned. Here's the gdb transcript:
> 
> $ gdb k12_1009 -ex 'target remote localhost:1234'
What is k12_1009? Are you sure this is vmlinux?

BTW what version on kvm/qemu are you using.

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alec Joseph Rivera 
On Wed, 2010-09-15 at 20:15 +0200, Alexander Graf wrote:
> On 15.09.2010, at 20:07, Alec Joseph Rivera wrote:
> 
> > On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
> >> On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:
> >> 
> >>> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
>  On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
>  
> > Hi all:
> > 
> > I'm Alec Joseph Rivera, from the Philippines and new on this list.
> > Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> > bootup. It stops right after:
> > 
> > Checking if this processor honours the WP bit even in supervisor
> > mode... Ok.
> > 
> > There's no more output after that. My invocation line is:
> > 
> > $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
>  
>  Your host is probably too new for this old guest. -cpu host directly 
>  passes through this host cpu's identifiers on which the guest might 
>  choke. Please try again without -cpu.
>  
>  
> >>> 
> >>> Tried without -cpu, still hangs after the WP bit checking...
> >>> 
> >>> $ qemu-kvm -m 1G -cdrom lfs.iso
> >>> 
> >>> I was scanning the changelogs and read something about a
> >>> -no-kernel-irqchip. The man page doesn't say anything about it but will
> >>> try this one too..
> >> 
> >> Please try:
> >> 
> >> $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio
> >> 
> >> Then when it shows the bootloader, add "console=ttyS0" to the kernel 
> >> command line. That should give all the debugging output necessary.
> >> 
> >> 
> > 
> > Already done this one too (I've read it from your conversations with a
> > Peter guy if I'm not mistaken).
> > 
> > It just stops with no panic messages right after the mentioned checking
> > part, which made me dig after timers (bogomips calibration should be
> > next I believe). But I've gotten nowhere so far...
> > 
> > Also, there's no -no-kernel-irqchip parameter, must have been a typo for
> > -no-kvm-irqchip.
> > 
> > -- begin kernel messages
> >> Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
> >> 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
> >> BIOS-provided physical RAM map:
> >> BIOS-e820:  - 0009f400 (usable)
> >> BIOS-e820: 0009f400 - 000a (reserved)
> >> BIOS-e820: 000f - 0010 (reserved)
> >> BIOS-e820: 0010 - 3fffd000 (usable)
> >> BIOS-e820: 3fffd000 - 4000 (reserved)
> >> BIOS-e820: fffbc000 - 0001 (reserved)
> >> 127MB HIGHMEM available.
> >> 895MB LOWMEM available.
> >> found SMP MP-table at 000f8990
> >> DMI 2.4 present.
> >> Using APIC driver default
> >> ACPI: PM-Timer IO Port: 0xb008
> >> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> >> Processor #0 15:11 APIC version 20
> >> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> >> Processor #1 15:11 APIC version 20
> >> Overriding APIC driver with bigsmp
> >> ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
> >> IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> >> Enabling APIC mode:  Physflat.  Using 1 I/O APICs
> >> ACPI: HPET id: 0x8086a201 base: 0xfed0
> >> Using ACPI (MADT) for SMP configuration information
> >> Allocating PCI resources starting at 5000 (gap: 4000:bffbc000)
> >> Built 1 zonelists
> >> Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram 
> >> BOOT_IMAGE=k12_1009 console=ttyS0
> >> Enabling fast FPU save and restore... done.
> >> Enabling unmasked SIMD FPU exception support... done.
> >> Initializing CPU#0
> >> PID hash table entries: 4096 (order: 12, 65536 bytes)
> >> Console: colour VGA+ 80x25
> >> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
> >> 890k data, 200k init, 131064k highmem)
> >> Checking if this processor honours the WP bit even in supervisor mode... 
> >> Ok.
> 
> Interesting. Mind to check if you find a the vmlinux binary for that kernel 
> on the cd? Maybe it's hidden inside an rpm. Then you can use:
> 
> $ qemu-kvm -s -cdrom ...
> $ gdb  -ex 'target remote localhost:1234'
> 
> (gdb) bt
> 
> That should give us a clue on what's going wrong.
> 

I did the steps you mentioned. Here's the gdb transcript:

$ gdb k12_1009 -ex 'target remote localhost:1234'
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you a

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Michael Tokarev 
Alec Joseph Rivera wrote:
[]
>> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
>> 890k data, 200k init, 131064k highmem)
>> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> -- end

Hm.  There was some error with earlier kernels and
kvm that resulted in exactly this behavour.  Maybe
even a (guest) kernel bug.. no?  My memory is vague
in this area, but it tells there was something...

/mjt
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alec Joseph Rivera 
On Wed, 2010-09-15 at 20:15 +0200, Alexander Graf wrote:
> On 15.09.2010, at 20:07, Alec Joseph Rivera wrote:
> 
> > On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
> >> On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:
> >> 
> >>> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
>  On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
>  
> > Hi all:
> > 
> > I'm Alec Joseph Rivera, from the Philippines and new on this list.
> > Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> > bootup. It stops right after:
> > 
> > Checking if this processor honours the WP bit even in supervisor
> > mode... Ok.
> > 
> > There's no more output after that. My invocation line is:
> > 
> > $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
>  
>  Your host is probably too new for this old guest. -cpu host directly 
>  passes through this host cpu's identifiers on which the guest might 
>  choke. Please try again without -cpu.
>  
>  
> >>> 
> >>> Tried without -cpu, still hangs after the WP bit checking...
> >>> 
> >>> $ qemu-kvm -m 1G -cdrom lfs.iso
> >>> 
> >>> I was scanning the changelogs and read something about a
> >>> -no-kernel-irqchip. The man page doesn't say anything about it but will
> >>> try this one too..
> >> 
> >> Please try:
> >> 
> >> $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio
> >> 
> >> Then when it shows the bootloader, add "console=ttyS0" to the kernel 
> >> command line. That should give all the debugging output necessary.
> >> 
> >> 
> > 
> > Already done this one too (I've read it from your conversations with a
> > Peter guy if I'm not mistaken).
> > 
> > It just stops with no panic messages right after the mentioned checking
> > part, which made me dig after timers (bogomips calibration should be
> > next I believe). But I've gotten nowhere so far...
> > 
> > Also, there's no -no-kernel-irqchip parameter, must have been a typo for
> > -no-kvm-irqchip.
> > 
> > -- begin kernel messages
> >> Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
> >> 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
> >> BIOS-provided physical RAM map:
> >> BIOS-e820:  - 0009f400 (usable)
> >> BIOS-e820: 0009f400 - 000a (reserved)
> >> BIOS-e820: 000f - 0010 (reserved)
> >> BIOS-e820: 0010 - 3fffd000 (usable)
> >> BIOS-e820: 3fffd000 - 4000 (reserved)
> >> BIOS-e820: fffbc000 - 0001 (reserved)
> >> 127MB HIGHMEM available.
> >> 895MB LOWMEM available.
> >> found SMP MP-table at 000f8990
> >> DMI 2.4 present.
> >> Using APIC driver default
> >> ACPI: PM-Timer IO Port: 0xb008
> >> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> >> Processor #0 15:11 APIC version 20
> >> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> >> Processor #1 15:11 APIC version 20
> >> Overriding APIC driver with bigsmp
> >> ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
> >> IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> >> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> >> Enabling APIC mode:  Physflat.  Using 1 I/O APICs
> >> ACPI: HPET id: 0x8086a201 base: 0xfed0
> >> Using ACPI (MADT) for SMP configuration information
> >> Allocating PCI resources starting at 5000 (gap: 4000:bffbc000)
> >> Built 1 zonelists
> >> Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram 
> >> BOOT_IMAGE=k12_1009 console=ttyS0
> >> Enabling fast FPU save and restore... done.
> >> Enabling unmasked SIMD FPU exception support... done.
> >> Initializing CPU#0
> >> PID hash table entries: 4096 (order: 12, 65536 bytes)
> >> Console: colour VGA+ 80x25
> >> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
> >> 890k data, 200k init, 131064k highmem)
> >> Checking if this processor honours the WP bit even in supervisor mode... 
> >> Ok.
> 
> Interesting. Mind to check if you find a the vmlinux binary for that kernel 
> on the cd? Maybe it's hidden inside an rpm. Then you can use:
> 
> $ qemu-kvm -s -cdrom ...
> $ gdb  -ex 'target remote localhost:1234'
> 
> (gdb) bt
> 
> That should give us a clue on what's going wrong.
> 

Sure will do this. I'll update the list later this morning.

> Also, does the host's dmesg say anything?
> 

Nothing on the host's dmesg too. I've checked
{kernel,messages,syslog,everything}.log just to be safe but they're on
the clear also...

Meanwhile gotta sleep. Thanks for the

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alexander Graf 

On 15.09.2010, at 20:07, Alec Joseph Rivera wrote:

> On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
>> On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:
>> 
>>> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
 On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
 
> Hi all:
> 
> I'm Alec Joseph Rivera, from the Philippines and new on this list.
> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> bootup. It stops right after:
> 
> Checking if this processor honours the WP bit even in supervisor
> mode... Ok.
> 
> There's no more output after that. My invocation line is:
> 
> $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
 
 Your host is probably too new for this old guest. -cpu host directly 
 passes through this host cpu's identifiers on which the guest might choke. 
 Please try again without -cpu.
 
 
>>> 
>>> Tried without -cpu, still hangs after the WP bit checking...
>>> 
>>> $ qemu-kvm -m 1G -cdrom lfs.iso
>>> 
>>> I was scanning the changelogs and read something about a
>>> -no-kernel-irqchip. The man page doesn't say anything about it but will
>>> try this one too..
>> 
>> Please try:
>> 
>> $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio
>> 
>> Then when it shows the bootloader, add "console=ttyS0" to the kernel command 
>> line. That should give all the debugging output necessary.
>> 
>> 
> 
> Already done this one too (I've read it from your conversations with a
> Peter guy if I'm not mistaken).
> 
> It just stops with no panic messages right after the mentioned checking
> part, which made me dig after timers (bogomips calibration should be
> next I believe). But I've gotten nowhere so far...
> 
> Also, there's no -no-kernel-irqchip parameter, must have been a typo for
> -no-kvm-irqchip.
> 
> -- begin kernel messages
>> Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
>> 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
>> BIOS-provided physical RAM map:
>> BIOS-e820:  - 0009f400 (usable)
>> BIOS-e820: 0009f400 - 000a (reserved)
>> BIOS-e820: 000f - 0010 (reserved)
>> BIOS-e820: 0010 - 3fffd000 (usable)
>> BIOS-e820: 3fffd000 - 4000 (reserved)
>> BIOS-e820: fffbc000 - 0001 (reserved)
>> 127MB HIGHMEM available.
>> 895MB LOWMEM available.
>> found SMP MP-table at 000f8990
>> DMI 2.4 present.
>> Using APIC driver default
>> ACPI: PM-Timer IO Port: 0xb008
>> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> Processor #0 15:11 APIC version 20
>> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
>> Processor #1 15:11 APIC version 20
>> Overriding APIC driver with bigsmp
>> ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
>> IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
>> Enabling APIC mode:  Physflat.  Using 1 I/O APICs
>> ACPI: HPET id: 0x8086a201 base: 0xfed0
>> Using ACPI (MADT) for SMP configuration information
>> Allocating PCI resources starting at 5000 (gap: 4000:bffbc000)
>> Built 1 zonelists
>> Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram 
>> BOOT_IMAGE=k12_1009 console=ttyS0
>> Enabling fast FPU save and restore... done.
>> Enabling unmasked SIMD FPU exception support... done.
>> Initializing CPU#0
>> PID hash table entries: 4096 (order: 12, 65536 bytes)
>> Console: colour VGA+ 80x25
>> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 
>> 890k data, 200k init, 131064k highmem)
>> Checking if this processor honours the WP bit even in supervisor mode... Ok.

Interesting. Mind to check if you find a the vmlinux binary for that kernel on 
the cd? Maybe it's hidden inside an rpm. Then you can use:

$ qemu-kvm -s -cdrom ...
$ gdb  -ex 'target remote localhost:1234'

(gdb) bt

That should give us a clue on what's going wrong.

Also, does the host's dmesg say anything?

Alex

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alec Joseph Rivera 
On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
> On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:
> 
> > On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
> >> On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
> >> 
> >>> Hi all:
> >>> 
> >>> I'm Alec Joseph Rivera, from the Philippines and new on this list.
> >>> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> >>> bootup. It stops right after:
> >>> 
> >>> Checking if this processor honours the WP bit even in supervisor
> >>> mode... Ok.
> >>> 
> >>> There's no more output after that. My invocation line is:
> >>> 
> >>> $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
> >> 
> >> Your host is probably too new for this old guest. -cpu host directly 
> >> passes through this host cpu's identifiers on which the guest might choke. 
> >> Please try again without -cpu.
> >> 
> >> 
> > 
> > Tried without -cpu, still hangs after the WP bit checking...
> > 
> > $ qemu-kvm -m 1G -cdrom lfs.iso
> > 
> > I was scanning the changelogs and read something about a
> > -no-kernel-irqchip. The man page doesn't say anything about it but will
> > try this one too..
> 
> Please try:
> 
> $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio
> 
> Then when it shows the bootloader, add "console=ttyS0" to the kernel command 
> line. That should give all the debugging output necessary.
> 
> 

Already done this one too (I've read it from your conversations with a
Peter guy if I'm not mistaken).

It just stops with no panic messages right after the mentioned checking
part, which made me dig after timers (bogomips calibration should be
next I believe). But I've gotten nowhere so far...

Also, there's no -no-kernel-irqchip parameter, must have been a typo for
-no-kvm-irqchip.

-- begin kernel messages
> Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
> 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
> BIOS-provided physical RAM map:
>  BIOS-e820:  - 0009f400 (usable)
>  BIOS-e820: 0009f400 - 000a (reserved)
>  BIOS-e820: 000f - 0010 (reserved)
>  BIOS-e820: 0010 - 3fffd000 (usable)
>  BIOS-e820: 3fffd000 - 4000 (reserved)
>  BIOS-e820: fffbc000 - 0001 (reserved)
> 127MB HIGHMEM available.
> 895MB LOWMEM available.
> found SMP MP-table at 000f8990
> DMI 2.4 present.
> Using APIC driver default
> ACPI: PM-Timer IO Port: 0xb008
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 15:11 APIC version 20
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> Processor #1 15:11 APIC version 20
> Overriding APIC driver with bigsmp
> ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
> IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> Enabling APIC mode:  Physflat.  Using 1 I/O APICs
> ACPI: HPET id: 0x8086a201 base: 0xfed0
> Using ACPI (MADT) for SMP configuration information
> Allocating PCI resources starting at 5000 (gap: 4000:bffbc000)
> Built 1 zonelists
> Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram 
> BOOT_IMAGE=k12_1009 console=ttyS0
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 65536 bytes)
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 890k 
> data, 200k init, 131064k highmem)
> Checking if this processor honours the WP bit even in supervisor mode... Ok.
-- end

> Alex
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera


Linux version 2.6.16.54-0.2.5-bigsmp (ge...@buildhost) (gcc version 4.1.2 
20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f400 (usable)
 BIOS-e820: 0009f400 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 3fffd000 (usable)
 BIOS-e820: 3fffd000 - 4000 (reserved)
 BIOS-e820: fffbc000 - 0001 (reserved)
127MB HIGHMEM available.
895MB LOWMEM available.
found SMP MP-table at 000f8990
DMI 2.4 present.
Using APIC driver default
ACPI: PM-Timer IO Port: 0xb008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:11 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alexander Graf 

On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:

> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
>> On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
>> 
>>> Hi all:
>>> 
>>> I'm Alec Joseph Rivera, from the Philippines and new on this list.
>>> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
>>> bootup. It stops right after:
>>> 
>>> Checking if this processor honours the WP bit even in supervisor
>>> mode... Ok.
>>> 
>>> There's no more output after that. My invocation line is:
>>> 
>>> $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
>> 
>> Your host is probably too new for this old guest. -cpu host directly passes 
>> through this host cpu's identifiers on which the guest might choke. Please 
>> try again without -cpu.
>> 
>> 
> 
> Tried without -cpu, still hangs after the WP bit checking...
> 
> $ qemu-kvm -m 1G -cdrom lfs.iso
> 
> I was scanning the changelogs and read something about a
> -no-kernel-irqchip. The man page doesn't say anything about it but will
> try this one too..

Please try:

$ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio

Then when it shows the bootloader, add "console=ttyS0" to the kernel command 
line. That should give all the debugging output necessary.


Alex

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alec Joseph Rivera 
On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
> On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
> 
> > Hi all:
> > 
> > I'm Alec Joseph Rivera, from the Philippines and new on this list.
> > Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> > bootup. It stops right after:
> > 
> >  Checking if this processor honours the WP bit even in supervisor
> > mode... Ok.
> > 
> > There's no more output after that. My invocation line is:
> > 
> >  $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
> 
> Your host is probably too new for this old guest. -cpu host directly passes 
> through this host cpu's identifiers on which the guest might choke. Please 
> try again without -cpu.
> 
> 

Tried without -cpu, still hangs after the WP bit checking...

$ qemu-kvm -m 1G -cdrom lfs.iso

I was scanning the changelogs and read something about a
-no-kernel-irqchip. The man page doesn't say anything about it but will
try this one too..


> Alex
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alexander Graf 

On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:

> Hi all:
> 
> I'm Alec Joseph Rivera, from the Philippines and new on this list.
> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
> bootup. It stops right after:
> 
>  Checking if this processor honours the WP bit even in supervisor
> mode... Ok.
> 
> There's no more output after that. My invocation line is:
> 
>  $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso

Your host is probably too new for this old guest. -cpu host directly passes 
through this host cpu's identifiers on which the guest might choke. Please try 
again without -cpu.


Alex

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

2.6.16 Guest Hangs on Boot

2010-09-15 Thread Alec Joseph Rivera 
Hi all:

I'm Alec Joseph Rivera, from the Philippines and new on this list.
Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
bootup. It stops right after:

  Checking if this processor honours the WP bit even in supervisor
mode... Ok.

There's no more output after that. My invocation line is:

  $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso

Adding -no-acpi allows the bootup to progress for a little bit then
hangs again with no further error messages after:

  PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0
  PCI: Using configuration type 1

I tried adding kernel parameters like noapic, nolapic and pci=xxx but to
no avail. Adding -no-kvm allows somewhat normal operations but I/O
breakdowns after awhile. Kernel logs say something about dma timer
expiry. nolapic_timer on the kernel commandline seems to fix it. But no
one likes to settle with -no-kvm right :-)

I tried -no-kvm-irqchip and -no-kvm-pit separately, then together, but
they also don't have any effect. Still hangs after the WP bit checking
part.

I made some digging and found out that Foundations is actually based on
SLES 10 and uses a rather old 2.6.16 kernel. On kvm's changelog, kvm-47
already had added support for these kernels. Might this be a regression?

My host kernel is 2.6.35 and qemu-kvm is 0.12.5. modinfo kvm gives
nothing about the kvm version though..

Anyone got some suggestions I could try? BTW, kernel rebuilding is not
an option on Foundations :-(

Thanks.


Cheese!
Agi


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera



--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html