[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [fedora-virt] virt-viewer windows port



Hi,
 
1st i tried connecting to libvirt from a remote linux machine
 
This is the URI:
LIBVIRT_DEBUG=1 virt-viewer -c qemu://FC11-KVM/session 2
 
This is the result that i got:

11:28:15.602: debug : virInitialize:279 : register drivers
11:28:15.603: debug : virRegisterDriver:776 : registering Test as driver 0
11:28:15.603: debug : virRegisterNetworkDriver:614 : registering Test as network driver 0
11:28:15.603: debug : virRegisterInterfaceDriver:645 : registering Test as interface driver 0
11:28:15.603: debug : virRegisterStorageDriver:676 : registering Test as storage driver 0
11:28:15.603: debug : virRegisterDeviceMonitor:707 : registering Test as device driver 0
11:28:15.603: debug : virRegisterSecretDriver:738 : registering Test as secret driver 0
11:28:15.603: debug : virRegisterDriver:776 : registering OPENVZ as driver 1
11:28:15.603: debug : vboxRegister:101 : VBoxCGlueInit failed, using dummy driver
11:28:15.604: debug : virRegisterDriver:776 : registering VBOX as driver 2
11:28:15.604: debug : virRegisterNetworkDriver:614 : registering VBOX as network driver 1
11:28:15.604: debug : virRegisterStorageDriver:676 : registering VBOX as storage driver 1
11:28:15.604: debug : virRegisterDriver:776 : registering ESX as driver 3
11:28:15.604: debug : virRegisterDriver:776 : registering remote as driver 4
11:28:15.604: debug : virRegisterNetworkDriver:614 : registering remote as network driver 2
11:28:15.604: debug : virRegisterInterfaceDriver:645 : registering remote as interface driver 1
11:28:15.604: debug : virRegisterStorageDriver:676 : registering remote as storage driver 2
11:28:15.604: debug : virRegisterDeviceMonitor:707 : registering remote as device driver 1
11:28:15.604: debug : virRegisterSecretDriver:738 : registering remote as secret driver 1
11:28:15.604: debug : virConnectOpenAuth:1273 : name=qemu://FC11-KVM/session, auth=0x9bfe40, flags=1
11:28:15.604: debug : do_open:1042 : name "qemu://FC11-KVM/session" to URI components:
  scheme qemu
  opaque (null)
  authority (null)
  server FC11-KVM
  user (null)
  port 0
  path /session
11:28:15.604: debug : do_open:1052 : trying driver 0 (Test) ...
11:28:15.604: debug : do_open:1058 : driver 0 Test returned DECLINED
11:28:15.604: debug : do_open:1052 : trying driver 1 (OPENVZ) ...
11:28:15.604: debug : do_open:1058 : driver 1 OPENVZ returned DECLINED
11:28:15.604: debug : do_open:1052 : trying driver 2 (VBOX) ...
11:28:15.604: debug : do_open:1058 : driver 2 VBOX returned DECLINED
11:28:15.604: debug : do_open:1052 : trying driver 3 (ESX) ...
11:28:15.604: debug : do_open:1058 : driver 3 ESX returned DECLINED
11:28:15.604: debug : do_open:1052 : trying driver 4 (remote) ...
11:28:15.605: debug : doRemoteOpen:535 : proceeding with name = qemu:///session
11:28:15.608: debug : initialise_gnutls:1101 : loading CA file //etc/pki/CA/cacert.pem
11:28:15.608: debug : initialise_gnutls:1114 : loading client cert and key from files //etc/pki/libvirt/clientcert.pem and //etc/pki/libvirt/private/clientkey.pem
11:28:15.703: debug : remoteIO:7421 : Do proc=66 serial=0 length=28 wait=(nil)
11:28:15.703: debug : remoteIO:7483 : We have the buck 66 0xb7d3e008 0xb7d3e008
11:28:15.709: debug : remoteIODecodeMessageLength:7032 : Got length, now need 64 total (60 more)
11:28:15.710: debug : remoteIOEventLoop:7347 : Giving up the buck 66 0xb7d3e008 (nil)
11:28:15.710: debug : remoteIO:7514 : All done with our call 66 (nil) 0xb7d3e008
11:28:15.710: debug : remoteIO:7421 : Do proc=1 serial=1 length=56 wait=(nil)
11:28:15.710: debug : remoteIO:7483 : We have the buck 1 0x8424f50 0x8424f50
11:28:15.712: debug : remoteIODecodeMessageLength:7032 : Got length, now need 56 total (52 more)
11:28:15.712: debug : remoteIOEventLoop:7347 : Giving up the buck 1 0x8424f50 (nil)
11:28:15.712: debug : remoteIO:7514 : All done with our call 1 (nil) 0x8424f50
11:28:15.715: debug : doRemoteOpen:850 : Adding Handler for remote events
11:28:15.715: debug : doRemoteOpen:857 : virEventAddHandle failed: No addHandleImpl defined. continuing without events.
11:28:15.715: debug : do_open:1058 : driver 4 remote returned SUCCESS
11:28:15.715: debug : do_open:1078 : network driver 0 Test returned DECLINED
11:28:15.716: debug : do_open:1078 : network driver 1 VBOX returned DECLINED
11:28:15.716: debug : do_open:1078 : network driver 2 remote returned SUCCESS
11:28:15.716: debug : do_open:1097 : interface driver 0 Test returned DECLINED
11:28:15.716: debug : do_open:1097 : interface driver 1 remote returned SUCCESS
11:28:15.716: debug : do_open:1117 : storage driver 0 Test returned DECLINED
11:28:15.716: debug : do_open:1117 : storage driver 1 VBOX returned DECLINED
11:28:15.716: debug : do_open:1117 : storage driver 2 remote returned SUCCESS
11:28:15.716: debug : do_open:1137 : node driver 0 Test returned DECLINED
11:28:15.717: debug : do_open:1137 : node driver 1 remote returned SUCCESS
11:28:15.717: debug : do_open:1164 : secret driver 0 Test returned DECLINED
11:28:15.717: debug : do_open:1164 : secret driver 1 remote returned SUCCESS
11:28:15.717: debug : virDomainLookupByID:1739 : conn=0x83fc4b0, id=2
11:28:15.717: debug : remoteIO:7421 : Do proc=22 serial=2 length=32 wait=(nil)
11:28:15.717: debug : remoteIO:7483 : We have the buck 22 0x8424f50 0x8424f50
11:28:15.719: debug : remoteIODecodeMessageLength:7032 : Got length, now need 92 total (88 more)
11:28:15.719: debug : remoteIOEventLoop:7347 : Giving up the buck 22 0x8424f50 (nil)
11:28:15.719: debug : remoteIO:7514 : All done with our call 22 (nil) 0x8424f50
11:28:15.720: debug : virGetDomain:343 : New hash entry 0x841c630
11:28:15.720: debug : virDomainGetXMLDesc:2780 : domain=0x841c630, flags=0
11:28:15.720: debug : remoteIO:7421 : Do proc=14 serial=3 length=68 wait=(nil)
11:28:15.720: debug : remoteIO:7483 : We have the buck 14 0x8424f50 0x8424f50
11:28:15.723: debug : remoteIODecodeMessageLength:7032 : Got length, now need 1296 total (1292 more)
11:28:15.723: debug : remoteIOEventLoop:7347 : Giving up the buck 14 0x8424f50 (nil)
11:28:15.723: debug : remoteIO:7514 : All done with our call 14 (nil) 0x8424f50
11:28:15.724: debug : virDomainGetName:2431 : domain=0x841c630
11:28:15.724: debug : virDomainFree:1969 : domain=0x841c630
11:28:15.724: debug : virUnrefDomain:420 : unref domain 0x841c630 CloneWinXp 1
11:28:15.725: debug : virReleaseDomain:374 : release domain 0x841c630 CloneWinXp
11:28:15.725: debug : virReleaseDomain:390 : unref connection 0x83fc4b0 2
11:28:15.725: debug : virConnectClose:1291 : conn=0x83fc4b0
11:28:15.725: debug : virUnrefConnect:257 : unref connection 0x83fc4b0 1
11:28:15.725: debug : remoteIO:7421 : Do proc=2 serial=4 length=28 wait=(nil)
11:28:15.725: debug : remoteIO:7483 : We have the buck 2 0x8424f50 0x8424f50
11:28:15.727: debug : remoteIODecodeMessageLength:7032 : Got length, now need 56 total (52 more)
11:28:15.757: debug : remoteIOEventLoop:7347 : Giving up the buck 2 0x8424f50 (nil)
11:28:15.757: debug : remoteIO:7514 : All done with our call 2 (nil) 0x8424f50
11:28:15.758: debug : virReleaseConnect:214 : release connection 0x83fc4b0

 
Then i tried on my windows machine
 
URI that i used:
>virt-viewer.exe -c qemu://FC11-KVM/session 2
 
and this is the result that i got:
 
11:35:01.621: debug : virInitialize:294 : register drivers
11:35:01.626: debug : virRegisterDriver:735 : registering Test as driver 0
11:35:01.626: debug : virRegisterNetworkDriver:604 : registering Test as network
 driver 0
11:35:01.626: debug : virRegisterInterfaceDriver:635 : registering Test as inter
face driver 0
11:35:01.626: debug : virRegisterStorageDriver:666 : registering Test as storage
 driver 0
11:35:01.627: debug : virRegisterDeviceMonitor:697 : registering Test as device
driver 0
11:35:01.627: debug : virRegisterDriver:735 : registering ESX as driver 1
11:35:01.627: debug : virRegisterDriver:735 : registering remote as driver 2
11:35:01.627: debug : virRegisterNetworkDriver:604 : registering remote as netwo
rk driver 1
11:35:01.627: debug : virRegisterInterfaceDriver:635 : registering remote as int
erface driver 1
11:35:01.627: debug : virRegisterStorageDriver:666 : registering remote as stora
ge driver 1
11:35:01.628: debug : virRegisterDeviceMonitor:697 : registering remote as devic
e driver 1
11:35:01.635: debug : virConnectOpenAuth:1214 : name=qemu://FC11-KVM/session, au
th=0022FD88, flags=1
11:35:01.639: debug : do_open:1001 : name "qemu://FC11-KVM/session" to URI compo
nents:
  scheme qemu
  opaque (null)
  authority (null)
  server FC11-KVM
  user (null)
  port 0
  path /session
11:35:01.646: debug : do_open:1011 : trying driver 0 (Test) ...
11:35:01.648: debug : do_open:1017 : driver 0 Test returned DECLINED
11:35:01.650: debug : do_open:1011 : trying driver 1 (ESX) ...
11:35:01.652: debug : do_open:1017 : driver 1 ESX returned DECLINED
11:35:01.653: debug : do_open:1011 : trying driver 2 (remote) ...
11:35:01.656: debug : doRemoteOpen:533 : proceeding with name = qemu:///session
11:35:01.672: debug : initialise_gnutls:1099 : loading CA file /usr/i686-pc-ming
w32/sys-root/mingw/etc/pki/CA/cacert.pem
11:35:01.677: debug : initialise_gnutls:1112 : loading client cert and key from
files /usr/i686-pc-mingw32/sys-root/mingw/etc/pki/libvirt/clientcert.pem and /us
r/i686-pc-mingw32/sys-root/mingw/etc/pki/libvirt/private/clientkey.pem
11:35:01.697: debug : do_open:1017 : driver 2 remote returned ERROR
11:35:01.698: debug : virUnrefConnect:232 : unref connection 0263B068 1
11:35:01.700: debug : virReleaseConnect:191 : release connection 0263B068
unable to connect to libvirt qemu://FC11-KVM/session

 
tried with different URI on windows:
>virt-viewer.exe -c qemu+tcp://FC11-KVM/session 2
 
Result:
 
11:45:36.054: debug : virInitialize:294 : register drivers
11:45:36.060: debug : virRegisterDriver:735 : registering Test as driver 0
11:45:36.060: debug : virRegisterNetworkDriver:604 : registering Test as network
 driver 0
11:45:36.060: debug : virRegisterInterfaceDriver:635 : registering Test as inter
face driver 0
11:45:36.060: debug : virRegisterStorageDriver:666 : registering Test as storage
 driver 0
11:45:36.060: debug : virRegisterDeviceMonitor:697 : registering Test as device
driver 0
11:45:36.060: debug : virRegisterDriver:735 : registering ESX as driver 1
11:45:36.060: debug : virRegisterDriver:735 : registering remote as driver 2
11:45:36.060: debug : virRegisterNetworkDriver:604 : registering remote as netwo
rk driver 1
11:45:36.060: debug : virRegisterInterfaceDriver:635 : registering remote as int
erface driver 1
11:45:36.061: debug : virRegisterStorageDriver:666 : registering remote as stora
ge driver 1
11:45:36.061: debug : virRegisterDeviceMonitor:697 : registering remote as devic
e driver 1
11:45:36.068: debug : virConnectOpenAuth:1214 : name=qemu+tcp://FC11-KVM/session
, auth=0022FD88, flags=1
11:45:36.071: debug : do_open:1001 : name "qemu+tcp://FC11-KVM/session" to URI c
omponents:
  scheme qemu+tcp
  opaque (null)
  authority (null)
  server FC11-KVM
  user (null)
  port 0
  path /session
11:45:36.080: debug : do_open:1011 : trying driver 0 (Test) ...
11:45:36.083: debug : do_open:1017 : driver 0 Test returned DECLINED
11:45:36.085: debug : do_open:1011 : trying driver 1 (ESX) ...
11:45:36.087: debug : do_open:1017 : driver 1 ESX returned DECLINED
11:45:36.089: debug : do_open:1011 : trying driver 2 (remote) ...
11:45:36.091: debug : doRemoteOpen:533 : proceeding with name = qemu:///session
11:45:36.106: debug : remoteIO:7078 : Do proc=66 serial=0 length=28 wait=0000000
0
11:45:36.109: debug : remoteIO:7140 : We have the buck 66 029BDFC8 029BDFC8
11:45:36.114: debug : remoteIODecodeMessageLength:6689 : Got length, now need 64
 total (60 more)
11:45:36.118: debug : remoteIOEventLoop:7004 : Giving up the buck 66 029BDFC8 00
000000
11:45:36.120: debug : remoteIO:7171 : All done with our call 66 00000000 029BDFC
8
11:45:36.126: debug : remoteIO:7078 : Do proc=1 serial=1 length=56 wait=00000000
11:45:36.128: debug : remoteIO:7140 : We have the buck 1 029BDFC8 029BDFC8
11:45:36.134: debug : remoteIODecodeMessageLength:6689 : Got length, now need 56
 total (52 more)
11:45:36.137: debug : remoteIOEventLoop:7004 : Giving up the buck 1 029BDFC8 000
00000
11:45:36.139: debug : remoteIO:7171 : All done with our call 1 00000000 029BDFC8
11:45:36.141: debug : doRemoteOpen:848 : Adding Handler for remote events
11:45:36.143: debug : doRemoteOpen:858 : Adding Timeout for remote event queue f
lushing
11:45:36.146: debug : do_open:1017 : driver 2 remote returned SUCCESS
11:45:36.148: debug : do_open:1037 : network driver 0 Test returned DECLINED
11:45:36.149: debug : do_open:1037 : network driver 1 remote returned SUCCESS
11:45:36.151: debug : do_open:1056 : interface driver 0 Test returned DECLINED
11:45:36.153: debug : do_open:1056 : interface driver 1 remote returned SUCCESS
11:45:36.155: debug : do_open:1076 : storage driver 0 Test returned DECLINED
11:45:36.157: debug : do_open:1076 : storage driver 1 remote returned SUCCESS
11:45:36.158: debug : do_open:1096 : node driver 0 Test returned DECLINED
11:45:36.160: debug : do_open:1096 : node driver 1 remote returned SUCCESS
11:45:36.249: debug : virDomainLookupByID:1692 : conn=0297A3A0, id=2
11:45:36.252: debug : remoteIO:7078 : Do proc=22 serial=2 length=32 wait=0000000
0
11:45:36.254: debug : remoteIO:7140 : We have the buck 22 03EF6858 03EF6858
 
 
Regards
Anuj
 
On Thu, Sep 24, 2009 at 6:54 PM, Richard W.M. Jones <rjones redhat com> wrote:
On Thu, Sep 24, 2009 at 06:41:03PM +0530, anuj rampal wrote:
> But with TLS there was some certificate issue but after resolving this
> issue, im still not able to connect to the libvirt
> this is what it says:
>
> virsh.exe -c qemu://FC11-KVM/session
> error: unable to connect to libvirtd at 'FC11-KVM': errno=22
> error: failed to connect to the hypervisor
>
> this is what it says...???? (this is from my vista machine)

Apparently "errno 22" is EINVAL.

That doesn't help much.  I really need you to set the LIBVIRT_DEBUG
environment variable to 1 on order to show the full messages, and then
continue with the tests as outlined in the previous email.

http://support.microsoft.com/kb/310519

Rich.

--
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]