From: Jes S. <je...@sg...> - 2008-03-19 10:30:38
|
Zhang, Xiantao wrote: > Since I don't know how old the Qemu you are using, I can't say yes or > no. Generally, we need to use the latest source to build, but seems it > is broken for ia64 due to recent merge with Qemu upstream. > > BTW, Do you see any error info in the shell ? Are you sure the kvm > guest is created or just run qemu with kvm support? You can check it > with dmesg in host. > If a new guest is created, it will generate some debug info in kernel > log. :) > > Maybe you can try 5ffc6784843600e72d78dd5609e0f7861a3f0e2d, it should be > workable . Hi Xiantao, I get this in the dmesg log: device tap0 entered promiscuous mode kvm:vm data base address:0xe000006059000000 kvm: vcpu:e000006059d00000,ivt: 0xd000000000018000 I presume KVM is doing something :-) My QEMU isn't that old, but I'll try and revert to that patch. Thanks, Jes |