Hello. This is just an initial/preliminary heads-up, maybe mis-directed, about a possible issue. I upgraded 2 machines today to 3.10.25, and both shows some.. strangeness within linux guests, which are also running 3.10.25. Revering to 3.10.24 in guests (compiled by the same compiler with the same options) or using older qemu/kvm (running with 1.7 now) fixes it. All guests are using virtio-net and virtio-blk. On one machine (prod), one guest (also prod) loads okay, but the networking is not functioning: no packets are received by the guest. I weren't able to debug this further at this time, so reverted back to an older qemu/kvm (1.1). On another machine (my home workstation where I can experiment), the same combination (3.10.25 on host & guest and qemu 1.7) shows rather unstable behavour: about every 1/2 boot it stalls somewhere at the initial boot, either after initializing PNP, or initializing networking, or sometimes after initializing virtio, and the rest 1/2 it boots okay. When it stalls, it consumes no CPU, qemu process is responsive, the guest just does nothing. Like this: ... NET: Registering protocol family 2 TCP: established hash table entries: 8192 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP: reno registered [at this point it hanged] (after this it normally registers UDP hash tables and other net stuff) I'm not sure yet what's going on. I understand that there are no guest-related changes in 3.10.25 (compared with .24), so there should be something else. The fact that it stalls randomly suggests there's some uninitialized value somewhere. I'll try to debug it further. Just a heads-up for now. Thanks, /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
