On Fri, Aug 03, 2012 at 06:47:44AM +1000, Justin Clift wrote:
On 02/08/2012, at 2:29 AM, Ricardo Esteves wrote:
And now, after reboot of the node, i get this:
[root@blade4 ~]# virsh capabilities
Segmentation fault
When that seg fault happens, does anything get printed to
On 04/08/12 17:51, Jacob Wyatt wrote:
I just installed a new 3.1 engine and I have one node with the latest node
iso installed. After setting up one of the network interfaces on the node
and confirming I have network I am able to attach it to the engine. I've
done this starting from both
Hi all,
spicec connected to virtual machines on Ovirt web console... but
manual connect this (on windows or linux)
1344197680 INFO [3001:3002] RedPeer::connect_unsecure: Connected to
192.168.0.3 5900
1344197680 INFO [3001:3002] RedPeer::connect_secure: Connected to
192.168.0.3 5901
1344197680
On 08/05/2012 07:23 PM, Artem wrote:
Hi all,
spicec connected to virtual machines on Ovirt web console... but
manual connect this (on windows or linux)
1344197680 INFO [3001:3002] RedPeer::connect_unsecure: Connected to
192.168.0.3 5900
1344197680 INFO [3001:3002] RedPeer::connect_secure:
I have tried so
# spicec -h vm-srv -p 5900 -s 5901 --host-subject C=US, O=ICL,
CN=CA-vm-srv.15064 --secure-channels=all
Error: subject mismatch: #entries cert=2, input=3
Error: failed to connect w/SSL, ssl_error
error:0001:lib(0):func(0):reason(1)
3078249000:error:14090086:SSL
On 08/05/2012 11:56 PM, Artem wrote:
I have tried so
# spicec -h vm-srv -p 5900 -s 5901 --host-subject C=US, O=ICL,
CN=CA-vm-srv.15064 --secure-channels=all
this looks like the subject name of the CA, not the host running the
virtual machine?
Error: subject mismatch: #entries cert=2,
hmm... not sure if understood correctly...
vm-srv this KVM host.. (server) and I connect from another machine to vm on kvm.
this subject name i get in .spicec/spice_truststore.pem
//
# cat .spicec/spice_truststore.pem
Certificate:
Data:
Version: 3
On 08/06/2012 12:07 AM, Artem wrote:
hmm... not sure if understood correctly...
vm-srv this KVM host.. (server) and I connect from another machine to vm on kvm.
did you install the engine and kvm host on same machine?
this subject name i get in .spicec/spice_truststore.pem
yes, spice
On 08/06/2012 12:30 AM, Artem wrote:
yes engine and kvm(qemu-kvm) installed on same machine (vm-srv)
what do you get for:
cat /etc/pki/vdsm/certs/vdsmcert.pem | grep Subject
?
i change host-subject but..
# spicec -h vm-srv -p 5900 -s 5901 --host-subject C=US, O=ICL,
CN=vm-srv
[root@vm-srv ~]# cat /etc/pki/vdsm/certs/vdsmcert.pem | grep Subject
Subject: O=ICL, CN=192.168.0.3
Subject Public Key Info:
2012/8/6 Itamar Heim ih...@redhat.com:
cat /etc/pki/vdsm/certs/vdsmcert.pem | grep Subject
___
Users mailing
On 08/06/2012 12:51 AM, Artem wrote:
oh ... I have done a foolish thing, but...
spicec -h vm-srv -p 5900 -s 5901 --host-subject O=ICL,
CN=192.168.0.3 --secure-channels=all
Warning: connect failed 7
why are you assuming port 5901 is the secure port for spice connection?
cat
section for target vm
display
typespice/type
address192.168.0.3/address
port5900/port
secure_port5901/secure_port
monitors1/monitors
allow_reconnecttrue/allow_reconnect
/display
log from connect to spice-xpi
2012-08-05 22:03:30.766+: 1587: debug : qemuMonitorIOProcess:327 :
hm... this all config... hov i get it?
vms
vm id=d3db360f-4ff5-46f5-b61d-db09465db52c
href=/api/vms/d3db360f-4ff5-46f5-b61d-db09465db52c
namedns-srv/name
actions
link rel=shutdown
href=/api/vms/d3db360f-4ff5-46f5-b61d-db09465db52c/shutdown/
link rel=start
13 matches
Mail list logo
