Re: [libvirt] [libvirt-users] Regarding SPICE

2010-03-04 Thread anuj rampal
Hi,

Thanks a lot for the reply.

Is it going to be there in the future?

And i wanted to confirm one more thing...
KVM on RHEL 5.4 supports SPICE through libvirt?
Because there were some patches regarding " Implement RHEL-5.4 support for
SPICE graphics"

Regards
Anuj


On Thu, Mar 4, 2010 at 3:31 PM, Daniel P. Berrange wrote:

> On Thu, Mar 04, 2010 at 12:07:06PM +0530, anuj rampal wrote:
> > Hi,
> >
> > I have set up KVM on FC12.
> > I was wondering if its possible to Display the VM using spice + libvirt?
>
> KVM in Fedora 12 does not support SPICE, since it is not merged in the
> upstream repository.
>
> Daniel
> --
> |: Red Hat, Engineering, London-o-
> http://people.redhat.com/berrange/ :|
> |: http://libvirt.org -o- http://virt-manager.org -o-
> http://deltacloud.org :|
> |: http://autobuild.org-o-
> http://search.cpan.org/~danberr/ <http://search.cpan.org/%7Edanberr/> :|
> |: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
> :|
>
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Regarding SPICE

2010-03-03 Thread anuj rampal
Hi,

I have set up KVM on FC12.
I was wondering if its possible to Display the VM using spice + libvirt?

As in, if I can define my domain with graphics like:



   or



Thanks & Regards
Anuj
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Check out my photos on Facebook

2010-02-18 Thread Anuj Rampal
Hi Libvir-list,

I set up a Facebook profile where I can post my pictures, videos and events and 
I want to add you as a friend so you can see it. First, you need to join 
Facebook! Once you join, you can also create your own profile.

Thanks,
Anuj

To sign up for Facebook, follow the link below:
http://www.facebook.com/p.php?i=10789786934&k=Z6E3Y5PS3YVAVA1JPB63QTWRU31JYTVNUWFWGK4FUR&r



Already have an account? Add this email address to your account 
http://www.facebook.com/n/?merge_accounts.php&e=libvir-l...@redhat.com&c=1f4bc10bdb10e47dccb429803b117bf5.libvir-l...@redhat.com
 was invited to join Facebook by Anuj Rampal. If you do not wish to receive 
this type of email from Facebook in the future, please click on the link below 
to unsubscribe.
http://www.facebook.com/o.php?k=07f024&u=10616939699&mid=1e71081G5af3354000b3G0G8
Facebook's offices are located at 1601 S. California Ave., Palo Alto, CA 94304.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Problem with libvirt-0.7.5 windows port

2010-01-13 Thread anuj rampal
Hi,

I'm trying to cross compile the libvirt-0.7.5 for windows.

This is the error I'm getting:

# make
make  all-recursive
make[1]: Entering directory `/root/libvirt-0.7.5'
Making all in gnulib/lib
make[2]: Entering directory `/root/libvirt-0.7.5/gnulib/lib'

[...]

Making all in tools
make[2]: Entering directory `/root/libvirt-0.7.5/tools'
make  all-am
make[3]: Entering directory `/root/libvirt-0.7.5/tools'
  CC virsh-console.o
  CC virsh-virsh.o
  CCLD   virsh.exe
