Thanks! I get it!

Thanks again for your help!

2012/3/8 Eric Blake <eblake@redhat.com>
On 03/08/2012 02:04 AM, Osier Yang wrote:
> On 03/08/2012 11:47 AM, suyi wang wrote:
>>
>> Hi all:
>>        My OS is now Fedora16 , and the spice server is installed on it
>> by rpms. Then I run 'qemu-kvm -hda /root/vaddsoft.img -m 512 -vga qxl
>> -spice port=5930,disable-ticketing' , I want to find out where is the
>> libvirt.xml for the command .  Well , I mean that the libvirt.xml is
>> genrated automatically,  not by myself manually.
>>       Wish your help! Thanks a lot!
>
> If you start a guest with qemu command line directly, there
> is no libvirt XML for it, libvirt doesn't try to manage
> guest which is not created through libvirt API.

However, you  _can_ teach libvirt about certain guests started directly
by qemu; the 'virsh qemu-attach' command can attach to guests that were
properly started with a socket monitor.

>
> For a guest created through libvirt, and it's persistent,
> the persistent XML is stored in /etc/libvirt/qemu/, and
> the running state XML is in /var/run/libvirt/qemu/, and

Note that these files are to be treated as read-only.  If you want to
modify the guest, you must not edit these files, but instead should use
commands like 'virsh edit' for the persistent definition, and hotplug
actions like 'virsh add-device' for the live definition.

> you would see the generated qemu command line by libvirt
> either by
>
> # ps -ef | grep qemu
>
> # cat /var/log/libvirt/qemu/$guest.log

--
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org




--
Yours.
suyi