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

Re: [Ovirt-devel] Trouble on loading the VM onto the node



Hi

Thank you for your very intelligible explanation.
I did the command

#virsh -c qemu+ssh://192.168.50.3/system list
#virsh -c qemu+ssh://192.168.50.4/system list
#virsh -c qemu+ssh://192.168.50.5/system list

and I could see the VM named dddd running on the node3.
Thank you!
But I still feel strange because I could see only one VM named dddd running
though I'm running four VMs(aaaa, bbbb, cccc, and dddd).
Could this be a bug?
I attach the files in /var/log/ovirt-wui except rails.log and some
screenshots.
Screenshots explains how many VM are running now and how much resorces are
used.
please let me know where the problem is.

Thank you

----- Original Message ----- 
From: "Perry N. Myers" <pmyers redhat com>
To: "Naoya Terashima" <terashima naoya np css fujitsu com>
Cc: "Chris Lalancette" <clalance redhat com>; <ovirt-devel redhat com>
Sent: Monday, September 01, 2008 1:01 PM
Subject: Re: [Ovirt-devel] Trouble on loading the VM onto the node


> Naoya Terashima wrote:
> > Hi
> >
> > I felt relieved to hear VM is running within one of three node.
> > Thank you.
> > But how can I find out which node VM in running on?
> > I logged in every node to see if which has VM but I couldn't find out.
> > Every node I logged in didn't seemd to have VM.
> > Sorry for my repetitious question but please teach me how to find out
> > which node has VM.
>
> Right now the web UI does not expose which host is running a particular VM
> (note to self, we should add this).
>
> So the best way to tell if a VM is running on a particular node is to use
> the virsh list command as follows:
>
>  From the host running the ovirt-appliance:
> # virsh -c qemu+ssh://192.168.50.3/system list
>
> Use the IP address of the node you want to check.  node3 is 50.3, node4 is
> 50.4, etc...
>
> If you get errors about known_hosts having offending keys, prune the
> known_hosts file first:
> # ssh-keygen -R 192.168.50.3
> or
> # ssh-keygen -R node3.priv.ovirt.org
>
> (This is because the node generates a new ssh key on each boot.  This is
> something we haven't cleaned up yet)
>
> If you don't see your vm name listed in one of the virsh list commands it
> means the VM is not running on any node.  If the UI says it's running, but
> virsh list doesn't confirm it, this is probably a bug. If this is the
> case, please send us the log files in /var/log/ovirt-wui from the
> appliance as they may help us figure out what is not working properly.
>
> Thanks,
>
> Perry
>

Attachment: host-browser.log
Description: Binary data

Attachment: host-status.log
Description: Binary data

Attachment: mongrel.log
Description: Binary data

Attachment: Screenshot1.png
Description: PNG image

Attachment: Screenshot2.png
Description: PNG image

Attachment: Screenshot3.png
Description: PNG image

Attachment: taskomatic.log
Description: Binary data


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