Dong, Eddie wrote: >> BTW, I downloaded KVM-36 with REHL5U 32e guest, reboot doesn't work >> either. But if I use no-kvm option, it can. >> So I would like to know which release is the latest known working >> tree for "reboot". >> >> > More update: > Using today's master, without any patch, reboot works!!! > It could be explained that at reboot time, the eflag.IF is > cleared, > so no matter how PIC/APIC beahivors at that stage, it doesn't matter. > Later on, guest will reset those chips and then keep forwarding... > Some other patches fixed the issue from KVM-36, or anybody has more > finding? > > It is good that I don't need to push the kernel device reset > patch out that soon, > but we still need to do so for a graceful reset especially kernel > devices need to be reseted since >
Yes, that patch is needed. I thought of another way to do it: have a single vm ioctl reset, which can set a reset bit in all vcpu->requests and then kick the vcpus. When the vcpus execute, they'll check the bit and reset the cpu and lapic then; no locking needed. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
