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

Re: [virt-tools-list] progress on virt-viewer for windows



Hi,

My first tests using virsh from http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit (x86_64) binaries. I'll try the 32-bit binaries and report on the results.

After having success with a few comands using virsh, I decided to try virt-viewer.

It reported missing libssp-0.dll, so I copied as per previous intructions by Christophe. Now when I try:

C:\Program Files\VirtViewer\bin>virt-viewer -c qemu+tls://kvmhost/system guest1

It locks up. No output, no error, no remote-viewer window. :-( As both virsh and remote-viewer were woking now, I kinda expected virt-viewer should work, or at least give an error we could debug.

Changing the connection URL to:

C:\Program Files\VirtViewer\bin>virt-viewer -c qemu+tcp://kvmhost/system guest1

Which would give an "unsupported authentication type 1" on virsh, but locks up virt-viewer the same way as using TLS. It looks like virt-viewer is locking up *before* connecting to libvirtd to find the remote display config for "guest1".

Adding --debug to virt-viewer with tls shows:

(virt-viewer.exe:23376): virt-viewer-DEBUG: Insert window 0 0000000000A240A0
(virt-viewer.exe:23376): virt-viewer-DEBUG: fullscreen display 0: 0
(virt-viewer.exe:23376): virt-viewer-DEBUG: connecting ...
(virt-viewer.exe:23376): virt-viewer-DEBUG: Opening connection to libvirt with U
RI qemu+tls://kvmhost/system
(virt-viewer.exe:23376): virt-viewer-DEBUG: Add handle 3 1 0000000003684A90

If I try --debug but using a qemu+tcp URL, I get the same output (with different memory addresses, of course)

Attached is another virt-maanger try (using qemu+tls, which should work for libvirt) but with LIBVIRT_DEBUG=debug.

This log shows that libvirt has connected and was authenticated (the RPC_TLS_CONTEXT_SESSION_ALLOW entry means that, right?). How strange. So I also attached also a debug log for the qemu+tcp url.

Hope this helps making virt-viewer work on windows.


[]s, Fernando Lozano


[]s, Fernando Lozano

C:\Program Files\VirtViewer\bin>virt-viewer --debug  -c qemu+tcp://kvmhost/sys
tem guest1
2013-09-19 19:23:09.589+0000: 22716: info : libvirt version: 1.1.2
2013-09-19 19:23:09.589+0000: 22716: debug : virLogParseOutputs:1336 : outputs="
1:file:virt-viewer.log"
2013-09-19 19:23:09.590+0000: 22716: warning : virLogParseOutputs:1401 : Ignorin
g invalid log output setting.
2013-09-19 19:23:09.599+0000: 22716: debug : virGlobalInit:438 : register driver
s
2013-09-19 19:23:09.599+0000: 22716: debug : virRegisterDriver:764 : driver=0000
00006CDBAA60 name=Test
2013-09-19 19:23:09.600+0000: 22716: debug : virRegisterDriver:776 : registering
 Test as driver 0
2013-09-19 19:23:09.600+0000: 22716: debug : virRegisterNetworkDriver:611 : regi
stering Test as network driver 0
2013-09-19 19:23:09.600+0000: 22716: debug : virRegisterInterfaceDriver:638 : re
gistering Test as interface driver 0
2013-09-19 19:23:09.600+0000: 22716: debug : virRegisterStorageDriver:665 : regi
stering Test as storage driver 0
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterNodeDeviceDriver:692 : r
egistering Test as device driver 0
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterSecretDriver:719 : regis
tering Test as secret driver 0
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterNWFilterDriver:746 : reg
istering Test as network filter driver 0
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterDriver:764 : driver=0000
00006CDBBF20 name=PHYP
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterDriver:776 : registering
 PHYP as driver 1
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterStorageDriver:665 : regi
stering PHYP as storage driver 1
2013-09-19 19:23:09.601+0000: 22716: debug : virRegisterInterfaceDriver:638 : re
gistering PHYP as interface driver 1
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterDriver:764 : driver=0000
00006CDBC540 name=ESX
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterDriver:776 : registering
 ESX as driver 2
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterInterfaceDriver:638 : re
gistering ESX as interface driver 2
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterNetworkDriver:611 : regi
stering ESX as network driver 1
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterStorageDriver:665 : regi
stering ESX as storage driver 2
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterNodeDeviceDriver:692 : r
egistering ESX as device driver 1
2013-09-19 19:23:09.602+0000: 22716: debug : virRegisterSecretDriver:719 : regis
tering ESX as secret driver 1
2013-09-19 19:23:09.603+0000: 22716: debug : virRegisterNWFilterDriver:746 : reg
istering ESX as network filter driver 1
2013-09-19 19:23:09.603+0000: 22716: debug : virRegisterDriver:764 : driver=0000
00006CDBB4A0 name=remote
2013-09-19 19:23:09.603+0000: 22716: debug : virRegisterDriver:776 : registering
 remote as driver 3
2013-09-19 19:23:09.603+0000: 22716: debug : virRegisterNetworkDriver:611 : regi
stering remote as network driver 2
2013-09-19 19:23:09.603+0000: 22716: debug : virRegisterInterfaceDriver:638 : re
gistering remote as interface driver 3
2013-09-19 19:23:09.604+0000: 22716: debug : virRegisterStorageDriver:665 : regi
stering remote as storage driver 3
2013-09-19 19:23:09.604+0000: 22716: debug : virRegisterNodeDeviceDriver:692 : r
egistering remote as device driver 2
2013-09-19 19:23:09.604+0000: 22716: debug : virRegisterSecretDriver:719 : regis
tering remote as secret driver 2
2013-09-19 19:23:09.604+0000: 22716: debug : virRegisterNWFilterDriver:746 : reg
istering remote as network filter driver 2
(virt-viewer.exe:23348): virt-viewer-DEBUG: Insert window 0 00000000009040A0
(virt-viewer.exe:23348): virt-viewer-DEBUG: fullscreen display 0: 0
2013-09-19 19:23:09.659+0000: 22716: debug : virEventRegisterImpl:203 : addHandl
e=0000000000414370 updateHandle=0000000000414270 removeHandle=0000000000414600 a
ddTimeout=0000000000414180 updateTimeout=0000000000414090 removeTimeout=00000000
00414520
(virt-viewer.exe:23348): virt-viewer-DEBUG: connecting ...
(virt-viewer.exe:23348): virt-viewer-DEBUG: Opening connection to libvirt with U
RI qemu+tcp://kvmhost/system
2013-09-19 19:23:09.673+0000: 22716: debug : virConnectOpenAuth:1459 : name=qemu
+tcp://kvmhost/system, auth=000000000022FA90, flags=1
2013-09-19 19:23:09.677+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000009964E0 classname=virConnect
2013-09-19 19:23:09.682+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035E6CD0 classname=virConnectCloseCallbackData
2013-09-19 19:23:09.687+0000: 22716: debug : do_open:1171 : name "qemu+tcp://lnx
servvm/system" to URI components:
  scheme qemu+tcp
  server kvmhost
  user (null)
  port 0
  path /system

2013-09-19 19:23:09.694+0000: 22716: debug : do_open:1217 : trying driver 0 (Tes
t) ...
2013-09-19 19:23:09.697+0000: 22716: debug : do_open:1224 : driver 0 Test return
ed DECLINED
2013-09-19 19:23:09.700+0000: 22716: debug : do_open:1217 : trying driver 1 (PHY
P) ...
2013-09-19 19:23:09.703+0000: 22716: debug : do_open:1224 : driver 1 PHYP return
ed DECLINED
2013-09-19 19:23:09.707+0000: 22716: debug : do_open:1217 : trying driver 2 (ESX
) ...
2013-09-19 19:23:09.711+0000: 22716: debug : do_open:1224 : driver 2 ESX returne
d DECLINED
2013-09-19 19:23:09.714+0000: 22716: debug : do_open:1217 : trying driver 3 (rem
ote) ...
2013-09-19 19:23:09.717+0000: 22716: debug : doRemoteOpen:599 : proceeding with
name = qemu:///system
2013-09-19 19:23:09.720+0000: 22716: debug : doRemoteOpen:608 : Connecting with
transport 5
2013-09-19 19:23:09.728+0000: 22716: debug : virNetSocketNew:155 : localAddr=000
000000022F4E0 remoteAddr=000000000022F570 fd=3 errfd=-1 pid=0
2013-09-19 19:23:09.733+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000009A1D60 classname=virNetSocket
2013-09-19 19:23:09.738+0000: 22716: debug : virNetSocketNew:205 : RPC_SOCKET_NE
W: sock=00000000009A1D60 fd=3 errfd=-1 pid=0 localAddr=192.168.0.143;57056, remo
teAddr=192.168.0.7;16509
2013-09-19 19:23:09.746+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000000996B40 classname=virNetClient
2013-09-19 19:23:09.751+0000: 22716: debug : virNetClientNew:326 : RPC_CLIENT_NE
W: client=0000000000996B40 sock=00000000009A1D60
2013-09-19 19:23:09.755+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000000996B40
2013-09-19 19:23:09.760+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000009A1D60
(virt-viewer.exe:23348): virt-viewer-DEBUG: Add handle 3 1 00000000009A1D60
2013-09-19 19:23:09.766+0000: 22716: debug : virKeepAliveNew:196 : client=000000
0000996B40, interval=-1, count=0
2013-09-19 19:23:09.770+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035DDE00 classname=virKeepAlive
2013-09-19 19:23:09.775+0000: 22716: debug : virKeepAliveNew:215 : RPC_KEEPALIVE
_NEW: ka=00000000035DDE00 client=0000000000996B40
2013-09-19 19:23:09.780+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000000996B40
2013-09-19 19:23:09.783+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000035E6CD0
2013-09-19 19:23:09.786+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035E6510 classname=virNetClientProgram
2013-09-19 19:23:09.793+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035E6450 classname=virNetClientProgram
2013-09-19 19:23:09.797+0000: 22716: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035E6490 classname=virNetClientProgram
2013-09-19 19:23:09.801+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000035E6510
2013-09-19 19:23:09.805+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000035E6450
2013-09-19 19:23:09.810+0000: 22716: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000035E6490
2013-09-19 19:23:09.813+0000: 22716: debug : doRemoteOpen:816 : Trying authentic
ation
2013-09-19 19:23:09.816+0000: 22716: debug : virNetMessageNew:44 : msg=000000000
35DE030 tracked=0
2013-09-19 19:23:09.819+0000: 22716: debug : virNetMessageEncodePayload:373 : En
code length as 28
2013-09-19 19:23:09.824+0000: 22716: debug : virNetClientSendInternal:1952 : RPC
_CLIENT_MSG_TX_QUEUE: client=0000000000996B40 len=28 prog=536903814 vers=1 proc=
66 type=0 status=0 serial=0
2013-09-19 19:23:09.831+0000: 22716: debug : virNetClientCallNew:1905 : New call
 00000000035E6410: msg=00000000035DE030, expectReply=1, nonBlock=0
2013-09-19 19:23:09.836+0000: 22716: debug : virNetClientIO:1714 : Outgoing mess
age prog=536903814 version=1 serial=0 proc=66 type=0 length=28 dispatch=00000000
00000000
2013-09-19 19:23:09.844+0000: 22716: debug : virNetClientIO:1773 : We have the b
uck head=00000000035E6410 call=00000000035E6410
C:\Program Files\VirtViewer\bin>virt-viewer --debug  -c qemu+tls://kvmhost/sys
tem guest1
2013-09-19 19:18:32.581+0000: 23376: info : libvirt version: 1.1.2
2013-09-19 19:18:32.581+0000: 23376: debug : virLogParseOutputs:1336 : outputs="
1:file:virt-viewer.log"
2013-09-19 19:18:32.582+0000: 23376: warning : virLogParseOutputs:1401 : Ignorin
g invalid log output setting.
2013-09-19 19:18:32.592+0000: 23376: debug : virGlobalInit:438 : register driver
s
2013-09-19 19:18:32.592+0000: 23376: debug : virRegisterDriver:764 : driver=0000
00006CDBAA60 name=Test
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterDriver:776 : registering
 Test as driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterNetworkDriver:611 : regi
stering Test as network driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterInterfaceDriver:638 : re
gistering Test as interface driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterStorageDriver:665 : regi
stering Test as storage driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterNodeDeviceDriver:692 : r
egistering Test as device driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterSecretDriver:719 : regis
tering Test as secret driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterNWFilterDriver:746 : reg
istering Test as network filter driver 0
2013-09-19 19:18:32.593+0000: 23376: debug : virRegisterDriver:764 : driver=0000
00006CDBBF20 name=PHYP
2013-09-19 19:18:32.594+0000: 23376: debug : virRegisterDriver:776 : registering
 PHYP as driver 1
2013-09-19 19:18:32.594+0000: 23376: debug : virRegisterStorageDriver:665 : regi
stering PHYP as storage driver 1
2013-09-19 19:18:32.594+0000: 23376: debug : virRegisterInterfaceDriver:638 : re
gistering PHYP as interface driver 1
2013-09-19 19:18:32.594+0000: 23376: debug : virRegisterDriver:764 : driver=0000
00006CDBC540 name=ESX
2013-09-19 19:18:32.594+0000: 23376: debug : virRegisterDriver:776 : registering
 ESX as driver 2
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterInterfaceDriver:638 : re
gistering ESX as interface driver 2
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterNetworkDriver:611 : regi
stering ESX as network driver 1
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterStorageDriver:665 : regi
stering ESX as storage driver 2
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterNodeDeviceDriver:692 : r
egistering ESX as device driver 1
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterSecretDriver:719 : regis
tering ESX as secret driver 1
2013-09-19 19:18:32.595+0000: 23376: debug : virRegisterNWFilterDriver:746 : reg
istering ESX as network filter driver 1
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterDriver:764 : driver=0000
00006CDBB4A0 name=remote
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterDriver:776 : registering
 remote as driver 3
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterNetworkDriver:611 : regi
stering remote as network driver 2
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterInterfaceDriver:638 : re
gistering remote as interface driver 3
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterStorageDriver:665 : regi
stering remote as storage driver 3
2013-09-19 19:18:32.596+0000: 23376: debug : virRegisterNodeDeviceDriver:692 : r
egistering remote as device driver 2
2013-09-19 19:18:32.597+0000: 23376: debug : virRegisterSecretDriver:719 : regis
tering remote as secret driver 2
2013-09-19 19:18:32.597+0000: 23376: debug : virRegisterNWFilterDriver:746 : reg
istering remote as network filter driver 2
(virt-viewer.exe:22724): virt-viewer-DEBUG: Insert window 0 00000000009140A0
(virt-viewer.exe:22724): virt-viewer-DEBUG: fullscreen display 0: 0
2013-09-19 19:18:32.651+0000: 23376: debug : virEventRegisterImpl:203 : addHandl
e=0000000000414370 updateHandle=0000000000414270 removeHandle=0000000000414600 a
ddTimeout=0000000000414180 updateTimeout=0000000000414090 removeTimeout=00000000
00414520
(virt-viewer.exe:22724): virt-viewer-DEBUG: connecting ...
(virt-viewer.exe:22724): virt-viewer-DEBUG: Opening connection to libvirt with U
RI qemu+tls://kvmhost/system
2013-09-19 19:18:32.663+0000: 23376: debug : virConnectOpenAuth:1459 : name=qemu
+tls://kvmhost/system, auth=000000000022FA90, flags=1
2013-09-19 19:18:32.667+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000009A64E0 classname=virConnect
2013-09-19 19:18:32.670+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000003606CD0 classname=virConnectCloseCallbackData
2013-09-19 19:18:32.674+0000: 23376: debug : do_open:1171 : name "qemu+tls://lnx
servvm/system" to URI components:
  scheme qemu+tls
  server kvmhost
  user (null)
  port 0
  path /system

2013-09-19 19:18:32.679+0000: 23376: debug : do_open:1217 : trying driver 0 (Tes
t) ...
2013-09-19 19:18:32.681+0000: 23376: debug : do_open:1224 : driver 0 Test return
ed DECLINED
2013-09-19 19:18:32.684+0000: 23376: debug : do_open:1217 : trying driver 1 (PHY
P) ...
2013-09-19 19:18:32.687+0000: 23376: debug : do_open:1224 : driver 1 PHYP return
ed DECLINED
2013-09-19 19:18:32.690+0000: 23376: debug : do_open:1217 : trying driver 2 (ESX
) ...
2013-09-19 19:18:32.693+0000: 23376: debug : do_open:1224 : driver 2 ESX returne
d DECLINED
2013-09-19 19:18:32.695+0000: 23376: debug : do_open:1217 : trying driver 3 (rem
ote) ...
2013-09-19 19:18:32.697+0000: 23376: debug : doRemoteOpen:599 : proceeding with
name = qemu:///system
2013-09-19 19:18:32.701+0000: 23376: debug : doRemoteOpen:608 : Connecting with
transport 0
2013-09-19 19:18:32.704+0000: 23376: debug : virNetTLSContextLocateCredentials:8
08 : pkipath=(NULL) isServer=0 tryUserPkiPath=0
2013-09-19 19:18:32.708+0000: 23376: debug : virNetTLSContextLocateCredentials:8
80 : Using default TLS CA certificate path
2013-09-19 19:18:32.711+0000: 23376: debug : virNetTLSContextLocateCredentials:8
86 : Using default TLS CA revocation list path
2013-09-19 19:18:32.714+0000: 23376: debug : virNetTLSContextLocateCredentials:8
92 : Using default TLS key/certificate path
2013-09-19 19:18:32.718+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000036064D0 classname=virNetTLSContext
2013-09-19 19:18:32.722+0000: 23376: debug : virNetTLSContextLoadCertFromFile:51
2 : isServer 0 certFile /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/c
lientcert.pem
2013-09-19 19:18:32.728+0000: 23376: debug : virFileClose:90 : Closed fd 3
2013-09-19 19:18:32.730+0000: 23376: debug : virNetTLSContextLoadCACertListFromF
ile:556 : certFile /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/CA/cacert.pem
2013-09-19 19:18:32.735+0000: 23376: debug : virFileClose:90 : Closed fd 3
2013-09-19 19:18:32.740+0000: 23376: debug : virNetTLSContextCheckCertBasicConst
raints:185 : Cert /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/clientc
ert.pem basic constraints 0
2013-09-19 19:18:32.745+0000: 23376: debug : virNetTLSContextCheckCertKeyUsage:2
31 : Cert /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/clientcert.pem
key usage status 0 usage 224 critical 0
2013-09-19 19:18:32.752+0000: 23376: debug : virNetTLSContextCheckCertKeyPurpose
:303 : No key purpose data available at slot 0
2013-09-19 19:18:32.756+0000: 23376: debug : virNetTLSContextCheckCertBasicConst
raints:185 : Cert /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/CA/cacert.pem b
asic constraints 1
2013-09-19 19:18:32.761+0000: 23376: debug : virNetTLSContextCheckCertKeyUsage:2
31 : Cert /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/CA/cacert.pem key usage
 status 0 usage 6 critical 0
2013-09-19 19:18:32.767+0000: 23376: debug : virNetTLSContextLoadCredentials:638
 : loading CA cert from /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/CA/cacert
.pem
2013-09-19 19:18:32.772+0000: 23376: debug : virNetTLSContextLoadCredentials:667
 : Skipping non-existent CA CRL /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/C
A/cacrl.pem
2013-09-19 19:18:32.777+0000: 23376: debug : virNetTLSContextLoadCredentials:680
 : loading cert and key from /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libv
irt/clientcert.pem and /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/pr
ivate/clientkey.pem
2013-09-19 19:18:32.786+0000: 23376: debug : virNetTLSContextNew:778 : RPC_TLS_C
ONTEXT_NEW: ctxt=00000000036064D0 cacert=/usr/x86_64-w64-mingw32/sys-root/mingw/
etc/pki/CA/cacert.pem cacrl=/usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/CA/ca
crl.pem cert=/usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/clientcert.p
em key=/usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki/libvirt/private/clientkey.
pem sanityCheckCert=1 requireValidCert=1 isServer=0
2013-09-19 19:18:32.804+0000: 23376: debug : virNetSocketNew:155 : localAddr=000
000000022F4E0 remoteAddr=000000000022F570 fd=3 errfd=-1 pid=0
2013-09-19 19:18:32.809+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000003624FD0 classname=virNetSocket
2013-09-19 19:18:32.812+0000: 23376: debug : virNetSocketNew:205 : RPC_SOCKET_NE
W: sock=0000000003624FD0 fd=3 errfd=-1 pid=0 localAddr=192.168.0.143;56994, remo
teAddr=192.168.0.7;16514
2013-09-19 19:18:32.817+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000009A6B40 classname=virNetClient
2013-09-19 19:18:32.821+0000: 23376: debug : virNetClientNew:326 : RPC_CLIENT_NE
W: client=00000000009A6B40 sock=0000000003624FD0
2013-09-19 19:18:32.825+0000: 23376: debug : doRemoteOpen:635 : Starting TLS ses
sion
2013-09-19 19:18:32.827+0000: 23376: debug : virNetTLSSessionNew:1206 : ctxt=000
00000036064D0 hostname=kvmhost isServer=0
2013-09-19 19:18:32.830+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035F2C50 classname=virNetTLSSession
2013-09-19 19:18:32.834+0000: 23376: debug : virNetTLSSessionNew:1259 : RPC_TLS_
SESSION_NEW: sess=00000000035F2C50 ctxt=00000000036064D0 hostname=kvmhost isSe
rver=0
2013-09-19 19:18:32.841+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000035F2C50
2013-09-19 19:18:32.843+0000: 23376: debug : virNetTLSSessionHandshake:1348 : se
ss=00000000035F2C50
2013-09-19 19:18:32.855+0000: 23376: debug : virNetTLSSessionHandshake:1351 : Re
t=0
2013-09-19 19:18:32.858+0000: 23376: debug : virNetTLSSessionHandshake:1354 : Ha
ndshake is complete
2013-09-19 19:18:32.861+0000: 23376: debug : virNetTLSContextValidCertificate:10
75 : Peer DN is C=BR,ST=RJ,L=Rio de Janeiro,O=IBP,OU=Suporte TI,CN=kvmhost,EMA
IL=ti ibp org br
2013-09-19 19:18:32.867+0000: 23376: debug : virNetTLSContextCheckCertBasicConst
raints:185 : Cert [session] basic constraints 0
2013-09-19 19:18:32.871+0000: 23376: debug : virNetTLSContextCheckCertKeyUsage:2
31 : Cert [session] key usage status 0 usage 224 critical 0
2013-09-19 19:18:32.876+0000: 23376: debug : virNetTLSContextCheckCertKeyPurpose
:303 : No key purpose data available at slot 0
2013-09-19 19:18:32.880+0000: 23376: debug : virNetTLSContextValidCertificate:11
12 : RPC_TLS_CONTEXT_SESSION_ALLOW: ctxt=00000000036064D0 sess=00000000035F2C50
dname=C=BR,ST=RJ,L=Rio de Janeiro,O=IBP,OU=Suporte TI,CN=kvmhost,EMAIL=ti ibp 
org.br
2013-09-19 19:18:32.890+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000009A6B40
2013-09-19 19:18:32.894+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000003624FD0
(virt-viewer.exe:22724): virt-viewer-DEBUG: Add handle 3 1 0000000003624FD0
2013-09-19 19:18:32.900+0000: 23376: debug : virKeepAliveNew:196 : client=000000
00009A6B40, interval=-1, count=0
2013-09-19 19:18:32.904+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
00000000035FE030 classname=virKeepAlive
2013-09-19 19:18:32.909+0000: 23376: debug : virKeepAliveNew:215 : RPC_KEEPALIVE
_NEW: ka=00000000035FE030 client=00000000009A6B40
2013-09-19 19:18:32.913+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
00000000009A6B40
2013-09-19 19:18:32.917+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000003606CD0
2013-09-19 19:18:32.920+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000003606410 classname=virNetClientProgram
2013-09-19 19:18:32.925+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000003606D10 classname=virNetClientProgram
2013-09-19 19:18:32.929+0000: 23376: debug : virObjectNew:199 : OBJECT_NEW: obj=
0000000003606D50 classname=virNetClientProgram
2013-09-19 19:18:32.935+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000003606410
2013-09-19 19:18:32.939+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000003606D10
2013-09-19 19:18:32.944+0000: 23376: debug : virObjectRef:293 : OBJECT_REF: obj=
0000000003606D50
2013-09-19 19:18:32.947+0000: 23376: debug : doRemoteOpen:816 : Trying authentic
ation
2013-09-19 19:18:32.950+0000: 23376: debug : virNetMessageNew:44 : msg=000000000
35FE0A0 tracked=0
2013-09-19 19:18:32.954+0000: 23376: debug : virNetMessageEncodePayload:373 : En
code length as 28
2013-09-19 19:18:32.958+0000: 23376: debug : virNetClientSendInternal:1952 : RPC
_CLIENT_MSG_TX_QUEUE: client=00000000009A6B40 len=28 prog=536903814 vers=1 proc=
66 type=0 status=0 serial=0
2013-09-19 19:18:32.964+0000: 23376: debug : virNetClientCallNew:1905 : New call
 0000000003606D90: msg=00000000035FE0A0, expectReply=1, nonBlock=0
2013-09-19 19:18:32.970+0000: 23376: debug : virNetClientIO:1714 : Outgoing mess
age prog=536903814 version=1 serial=0 proc=66 type=0 length=28 dispatch=00000000
00000000
2013-09-19 19:18:32.976+0000: 23376: debug : virNetClientIO:1773 : We have the b
uck head=0000000003606D90 call=0000000003606D90

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