* Avi Kivity <[EMAIL PROTECTED]> [071023 10:21]:
> Thanks, that will be most helpful. If userspace won't compile against
> some intermediate version, let me know the commit hash and I'll add a fixup.
A bisect didn't find anything between 2.6.22 and 2.6.23. Which made me
very confused. I think,
* Avi Kivity <[EMAIL PROTECTED]> [071022 09:42]:
> I'm not sure that's useful -- very little changed after 2.6.23-rc1 (10
> patches).
>
> There were 92 kvm patches in 2.6.23, so a bisect should take about a
> week worst case.
I'll get started tonight.
-Bart
--
* Avi Kivity <[EMAIL PROTECTED]> [071021 07:23]:
> Does 2.6.23 hang immediately? If so, these may be two separate problems
> and it's worth bisecting to find out what's the fix in 2.6.24-rc.
>
> Of course we'll have to address the later hang as well.
Avi,
it does not hang immediately. It seem
* Bart Trojanowski <[EMAIL PROTECTED]> [071019 20:03]:
> * Bart Trojanowski <[EMAIL PROTECTED]> [071019 17:00]:
>
> >
> > Once the system is booted, I attached using vnc, then I ssh in and ran
> > 'svn update'... and the host machine froze.
> &g
* Bart Trojanowski <[EMAIL PROTECTED]> [071019 17:00]:
>
> Once the system is booted, I attached using vnc, then I ssh in and ran
> 'svn update'... and the host machine froze.
>
> The last messages I on my serial console are:
>
> kvm: unhandled rdmsr: 0x4
I am running 2.6.23.1 with kvm built from that tree as a module. My
system is running Debian/testing on a Tyan board with two dual-core
Opteron 2216 processors; each socket has 4G of RAM. I have attached the
serial console dump including a bunch of output from SysRq (gzipped,
because it was 300k
