lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <466BED18.5040708@qumranet.com>
Date:	Sun, 10 Jun 2007 15:22:48 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Luca <kronos.it@...il.com>
CC:	kvm-devel@...ts.sf.net, linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [BUG] Oops with KVM-27

Luca wrote:
> On 6/5/07, Avi Kivity <avi@...ranet.com> wrote:
>> Luca Tettamanti wrote:
>> > Il Mon, Jun 04, 2007 at 11:51:10PM +0300, Avi Kivity ha scritto:
>> >
>> >>> While doing repeated tests with the installer I ran into another
>> >>> (unrelated) problem. Sometimes the guest kernel hangs at boot at:
>> >>>
>> >>> NET: Registered protocol family 2
>> >>>
>> >>> with any kind of networking options (except for -net none, which 
>> works).
>> >>> With -no-kvm it boots with any networking option.
>> >>>
>> >>>
>> >>>
>> >> Can you try to pin the guest on a single core with taskset:
>> >>
>> >>    taskset 1 qemu ...
>> >>
>> >
>> > Doesn't help. What works is 'nolapic', i.e. disabling the local 
>> APIC on
>> > the guest kernel.
>> > I've also tried disabling TSC (notsc) and forcing PIT as the 
>> clocksource
>> > (clocksouce=pit clock=pit); neither of them helped.
>> >
>> >
>>
>> Is this a regression relative to a previous kvm version?
>
> Hello,
> sorry for the delay, I was having troubles compiling older KVMs with a
> recent kernel...
> The last version that works is kvm-21; starting from kvm-22 the VM
> hangs during network initialization (now always, but pretty often).
> This only occurs when the guest is Fedora7 setup ISO. The regular boot
> (i.e. from the hd) seems unaffected.

I've managed to reproduce this on kvm-21 (it takes many boots for this 
to happen, but it does eventually).

-- 
error compiling committee.c: too many arguments to function

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