Anthony Liguori wrote: >>> >>> That kills the -no-kvm switch, which allows a single binary to be >>> used both with and without kvm. Or do you think both >>> target-i386+kvm and target-kvm ought to be kept? >>> >>> >> >> I meant here: target-i386 (with kvm support) and target-i386-kvm. > > target-i386 is an architecture. It can currently generate > i386-softmmu, i386-user, x86_64-softmmu, x86_64-user. We're simply > adding the ability to generate i386-kvm and x86_64-kvm. I'd like to > find another name. > > I still want to be able to support kvm/qemu in the normal i386-softmmu.
Thanks, that clears it up. I'll apply the patch. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
