Menu
▾
▴
opennode-users
|
From: <ope...@li...> - 2010-03-02 19:14:54
|
Greetings, I'm trying to use virt-manager to create and manage KVM VMs on OpenNode. virt-manager doesn't seem to be aware that bridged networking is setup and defaults to providing private DHCP addresses to the VMs one creates. It seems that virt-manager is expecting one bridge setup in order to do public/static IPs and OpenNode sets up the bridging different. Perhaps it is just a matter of using a particular bridge device name. On my OpenNode machine I have two bridge devices: vmbr0 - Has the public IP assigned by OpenNode virbr0 - Has the private IP (192.168.122.1) setup by virt-manager At least I think that is what is going on. I realize that the OpenNode developers are working on a web-based management system... and that there are alternative management tools other than virt-manager... but it is installed and it would be nice if it was pre-configured in a working fashion. I was able to create KVM VM just fine with virt-manager, it just has semi-functional networking because only private IPs and NATing works. I don't know enough about the underlying config of virt-manager to fix it... other than creating a bridge device named br0 and giving it the public IP of the machine... bypassing the bridge device that OpenNode has created/configured. I haven't done that yet but I assume it would work since that's what I do on other Red Hat-based distros with KVM/virt-manager (RHEL 5.4 and Fedora 9, 10, 11, and 12). I also created an OpenVZ container with my own OS Template (rather than using those provided by OpenNode) and it worked fine. I realize that if I try the fix mentioned in the previous paragraph I'd have to edit the /etc/sysconfig/network-scripts/ifcfg-venet0 file to tell it to use the br0 instead of venet0. Any suggestions? TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] |
|
From: <ope...@li...> - 2010-03-03 11:19:04
|
Hi Scott, No - don't edit /etc/sysconfig/network-scripts/ifcfg-venet0 - as there are probably better alternatives. You should be able to change bridge on existing VM also - just edit VM-s xml definition file: nano -w /etc/libvirt/qemu/VMNAME.xml #Replace bridge name like that in VM domain xml definition <source bridge='vmbr0'/> It seems that default KVM bridge is defined here: nano -w /etc/libvirt/qemu/networks/default.xml You could try to replace bridge name there also and see if new KVM VM install with virt-manager now provides the right bridge. In virt-manager you should select something like * Shared physical device (instead of "Virtual network) and there should be eth0 (vmbr0) then to select. If its not possible to instruct virt-manager to use vmbr0 instead of virbr0 then better use virt-install cli utility to start KVM VM install for now (in this example its openfiler - replace iso, disk image and VM name to suit your needs): virt-install --connect qemu:///session --name openfiler23 --ram 512 --disk path=/storage/images/openfiler23.img,size=2 --network bridge:vmbr0 --vnc --os-type=linux --os-variant=rhel5 --cdrom /storage/iso/openfiler-2.3-x86_64-disc1.iso --accelerate --hvm --noautoconsole For attaching a vnc viewer do: #setup ssh tunnel for vnc ssh -L 5555:127.0.0.1:5900 ro...@vi... #on your desktop machine (this is ubuntu example - change vnc viewer name to what you have installed) xtighvncviewer localhost::5555 Regards, ---------------------------------------------- Andres Toomsalu, an...@ac... ope...@li... wrote: > Greetings, > > I'm trying to use virt-manager to create and manage KVM VMs on OpenNode. virt-manager doesn't seem to be aware that bridged networking is setup and defaults to providing private DHCP addresses to the VMs one creates. It seems that virt-manager is expecting one bridge setup in order to do public/static IPs and OpenNode sets up the bridging different. Perhaps it is just a matter of using a particular bridge device name. On my OpenNode machine I have two bridge devices: > > vmbr0 - Has the public IP assigned by OpenNode > virbr0 - Has the private IP (192.168.122.1) setup by virt-manager > > At least I think that is what is going on. > > I realize that the OpenNode developers are working on a web-based management system... and that there are alternative management tools other than virt-manager... but it is installed and it would be nice if it was pre-configured in a working fashion. > > I was able to create KVM VM just fine with virt-manager, it just has semi-functional networking because only private IPs and NATing works. > > I don't know enough about the underlying config of virt-manager to fix it... other than creating a bridge device named br0 and giving it the public IP of the machine... bypassing the bridge device that OpenNode has created/configured. I haven't done that yet but I assume it would work since that's what I do on other Red Hat-based distros with KVM/virt-manager (RHEL 5.4 and Fedora 9, 10, 11, and 12). > > I also created an OpenVZ container with my own OS Template (rather than using those provided by OpenNode) and it worked fine. I realize that if I try the fix mentioned in the previous paragraph I'd have to edit the /etc/sysconfig/network-scripts/ifcfg-venet0 file to tell it to use the br0 instead of venet0. > > Any suggestions? > > TYL, > |
|
From: <ope...@li...> - 2010-03-03 12:09:27
|
Hi Just to mention. Libvirt community has a stand that scripts/configs under /etc/libvirt should be edited through libvirt methods (virsh for console access). Default networking can be changed with virsh the following way: virsh -c qemu:///system net-edit default #change bridge name in xml configuration that appeared This should help with consistency as there are probably syntax checks after editing and saving. Danel On 03.03.2010, at 12:54, ope...@li... wrote: > Hi Scott, > > No - don't edit /etc/sysconfig/network-scripts/ifcfg-venet0 - as there > are probably better alternatives. > > You should be able to change bridge on existing VM also - just edit > VM-s > xml definition file: > nano -w /etc/libvirt/qemu/VMNAME.xml > > #Replace bridge name like that in VM domain xml definition > <source bridge='vmbr0'/> > > It seems that default KVM bridge is defined here: > nano -w /etc/libvirt/qemu/networks/default.xml > > You could try to replace bridge name there also and see if new KVM VM > install with virt-manager now provides the right bridge. > In virt-manager you should select something like * Shared physical > device (instead of "Virtual network) and there should be eth0 (vmbr0) > then to select. > > If its not possible to instruct virt-manager to use vmbr0 instead of > virbr0 then better use virt-install cli utility to start KVM VM > install > for now (in this example its openfiler - replace iso, disk image and > VM > name to suit your needs): > > virt-install --connect qemu:///session --name openfiler23 --ram 512 > --disk path=/storage/images/openfiler23.img,size=2 --network > bridge:vmbr0 --vnc --os-type=linux --os-variant=rhel5 --cdrom > /storage/iso/openfiler-2.3-x86_64-disc1.iso --accelerate --hvm > --noautoconsole > > For attaching a vnc viewer do: > > #setup ssh tunnel for vnc > ssh -L 5555:127.0.0.1:5900 ro...@vi... > #on your desktop machine (this is ubuntu example - change vnc viewer > name to what you have installed) > xtighvncviewer localhost::5555 > > > Regards, > > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > ope...@li... wrote: >> Greetings, >> >> I'm trying to use virt-manager to create and manage KVM VMs on >> OpenNode. virt-manager doesn't seem to be aware that bridged >> networking is setup and defaults to providing private DHCP >> addresses to the VMs one creates. It seems that virt-manager is >> expecting one bridge setup in order to do public/static IPs and >> OpenNode sets up the bridging different. Perhaps it is just a >> matter of using a particular bridge device name. On my OpenNode >> machine I have two bridge devices: >> >> vmbr0 - Has the public IP assigned by OpenNode >> virbr0 - Has the private IP (192.168.122.1) setup by virt-manager >> >> At least I think that is what is going on. >> >> I realize that the OpenNode developers are working on a web-based >> management system... and that there are alternative management >> tools other than virt-manager... but it is installed and it would >> be nice if it was pre-configured in a working fashion. >> >> I was able to create KVM VM just fine with virt-manager, it just >> has semi-functional networking because only private IPs and NATing >> works. >> >> I don't know enough about the underlying config of virt-manager to >> fix it... other than creating a bridge device named br0 and giving >> it the public IP of the machine... bypassing the bridge device that >> OpenNode has created/configured. I haven't done that yet but I >> assume it would work since that's what I do on other Red Hat-based >> distros with KVM/virt-manager (RHEL 5.4 and Fedora 9, 10, 11, and >> 12). >> >> I also created an OpenVZ container with my own OS Template (rather >> than using those provided by OpenNode) and it worked fine. I >> realize that if I try the fix mentioned in the previous paragraph >> I'd have to edit the /etc/sysconfig/network-scripts/ifcfg-venet0 >> file to tell it to use the br0 instead of venet0. >> >> Any suggestions? >> >> TYL, >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
|
From: <ope...@li...> - 2010-03-03 18:23:53
|
Danel, ----- ope...@li... wrote: > Just to mention. Libvirt community has a stand that scripts/configs > under /etc/libvirt should be edited through libvirt methods (virsh for > console access). > > Default networking can be changed with virsh the following way: > virsh -c qemu:///system > net-edit default > #change bridge name in xml configuration that appeared > > This should help with consistency as there are probably syntax checks > after editing and saving. Editing the default doesn't seem to help at all. Changing the bridge name would save fine but would revert right back to the original after saving. The default also includes NAT setup... and DHCP settings... so just changing the bridge device doesn't fix it. I'll try the virt-install method... but since it is using libvirt just like virt-manager, I'm not expecting any different results... but we'll see. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] |
|
From: <ope...@li...> - 2010-03-03 21:06:37
|
Scott, 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. Regards, -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 03.03.2010, at 20:23, ope...@li... wrote: > Danel, > > ----- ope...@li... wrote: >> Just to mention. Libvirt community has a stand that scripts/configs >> under /etc/libvirt should be edited through libvirt methods (virsh for >> console access). >> >> Default networking can be changed with virsh the following way: >> virsh -c qemu:///system >> net-edit default >> #change bridge name in xml configuration that appeared >> >> This should help with consistency as there are probably syntax checks >> after editing and saving. > > Editing the default doesn't seem to help at all. Changing the bridge name would save fine but would revert right back to the original after saving. The default also includes NAT setup... and DHCP settings... so just changing the bridge device doesn't fix it. > > I'll try the virt-install method... but since it is using libvirt just like virt-manager, I'm not expecting any different results... but we'll see. > > TYL, > -- > Scott Dowdle > 704 Church Street > Belgrade, MT 59714 > (406)388-0827 [home] > (406)994-3931 [work] > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
|
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] |
|
From: <ope...@li...> - 2010-03-03 21:32:04
|
Hi scott, Try to run virsh -c qemu:///system start kvmdemo1 This should select correct libvirt driver to connect to. Without giving driver name virsh might try to connect other drivers. Danel On 03.03.2010, at 23:26, ope...@li... wrote: > 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] > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
|
From: <ope...@li...> - 2010-03-03 22:06:24
|
Danel, ----- ope...@li... wrote: > Try to run > > virsh -c qemu:///system start kvmdemo1 > > This should select correct libvirt driver to connect to. Without > giving driver name virsh might try to connect other drivers. Thanks, that is exactly what I needed. I was busy writing more emails to the mailing list and hadn't gotten that far. :) Works now! TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] |
|
From: <ope...@li...> - 2010-03-03 21:32:40
|
As there are 2 different hypervizors on OpenNode - then just to be sure execute: virsh --connect qemu:///session start kvmdemo1 You can now use also virt-manager - as bridge conf is stored into domain xml file already. -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 03.03.2010, at 23:26, ope...@li... wrote: > 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] > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X