On 08/04/2012 02:07 AM, Rino Rondan wrote:
Hi
I want to know if you have a demo of a configured ovirt system because I
will be on this event
http://www.fcad.uner.edu.ar/destacadas/x-jornadas-nacionales-de-administracion-e-informatica
,
and I need to show ovirt as open-source implementation .
On 08/06/2012 01:40 AM, Artem wrote:
Run console from ovirt-shell work... but no auto fullscreen for display vm
please open a bug for this to be added.
thanks
# ovirt-shell -c -l "http://192.168.0.3:8080/api"; -u "admin@internal" -p 'pass'
==
On 08/06/2012 02:43 AM, Artem wrote:
Hm...
thi is correct?
curl -X POST -H "Accept: application/xml" -H "Content-Type:
application/xml" -u admin@internal:pass -d
"900"
https://192.168.0.3:8443/api/vms/d3db360f-4ff5-46f5-b61d-db09465db52c/ticket
partially...
this allows you to get the ticket
On 06/08/12 05:06, Jacob Wyatt wrote:
> OK, so I reinstalled yesterday using the prepackaged 3.1 beta yum repository.
> It's better. It now correctly assigns the ovirtmgmt network to the node
> when it is attached.
> Unfortunately, I still cannot seem to add a second interface or VLAN withou
OK, so I reinstalled yesterday using the prepackaged 3.1 beta yum repository.
It's better. It now correctly assigns the ovirtmgmt network to the node when
it is attached. Unfortunately, I still cannot seem to add a second interface
or VLAN without breaking the networking again. I'm wondering
Hm...
thi is correct?
curl -X POST -H "Accept: application/xml" -H "Content-Type:
application/xml" -u admin@internal:pass -d
"900"
https://192.168.0.3:8443/api/vms/d3db360f-4ff5-46f5-b61d-db09465db52c/ticket
2012/8/6 Artem :
> Run console from ovirt-shell work... but no auto fullscreen for dis
Run console from ovirt-shell work... but no auto fullscreen for display vm
# ovirt-shell -c -l "http://192.168.0.3:8080/api"; -u "admin@internal" -p 'pass'
==
>>> connected to oVirt manager 3.1.0.0 <<<
==
On 08/06/2012 01:30 AM, Itamar Heim wrote:
On 08/06/2012 01:24 AM, Artem wrote:
hm... this all config... hov i get it?
you need to set it (default expiration is 120 seconds iirc).
check this thread:
http://www.mail-archive.com/engine-devel@ovirt.org/msg00611.html
and this documentation on set
On 08/06/2012 01:24 AM, Artem wrote:
hm... this all config... hov i get it?
you need to set it (default expiration is 120 seconds iirc).
check this thread:
http://www.mail-archive.com/engine-devel@ovirt.org/msg00611.html
and this documentation on setvmticket:
http://docs.redhat.com/docs/en-US/
hm... this all config... hov i get it?
dns-srv
server
up
536870912
false
1
spice
192.168.0.3
5900
5901
1
true
2012-08-05T16:05:43.413+04:00
2012-08-01T03:01:12.573+04:00
ovirt
false
migratable
536870912
false
2012/8/6 Itamar Heim :
> what about set
On 08/06/2012 01:08 AM, Artem wrote:
section for target vm
spice
192.168.0.3
5900
5901
1
true
log from connect to spice-xpi
2012-08-05 22:03:30.766+: 1587: debug : qemuMonitorIOProcess:327 :
QEMU_MONITOR_IO_PROCESS: mon=0x7f3b2c0135d0 buf={"timestamp":
{"seconds": 13442
section for target vm
spice
192.168.0.3
5900
5901
1
true
log from connect to spice-xpi
2012-08-05 22:03:30.766+: 1587: debug : qemuMonitorIOProcess:327 :
QEMU_MONITOR_IO_PROCESS: mon=0x7f3b2c0135d0 buf={"timestamp":
{"seconds": 1344204210, "microseconds": 766409}, "event":
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 .spicec/spicec.
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
cat .spicec/spicec.log
1344217716 INFO [3164:3164] Application::main: starting 0.8.3
1344217716 INFO [3164:3164] init_key_map: using
On 08/06/2012 12:43 AM, Artem wrote:
[root@vm-srv ~]# cat /etc/pki/vdsm/certs/vdsmcert.pem | grep Subject
Subject: O=ICL, CN=192.168.0.3
so, you added this host based on it's ip.
the above is the subject you should be using...
Subject Public Key Info:
2012/8/6 Itamar Heim
[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 :
> cat /etc/pki/vdsm/certs/vdsmcert.pem | grep Subject
___
Users mailing list
Users@ovir
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" --secure-c
yes engine and kvm(qemu-kvm) installed on same machine (vm-srv)
i change host-subject but..
# spicec -h vm-srv -p 5900 -s 5901 --host-subject "C=US, O=ICL,
CN=vm-srv" --secure-channels=all
Error: subject mismatch: #entries cert=2, input=3
Error: failed to connect w/SSL, ssl_error
error:0001:
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 trus
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 (0x2
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, inp
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
routines:SSL3_
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: Conne
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 ERR
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 bo
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
> /
26 matches
Mail list logo
