Zhang, Jingke wrote: > Hi Xiantao, > The Guest network enabling patch has not been checked in by Avi. > So we can not get network in VTI guest. We appended the patch and > gave a verification for the other four P1 bugs. They are still > existing in the latest commit: kernel-ia64: > ec7c27790e75397e1e91488a18beadc60926e818 > kvm-userspace: 619ca34310a8968b6939fa6aba5b85a16b20315e > > Bugs info: > ==================== > [KVM-IPF] guest domain can not boot up network > http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=73 Per avi comment, he want this patch into qemu first, it will take a while. > > 1.[KVM-IPF] FAIL to boot up Windows-2008server guest > http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=85 > 2.[KVM-IPF] IA64-KVM Guest will crash at restore > http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=95 > 3.[KVM-IPF] Guest can not be booted with > 2 vcpus > http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=96 > 4.[KVM-IPF] Can not boot up guest with 4G memory > http://otc-qa.sh.intel.com/kvm/bugzilla/show_bug.cgi?id=97 > ==================== > > BTW Xiantao, could you please have a look at 3 trivial issues > which does not happen on x86 arch. [issue1] "qemu-system-ia64 -hda > ***.img" will report error "Unknown network device: user". [issue2] > the default memory (128M) by qemu-system-ia64 can not boot up VTI > guest, What's minimal memory request for native RHEL5 on ipf? Maybe it is larger than 128M :-) >for it will reserve 100M. [issue3] W We need find out what these memory is used for. Anthony >hen we type booting > command in PUTTY, it will complain "Could not initialize SDL > -exiting". (only for ia64 side) > > > Thanks, > Zhang Jingke -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
