From: <ope...@li...> - 2010-03-03 21:26:50
|
Andres, ----- ope...@li... wrote: > I have been done KVM VM installs through virt-install and specifing > the bridge (vmbr0 that is) - this have been worked so far - so I > expect it to work out for you also. I was looking into virt-manager > not offering vmbr0 choice - it seems to boil down to hald and dbus > problems - but so far I have not cracked the issue yet. Thanks for the reply. Just to make sure my changes to the system didn't put it in an unknown state, I did a fresh install of OpenNode from the 1.0 beta media. I did a yum upgrade and then I installed a few packages that make me happy like mc, screen, xorg-x11-xinit (so GUI X apps can easy be run over ssh tunnel), etc. I did not mess with the network configuration. As expected virt-manager will run but it still can't see the vmbr0 device and only offers NAT-based network devices. That's a shame so if you do figure out how to fix it, let me know. If it doesn't involve adding too many additional packages, I'd say it would be a worthwhile addition to the functionality. Per your advice, I used the virt-install method. I was able to install the machine and giving it the vmbr0 device, it was able to use a public IP just fine. Mission accomplished. Now though, post-install... after the VM is shut down, I'm not sure how to start it back up. virsh start vmname doesn't work. virsh gives the following error: [root@rhev-h2 ~]# virsh start kvmdemo1 error: failed to get domain 'kvmdemo1' error: Domain not found I'm used to virsh just working on Fedora 12 but I'm guessing it is because Fedora is assuming qemu whereas with opennode, it can be either an OpenVZ container or a KVM VM... so it doesn't assume a particular domain and that has to be specified? I'm going through the man page on virsh to see if I can figure it out... but I thought it didn't hurt to ask. I'm sure it is something pretty easy. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] |