HI Cole, I have attached a copy of my virt-manager.log file. hope you find it useful. You comments on KVM seem very inspiring, and im already set to give KVM a shot. Before that i would like to know a few things? -> What is faster Xen or KVM? I am aware that KVM particularly depends on the processor to support VT, which my processor does (Xeon 5000 Series). -> Will KVM allow me to use multiprocessor support for Windows XP -> Does KVM support paravirtualization? or does it matter at all? -> Is the Migration of Xen fully virtualized guest to KVM possible? -> Can i use virt-manager to manager KVM guests? I am having a good feeling about KVM. Please help me decide. -- BTW, just can't wait to upgrade my system to fedora 10. really excited about plymouth and the other speed ups in the fedora system. hoping that KDE 4 does not dissapoint me, in which case ill be sticking with fedora 8. Thanks to all you Redhat guys (an the Community of course) for Fedora 10. Regards ~Sameer <div class="gmail_quote">On Wed, Nov 26, 2008 at 8:00 PM, Cole Robinson <<a href="mailto:crobinso@redhat.com">crobinso@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Sameer Naik wrote: > Hello Cole. > > I did try to adding acpi and apic to the domain cofiguration file > (post-install), as you suggested. > But after applying these changes, Virt-Manager would display a message > (saying something like function requires an argument). As i have faced this > error earlier (many times), i just deleted the cdrom device from the machine > and then the domain was booting. > However these changes did not make any difference to my problems (still high > CPU load, no poweroff on shutdown). > </div>Do you have a copy of this error? Check ~/.virt-manager/virt-manager.log <div class="Ih2E3d"> > So i created a new xen guest by manually creating the configuration file > with apic and apic enabled and created the domain using the "xm create" > command. Then during the start of the installation i pressed F5 , and > selected "ACPI Multiprocessor" and continued installation. After this > everything is working great! All the problems have gone. > > Following is my feedback on virt-manager: > > I have been using virt-manager for around 2 years now, and alway shyed away > from the manual configuration. But during my experience of using > virt-manager i have seen quite a lot of issues, which would require me to > restart the xend service. > For Example: If i shutdowm a windows/linux guest, and then try to power it > on again, virt-manager will say "error posting message" or something of that > sort. As a result of this i would need to restart the xend service to power > on the domain again (and for some reason i always thought this was an issue > with xend, until now). I have been following this routine for a long time > now. Now i think the "xm" command is what i need to consider while creating > a virtual machine and basically use virt-manager to handle the hot-plugging > of devices, cloning domains, etc. > As it is ovirt needs fedora 9, so haven't go to test that yet. > I'm hoping to see a better,stable version of virt-manager > </div>The truth is, this has _nothing_ to do with virt-manager. virt-manager does nearly all it's work through libvirt, which talks to xen. All those errors you listed are coming straight from xen, and are legitimate xen bugs. xen has been a maintenance nightmare. I know that doesn't help any, but it's the truth. If you ever get the opportunity to move to a kvm based setup, you'll find things work _much_ better in fedora land (and you'll also be able to use newer distros F9 or F10). Thanks, Cole </blockquote></div>