Ovirt devel - May 2009 - Installing vm in ovirt

I will try to explain problem as good as possible.
I just finished building my ovirt server from the git repo.
Added a vm in cobbler.
But when i install a vm it will install on breth0 on my managed node(this is
my admin network(199.1.10.*)).
Now it is not reachable on the quest network.
Isn't this suppose to be breth1(guest network(192.168.50.*))?
The management server has ip 192.168.50.200(quest) and 199.1.10.1(admin).
If i boot with pxe from eth1 on the node breth0 wil get ip 192.168.50.201
but also the dns server will be 192.168.50.200.
Dis is not working , because it can't resolve the name of the ovirt serer
and the node won,t show up in the gui.

Please help..

Mike Maarse
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20090522/fec75ad7/attachment.htm>

On Fri, May 22, 2009 at 04:21:56PM +0200, Mike maarse
wrote:
> I will try to explain problem as good as possible.
> I just finished building my ovirt server from the git repo.
> Added a vm in cobbler.
> But when i install a vm it will install on breth0 on my managed node(this
is
> my admin network(199.1.10.*)).
> Now it is not reachable on the quest network.
> Isn't this suppose to be breth1(guest network(192.168.50.*))?
> The management server has ip 192.168.50.200(quest) and 199.1.10.1(admin).
> If i boot with pxe from eth1 on the node breth0 wil get ip 192.168.50.201
> but also the dns server will be 192.168.50.200.
> Dis is not working , because it can't resolve the name of the ovirt
serer
> and the node won,t show up in the gui.
> 
> Please help..
> 
> Mike Maarse
You have correctly realized that pxebooting a VM doesn't work with the
2-network setup (I think this is what you're describing, anyway). The
preferred method for installing a VM is to put an ISO image in cobbler
and boot that, assigning the VM to your guest network. We create a
special nfs share on the server for ISOs that all the nodes mount over
the admin network. (Alternatively, you could run another cobbler
instance on your guest network and pxe from that -- but it won't be
integrated with oVirt at all.)

Does this help at all?

Take care,
--Hugh

No i don't boot the vm in pxe just the node. I have 1 server as managed node
and 1 server to manage the node
When i create a vm i select the cobbler profile i created (Fedora10).
But then it will install the vm with the ip of the admin network
(199.1.10.*).
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20090522/fb6b4168/attachment.htm>

Is this the network part  on the left of the server gui or on the node
settings?
If yes, how do i set this up wright?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20090522/5cf433da/attachment.htm>

On Fri, May 22, 2009 at 04:49:39PM +0200, Mike maarse
wrote:
> Is this the network part  on the left of the server gui or on the node
> settings?
> If yes, how do i set this up wright?
> 
> 
> On Fri, May 22, 2009 at 4:42 PM, Hugh O. Brock <hbrock at redhat.com>
wrote:
> 
> > On Fri, May 22, 2009 at 04:37:47PM +0200, Mike maarse wrote:
> > > No i don't boot the vm in pxe just the node. I have 1 server
as managed
> > node
> > > and 1 server to manage the node
> > > When i create a vm i select the cobbler profile i created
(Fedora10).
> > > But then it will install the vm with the ip of the admin network
> > > (199.1.10.*).
> >
> >
> > Hmm... what network did you assign the VM when you created it?
> >
> > --Hugh
> >
OK so you have to do three things:

1. Create a "network" on the networks pane to serve as your guest
network. Here you name the network and define some basic things about it
-- is it dhcp or statically configured, what is the gateway, etc.

2. For each host you want to use this network, map one available nic to
it (click "edit networks" in the host details pane). Doesn't
matter
which NIC you choose except that it has to actually be physically
connected to whatever network you want to use. For now you have to
reboot the host after you have done this (this will go away in the
future).

3. When you create VMs, choose your guest network as the network for the
VM. When the VM boots it will automatically get a vnic that uses the
appropriate bridge on the physical host it's deployed on.

I know this is not clear in the docs, I apologize -- it is new code.

Hope this helps,
--Hugh