6:26 p.m.
[root@virt5 ~]# virsh -c qemu:///system list
Please enter your authentication name: admin
Please enter your password:
error: authentication failed: authentication failed
error: failed to connect to the hypervisor
I have tried the admin username/password, but that did not work. How do I
access virsh on the nodes directly?
<>
Nathan Stratton CTO,
BlinkMind, Inc.
nathan at robotics.net nathan at blinkmind.com
http://www.robotics.net http://www.blinkmind.com
6:37 p.m.
----- Original Message -----
From: "Nathan Stratton" <nathan(a)robotics.net>
To: users(a)ovirt.org
Sent: Sunday, February 26, 2012 11:26:55 AM
Subject: [Users] Using virsh on the node
[root@virt5 ~]# virsh -c qemu:///system list
Please enter your authentication name: admin
Please enter your password:
error: authentication failed: authentication failed
error: failed to connect to the hypervisor
I have tried the admin username/password, but that did not work. How
do I
access virsh on the nodes directly?
Ideally you'd not, you'd use vdsClient.
You can use --readonly if you're happy with read only
We really want to make sure that only vdsm is talking to libvirt otherwise we can get
ourselves into trouble.
If you *really* need to connect with libvirt have a look in this directory on the node
/etc/pki/vdsm/keys/
><>
Nathan Stratton CTO, BlinkMind, Inc.
nathan at robotics.net nathan at
blinkmind.com
http://www.robotics.net
http://www.blinkmind.com
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:44 p.m.
On Sun, 26 Feb 2012, Andrew Cathrow wrote:
Ideally you'd not, you'd use vdsClient.
You can use --readonly if you're happy with read only
I need to start ovirt-engine, so I need more then -r.
We really want to make sure that only vdsm is talking to libvirt
otherwise we can get ourselves into trouble.
Understand.
If you *really* need to connect with libvirt have a look in this
directory on the node /etc/pki/vdsm/keys/
Thanks, I found that same password via google, but I can't find the
username. I have tried a bunch I thought it might by, but get
authentication failed with everything I have tried.
-Nathan
10:05 p.m.
----- Original Message -----
From: "Nathan Stratton" <nathan(a)robotics.net>
To: "Andrew Cathrow" <acathrow(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Sunday, February 26, 2012 2:44:22 PM
Subject: Re: [Users] Using virsh on the node
On Sun, 26 Feb 2012, Andrew Cathrow wrote:
> Ideally you'd not, you'd use vdsClient.
> You can use --readonly if you're happy with read only
I need to start ovirt-engine, so I need more then -r.
So ovirt-engine is a VM on the node?
> We really want to make sure that only vdsm is talking to libvirt
> otherwise we can get ourselves into trouble.
Understand.
> If you *really* need to connect with libvirt have a look in this
> directory on the node /etc/pki/vdsm/keys/
Thanks, I found that same password via google, but I can't find the
username. I have tried a bunch I thought it might by, but get
authentication failed with everything I have tried.
iirc it's vdsm@rhevh
-Nathan
10:13 p.m.
On Sun, 26 Feb 2012, Andrew Cathrow wrote:
So ovirt-engine is a VM on the node?
Yes, I have a cluster of 20 nodes and don't want to have a static server
for ovirt-engine.
iirc it's vdsm@rhevh
Thanks, that worked with: "virsh -c qemu:///system list", I also found
that on a node I could use "virsh -c qemu+tcp:///system list" and it
worked without a username/password.
-Nathan
9:12 a.m.
----- Original Message -----
From: "Nathan Stratton" <nathan(a)robotics.net>
To: "Andrew Cathrow" <acathrow(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Sunday, 26 February, 2012 10:13:27 PM
Subject: Re: [Users] Using virsh on the node
On Sun, 26 Feb 2012, Andrew Cathrow wrote:
> So ovirt-engine is a VM on the node?
Yes, I have a cluster of 20 nodes and don't want to have a static
server
for ovirt-engine.
So the engine is a VM in that same cluster, along with the VMs it manages?
What do you use for storage?
> iirc it's vdsm@rhevh
Thanks, that worked with: "virsh -c qemu:///system list", I also
found
that on a node I could use "virsh -c qemu+tcp:///system list" and it
worked without a username/password.
-Nathan
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Regards,
Dan Yasny
Red Hat Israel
+972 9769 2280
4:13 p.m.
On Mon, 27 Feb 2012, Dan Yasny wrote:
So the engine is a VM in that same cluster, along with the VMs it
manages?
Yes, the only thing I have not been able to figure out is how to let the
ovirt-engine know that ovirt-engine is running. :) I thought that it would
see via libvirt, but it does not. I also tried setting it in the db, but
it keeps getting cleared. Any idea on how to let ovirt-engine know that a
host has been started manually?
What do you use for storage?
NFS:
mount 10.13.0.4:/images/ /rhev/data-center/mnt/10.13.0.4:_images
mount 10.13.0.4:/iso/ /rhev/data-center/mnt/10.13.0.4:_iso
Dan Yasny
Red Hat Israel
+972 9769 2280
<>
Nathan Stratton CTO,
BlinkMind, Inc.
nathan at robotics.net nathan at blinkmind.com
http://www.robotics.net http://www.blinkmind.com
6:34 p.m.
----- Original Message -----
From: "Nathan Stratton" <nathan(a)robotics.net>
To: "Dan Yasny" <dyasny(a)redhat.com>
Cc: users(a)ovirt.org, "Andrew Cathrow" <acathrow(a)redhat.com>
Sent: Monday, 27 February, 2012 4:13:54 PM
Subject: Re: [Users] Using virsh on the node
On Mon, 27 Feb 2012, Dan Yasny wrote:
> So the engine is a VM in that same cluster, along with the VMs it
> manages?
Yes, the only thing I have not been able to figure out is how to let
the
ovirt-engine know that ovirt-engine is running. :) I thought that it
would
see via libvirt, but it does not. I also tried setting it in the db,
but
it keeps getting cleared. Any idea on how to let ovirt-engine know
that a
host has been started manually?
Seriously, not a good idea. The Engine is supposed to be looking at the setup, and not be
in the setup, where it may be affected by the problems that might occur to the setup.
I'm pretty sure there's lots of though being devoted to removing this limitation,
but when we say it's a bad idea, it really is, it's not like we simply want you to
run an extra machine
> What do you use for storage?
That's easier than block storage, but still, what happens if the host where the engine
was running failed - who would update VM statuses and restart the HA VMs?
NFS:
mount 10.13.0.4:/images/ /rhev/data-center/mnt/10.13.0.4:_images
mount 10.13.0.4:/iso/ /rhev/data-center/mnt/10.13.0.4:_iso
> Dan Yasny
> Red Hat Israel
> +972 9769 2280
><>
Nathan Stratton CTO, BlinkMind, Inc.
nathan at robotics.net nathan at
blinkmind.com
http://www.robotics.net
http://www.blinkmind.com
--
Regards,
Dan Yasny
Red Hat Israel
+972 9769 2280
8:25 p.m.
On 02/27/2012 06:34 PM, Dan Yasny wrote:
----- Original Message -----
> From: "Nathan Stratton"<nathan(a)robotics.net>
> To: "Dan Yasny"<dyasny(a)redhat.com>
> Cc: users(a)ovirt.org, "Andrew Cathrow"<acathrow(a)redhat.com>
> Sent: Monday, 27 February, 2012 4:13:54 PM
> Subject: Re: [Users] Using virsh on the node
>
> On Mon, 27 Feb 2012, Dan Yasny wrote:
>
>> So the engine is a VM in that same cluster, along with the VMs it
>> manages?
>
> Yes, the only thing I have not been able to figure out is how to let
> the
> ovirt-engine know that ovirt-engine is running. :) I thought that it
> would
> see via libvirt, but it does not. I also tried setting it in the db,
> but
> it keeps getting cleared. Any idea on how to let ovirt-engine know
> that a
> host has been started manually?
Seriously, not a good idea. The Engine is supposed to be looking at the setup, and not be
in the setup, where it may be affected by the problems that might occur to the setup.
I'm pretty sure there's lots of though being devoted to removing this limitation,
but when we say it's a bad idea, it really is, it's not like we simply want you to
run an extra machine
Doron - this reminds me of the all-in-one discussion. what was the
resolution on flagging the node as a node running an engine VM (even
without engine knowing about its own VM)
>
>> What do you use for storage?
>
That's easier than block storage, but still, what happens if the host where the
engine was running failed - who would update VM statuses and restart the HA VMs?
> NFS:
>
> mount 10.13.0.4:/images/ /rhev/data-center/mnt/10.13.0.4:_images
> mount 10.13.0.4:/iso/ /rhev/data-center/mnt/10.13.0.4:_iso
>
>> Dan Yasny
>> Red Hat Israel
>> +972 9769 2280
>
>> <>
> Nathan Stratton CTO, BlinkMind, Inc.
> nathan at robotics.net nathan at
> blinkmind.com
> http://www.robotics.net
> http://www.blinkmind.com
>
8:48 p.m.
On Mon, 27 Feb 2012, Dan Yasny wrote:
Seriously, not a good idea. The Engine is supposed to be looking at
the setup, and not be in the setup, where it may be affected by the problems that might
occur to the setup.
I'm pretty sure there's lots of though being devoted to removing this limitation,
but when we say it's a bad idea, it really is, it's not like we simply want you to
run an extra machine
Hmm, find it hard to believe that people are not going to want to run
management on the cluster.
That's easier than block storage, but still, what happens if the
host where the engine was running failed - who would update VM statuses and restart the HA
VMs?
Don't I also run into similar problems if my dedicated host where the
engine was running fails?
<>
Nathan Stratton CTO,
BlinkMind, Inc.
nathan at robotics.net nathan at blinkmind.com
http://www.robotics.net http://www.blinkmind.com
4664
days inactive
4665
days old
10 comments
4 participants
participants (4)
-
Andrew Cathrow -
Dan Yasny -
Itamar Heim -
Nathan Stratton