../src/.libs/libvirt.a: could not read symbols: Archive has no index; run
ranlib to add one
collect2: ld returned 1 exit status
make[3]: *** [virsh.exe] Error 1
make[3]: Leaving directory `/root/libvirt-0.7.5/tools'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/libvirt-0.7.5/tools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/libvirt-0.7.5'
make: *** [all] Error 2


Does any1 has any idea.

Thanks in advance.

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Current cpu and memory usage for Host and Domains

2009-12-17 Thread anuj rampal
Hi,

Is there a way to get the Current CPU and Memory usage of the Host machine
and the Guest Domains..??

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


[libvirt] Re: problem connecting to vbox

2009-12-15 Thread anuj rampal
I installed libvirt-0.7.4 and now its working fine.

Regards
Auj

On Tue, Dec 15, 2009 at 3:04 PM, anuj rampal  wrote:

> Hi,
>
> I have installed VBOX 3.0.12 on fc12 which is running libvirt-0.7.1.
> Now when i try to connect using virsh using uri "virsh -c
> vbox+tcp:///system"
>
> this is the error i get:
>
> error: internal error unable to initialize VirtualBox driver API
> error: failed to connect to the hypervisor
>
> But it connects successfully with this ur:
> "virsh -c vbox:///system"
>
> i have also qemu installed on the same machine and connects successfully
> with uri "virsh -c qemu+tcp:///system"
>
> Libvirt is listening on tcp port:16509
>
> any idea what am i doing wrong?
>
> Here is a detailed message:
>
> LIBVIRT_DEBUG=1 virsh -c vbox+tcp:///system
> 11:10:45.469: debug : virInitialize:279 : register drivers
> 11:10:45.495: debug : virRegisterDriver:776 : registering Test as driver 0
> 11:10:45.495: debug : virRegisterNetworkDriver:614 : registering Test as
> network driver 0
> 11:10:45.495: debug : virRegisterInterfaceDriver:645 : registering Test as
> interface driver 0
> 11:10:45.495: debug : virRegisterStorageDriver:676 : registering Test as
> storage driver 0
> 11:10:45.495: debug : virRegisterDeviceMonitor:707 : registering Test as
> device driver 0
> 11:10:45.495: debug : virRegisterSecretDriver:738 : registering Test as
> secret driver 0
> 11:10:45.496: debug : virRegisterDriver:776 : registering Xen as driver 1
> 11:10:45.496: debug : virRegisterDriver:776 : registering OPENVZ as driver
> 2
> 11:10:45.496: debug : virRegisterDriver:776 : registering PHYP as driver 3
> 11:10:45.506: debug : vboxRegister:80 : VBoxCGlueInit found API version:
> 3.0.12 (312)
> 11:10:45.506: debug : vboxRegister:92 : VirtualBox API version: 3.0
> 11:10:45.506: debug : virRegisterDriver:776 : registering VBOX as driver 4
> 11:10:45.506: debug : virRegisterNetworkDriver:614 : registering VBOX as
> network driver 1
> 11:10:45.506: debug : virRegisterStorageDriver:676 : registering VBOX as
> storage driver 1
> 11:10:45.506: debug : virRegisterDriver:776 : registering ESX as driver 5
> 11:10:45.506: debug : virRegisterDriver:776 : registering remote as driver
> 6
> 11:10:45.506: debug : virRegisterNetworkDriver:614 : registering remote as
> network driver 2
> 11:10:45.506: debug : virRegisterInterfaceDriver:645 : registering remote
> as interface driver 1
> 11:10:45.506: debug : virRegisterStorageDriver:676 : registering remote as
> storage driver 2
> 11:10:45.506: debug : virRegisterDeviceMonitor:707 : registering remote as
> device driver 1
> 11:10:45.506: debug : virRegisterSecretDriver:738 : registering remote as
> secret driver 1
> 11:10:45.506: debug : virConnectOpenAuth:1273 : name=vbox+tcp:///system,
> auth=0x43d940, flags=0
> 11:10:45.506: debug : do_open:1042 : name "vbox+tcp:///system" to URI
> components:
>   scheme vbox+tcp
>   opaque (null)
>   authority (null)
>   server (null)
>   user (null)
>   port 0
>   path /system
>
> 11:10:45.506: debug : do_open:1052 : trying driver 0 (Test) ...
> 11:10:45.506: debug : do_open:1058 : driver 0 Test returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 1 (Xen) ...
> 11:10:45.506: debug : do_open:1058 : driver 1 Xen returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 2 (OPENVZ) ...
> 11:10:45.506: debug : do_open:1058 : driver 2 OPENVZ returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 3 (PHYP) ...
> 11:10:45.506: debug : do_open:1058 : driver 3 PHYP returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 4 (VBOX) ...
> 11:10:45.506: debug : do_open:1058 : driver 4 VBOX returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 5 (ESX) ...
> 11:10:45.506: debug : do_open:1058 : driver 5 ESX returned DECLINED
> 11:10:45.506: debug : do_open:1052 : trying driver 6 (remote) ...
> 11:10:45.506: debug : doRemoteOpen:535 : proceeding with name =
> vbox:///system
> 11:10:45.508: debug : remoteIO:7421 : Do proc=66 serial=0 length=28
> wait=(nil)
> 11:10:45.508: debug : remoteIO:7483 : We have the buck 66 0xb75df008
> 0xb75df008
> 11:10:45.509: debug : remoteIODecodeMessageLength:7032 : Got length, now
> need 64 total (60 more)
> 11:10:45.509: debug : remoteIOEventLoop:7347 : Giving up the buck 66
> 0xb75df008 (nil)
> 11:10:45.509: debug : remoteIO:7514 : All done with our call 66 (nil)
> 0xb75df008
> 11:10:45.509: debug : remoteIO:7421 : Do proc=1 serial=1 length=56
> wait=(nil)
> 11:10:45.509: debug : remoteIO:7483 : We have the buck 1 0x9fb2ea8
> 0x9fb2ea8
> 11:10:45.510: debug : remoteIODecodeMessageLength:7032 : Got length, now

[libvirt] problem connecting to vbox

2009-12-15 Thread anuj rampal
Hi,

I have installed VBOX 3.0.12 on fc12 which is running libvirt-0.7.1.
Now when i try to connect using virsh using uri "virsh -c
vbox+tcp:///system"

this is the error i get:

error: internal error unable to initialize VirtualBox driver API
error: failed to connect to the hypervisor

But it connects successfully with this ur:
"virsh -c vbox:///system"

i have also qemu installed on the same machine and connects successfully
with uri "virsh -c qemu+tcp:///system"

Libvirt is listening on tcp port:16509

any idea what am i doing wrong?

Here is a detailed message:

LIBVIRT_DEBUG=1 virsh -c vbox+tcp:///system
11:10:45.469: debug : virInitialize:279 : register drivers
11:10:45.495: debug : virRegisterDriver:776 : registering Test as driver 0
11:10:45.495: debug : virRegisterNetworkDriver:614 : registering Test as
network driver 0
11:10:45.495: debug : virRegisterInterfaceDriver:645 : registering Test as
interface driver 0
11:10:45.495: debug : virRegisterStorageDriver:676 : registering Test as
storage driver 0
11:10:45.495: debug : virRegisterDeviceMonitor:707 : registering Test as
device driver 0
11:10:45.495: debug : virRegisterSecretDriver:738 : registering Test as
secret driver 0
11:10:45.496: debug : virRegisterDriver:776 : registering Xen as driver 1
11:10:45.496: debug : virRegisterDriver:776 : registering OPENVZ as driver 2
11:10:45.496: debug : virRegisterDriver:776 : registering PHYP as driver 3
11:10:45.506: debug : vboxRegister:80 : VBoxCGlueInit found API version:
3.0.12 (312)
11:10:45.506: debug : vboxRegister:92 : VirtualBox API version: 3.0
11:10:45.506: debug : virRegisterDriver:776 : registering VBOX as driver 4
11:10:45.506: debug : virRegisterNetworkDriver:614 : registering VBOX as
network driver 1
11:10:45.506: debug : virRegisterStorageDriver:676 : registering VBOX as
storage driver 1
11:10:45.506: debug : virRegisterDriver:776 : registering ESX as driver 5
11:10:45.506: debug : virRegisterDriver:776 : registering remote as driver 6
11:10:45.506: debug : virRegisterNetworkDriver:614 : registering remote as
network driver 2
11:10:45.506: debug : virRegisterInterfaceDriver:645 : registering remote as
interface driver 1
11:10:45.506: debug : virRegisterStorageDriver:676 : registering remote as
storage driver 2
11:10:45.506: debug : virRegisterDeviceMonitor:707 : registering remote as
device driver 1
11:10:45.506: debug : virRegisterSecretDriver:738 : registering remote as
secret driver 1
11:10:45.506: debug : virConnectOpenAuth:1273 : name=vbox+tcp:///system,
auth=0x43d940, flags=0
11:10:45.506: debug : do_open:1042 : name "vbox+tcp:///system" to URI
components:
  scheme vbox+tcp
  opaque (null)
  authority (null)
  server (null)
  user (null)
  port 0
  path /system

11:10:45.506: debug : do_open:1052 : trying driver 0 (Test) ...
11:10:45.506: debug : do_open:1058 : driver 0 Test returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 1 (Xen) ...
11:10:45.506: debug : do_open:1058 : driver 1 Xen returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 2 (OPENVZ) ...
11:10:45.506: debug : do_open:1058 : driver 2 OPENVZ returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 3 (PHYP) ...
11:10:45.506: debug : do_open:1058 : driver 3 PHYP returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 4 (VBOX) ...
11:10:45.506: debug : do_open:1058 : driver 4 VBOX returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 5 (ESX) ...
11:10:45.506: debug : do_open:1058 : driver 5 ESX returned DECLINED
11:10:45.506: debug : do_open:1052 : trying driver 6 (remote) ...
11:10:45.506: debug : doRemoteOpen:535 : proceeding with name =
vbox:///system
11:10:45.508: debug : remoteIO:7421 : Do proc=66 serial=0 length=28
wait=(nil)
11:10:45.508: debug : remoteIO:7483 : We have the buck 66 0xb75df008
0xb75df008
11:10:45.509: debug : remoteIODecodeMessageLength:7032 : Got length, now
need 64 total (60 more)
11:10:45.509: debug : remoteIOEventLoop:7347 : Giving up the buck 66
0xb75df008 (nil)
11:10:45.509: debug : remoteIO:7514 : All done with our call 66 (nil)
0xb75df008
11:10:45.509: debug : remoteIO:7421 : Do proc=1 serial=1 length=56
wait=(nil)
11:10:45.509: debug : remoteIO:7483 : We have the buck 1 0x9fb2ea8 0x9fb2ea8
11:10:45.510: debug : remoteIODecodeMessageLength:7032 : Got length, now
need 208 total (204 more)
11:10:45.510: debug : remoteIOEventLoop:7347 : Giving up the buck 1
0x9fb2ea8 (nil)
11:10:45.510: debug : remoteIO:7514 : All done with our call 1 (nil)
0x9fb2ea8
11:10:45.510: debug : do_open:1058 : driver 6 remote returned ERROR
11:10:45.510: debug : virUnrefConnect:257 : unref connection 0x9fb0b30 1
11:10:45.510: debug : virReleaseConnect:214 : release connection 0x9fb0b30
error: internal error unable to initialize VirtualBox driver API
error: failed to connect to the hypervisor


Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


[libvirt] Having some issue with : virConnectRef

2009-12-13 Thread anuj rampal
Hi,

Im trying to call libvirt functions from a widows machine.

The client version i'm using is 0.6.1.

My application is a multi-Threaded application.

This is the way my application works:

1. I connect to Libvirt using "virConnectOpen". (this done only once when my
application starts).
2. For funther interaction with libvirt i just call "virConnectRef" and then
i call some other function like "virNodeGetInfo".
3. Then i call "virConnectClose".

Now my understanding is for every "virConnectRef" call there has to be a
corrosponding "virConnectClose".

In my application call to number of calls to "virConnectClose" is always
equal to "virConnectRef".
and "virConnectClose" corrosponding to "virConnectOpen" is called when the
application is closed.
So connection to libvirt should always be there till the time my application
is running.

But what is happening is, even if i call "virConnectRef" twice, a single
call to "virConnectClose" closes the connection with libvirt.

Is there anything that im doing wrong here...??

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


[libvirt] Regarding connecting to libvirt from windows

2009-10-06 Thread anuj rampal
Hi,

I can connect to libvirt over TCP/IP from windows and call all the
functions.

what i want is to do some kind of authentication like entering some kind of
username/password.

im using virConnectOpen(const char* name) function.

i tried using virConnectOpenAuth().. but whatever parameter ii give it gets
connected and there is no option to pass username/password.

Thanks in advance.

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


[libvirt] regarding the network information for Domain

2009-09-18 Thread anuj rampal
Hi all,

im trying to call libvirt api from windows.

I have created a guest OS(windows) using the libvirt api from my windows
machine.
It gets created fine it also gets the the IP address from the DHCP also.
So all works fine.

Now to RDP into the machine what I have to do is
1. logon to my host machine.
2. open the guest OS using either "virt-viewer" or "virt-manager".
3. check out the IP address of the machine.
4. then RDP into the guest OS.

My Question:

Is there a way to find The IP address of the Guest OS.???



im also trying to cross compile "virt-viewer 0.0.3" but this is what i get
when i do make:


[r...@fc-11 virt-viewer-0.0.3]# make
make  all-recursive
make[1]: Entering directory `/root/virt-viewer-0.0.3'
Making all in src
make[2]: Entering directory `/root/virt-viewer-0.0.3/src'
/bin/sh ../libtool --tag=CC   --mode=link i686-pc-mingw32-gcc -mms-bitfields
-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-vnc-1.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-2.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include
-I/usr/i686-pc-mingw32/sys-root/mingw/lib/gtk-2.0/include
-I/usr/i686-pc-mingw32/sys-root/mingw/include/atk-1.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include/cairo
-I/usr/i686-pc-mingw32/sys-root/mingw/include/pango-1.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0
-I/usr/i686-pc-mingw32/sys-root/mingw/lib/glib-2.0/include
-I/usr/i686-pc-mingw32/sys-root/mingw/include/pixman-1
-I/usr/i686-pc-mingw32/sys-root/mingw/include/libpng12   -mms-bitfields
-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-2.0
-I/usr/i686-pc-mingw32/sys-root/mingw/lib/gtk-2.0/include
-I/usr/i686-pc-mingw32/sys-root/mingw/include/atk-1.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include/cairo
-I/usr/i686-pc-mingw32/sys-root/mingw/include/pango-1.0
-I/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0
-I/usr/i686-pc-mingw32/sys-root/mingw/lib/glib-2.0/include
-I/usr/i686-pc-mingw32/sys-root/mingw/include/pixman-1
-I/usr/i686-pc-mingw32/sys-root/mingw/include/libpng12
-I/usr/i686-pc-mingw32/sys-root/mingw/include/libxml2
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -fasynchronous-unwind-tables -Wall
-Wmissing-prototypes -std=c99 -Wnested-externs -Wpointer-arith -Wextra
-Wshadow -Wcast-align -Wwrite-strings -Waggregate-return -Winline
-Wredundant-decls -Wno-sign-compare   -g -O2   -o virt-viewer.exe
virt_viewer-main.o -Wl,-luuid -L/usr/i686-pc-mingw32/sys-root/mingw/lib
-lgtk-vnc-1.0 -lgtk-win32-2.0 -lgnutls -lgdk-win32-2.0 -limm32 -lshell32
-lole32 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lgio-2.0 -lcairo
-lpangowin32-1.0 -lgdi32 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0
-lglib-2.0 -lintl   -Wl,-luuid -L/usr/i686-pc-mingw32/sys-root/mingw/lib
-lgtk-win32-2.0 -lgdk-win32-2.0 -limm32 -lshell32 -lole32 -latk-1.0
-lgdk_pixbuf-2.0 -lpangocairo-1.0 -lgio-2.0 -lcairo -lpangowin32-1.0 -lgdi32
-lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
-L/usr/i686-pc-mingw32/sys-root/mingw/lib -lxml2   -lvirt -lpthread
../libtool: line 834: X--tag=CC: command not found
../libtool: line 867: libtool: ignoring unknown tag : command not found
../libtool: line 834: X--mode=link: command not found
../libtool: line 1001: *** Warning: inferring the mode of operation is
deprecated.: command not found
../libtool: line 1002: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../libtool: line 2074: X-mms-bitfields: command not found
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-vnc-1.0: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-2.0: No such file or
directory
../libtool: line 2239: X-I/usr/i686-pc-mingw32/sys-root/mingw/include: No
such file or directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/lib/gtk-2.0/include: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/atk-1.0: No such file or
directory
../libtool: line 2239: X-I/usr/i686-pc-mingw32/sys-root/mingw/include/cairo:
No such file or directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/pango-1.0: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/lib/glib-2.0/include: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/pixman-1: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/libpng12: No such file or
directory
../libtool: line 2074: X-mms-bitfields: command not found
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/include/gtk-2.0: No such file or
directory
../libtool: line 2239:
X-I/usr/i686-pc-mingw32/sys-root/mingw/lib/gtk-2.0/include: No such file 

[libvirt] Create a Domain from windows client

2009-08-31 Thread anuj rampal
Hi all,

I'm trying to call the libvirt API from my Windows machine.

When i try to create to a Domain using "virDomainDefineXML" function

I have to pass an XML file containing the Description of the Domain.

Here is the part of the XML file that im using:


..
..
  
/usr/bin/qemu

  
  


  
  
  

..
..



This is the path which contains the img file for the Domain.

I have created this file using this command:

qemu-img create -f raw /var/lib/libvirt/images/WinXp.img 10G

*Now: my question is:*

Is there a way by which i can create this img file using some libvirt call
directly and then use this for my domain creation.

Or modify the XML file itself so  that virDomainDefineXML call creates the
img file at the path and the size that i specify.

Could someone also give me some example for the same.

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


[libvirt] Communicating with libvirt from windows

2009-08-24 Thread anuj rampal
Hi,

I have KVM running on one of my machine and I can controle the geues OS
using the virt-manager and Virsh tools.

Now what I want to do is talk to libvirt from my windows machine.

I tried to compile libvirt for windows but couldnt get any success with
that.

Is there a way by which i can talk to libvirt without this client..??

As in can i talk to libvirt over TCP sockets using xml (something like
that)...??

Thanks a lot in advance.

Regards
Anuj
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list