To my pleasure, I was able to get two different virtual machines running pretty quickly. I installed Fedora 10 x86_64 on my new laptop with the Virtualization package group and as little else as possible. Then I updated the system (so now I''m using kvm-74-6-fc10.x86_64), started the graphical Virtual Machine Manager, and built a guest for Windows XP Professional and a second guest for Fedora 10 x86_64. I want the Fedora 10 guest to fetch an IP address of 192.168.1.115 from the dhcp server running on my network. Virtual Machine Manager seems to be creating it''s very own dhcp server and assigning network addresses of 192.168.122.2 and higher. So I can''t ping the guest I just created from a host on the 192.168.1.0 network. The networking behavior VMWare gives me results in my virtual machines getting their addresses from the dhcp server on the 192.168.1.0 network, so the host IP I''m expecting for a machine is the one that is assigned and used. How do I change the networking in Virtual Machine Manager to simply pass all the dhcp calls to my network? Or is there a good reason to let the Manager do its own 192.168.122.x network? Thanks Bob Cochran
On Sat, Dec 13, 2008 at 10:33 PM, Robert L Cochran <cochranb@speakeasy.net> wrote:> To my pleasure, I was able to get two different virtual machines running > pretty quickly. I installed Fedora 10 x86_64 on my new laptop with the > Virtualization package group and as little else as possible. Then I > updated the system (so now I''m using kvm-74-6-fc10.x86_64), started the > graphical Virtual Machine Manager, and built a guest for Windows XP > Professional and a second guest for Fedora 10 x86_64. > > I want the Fedora 10 guest to fetch an IP address of 192.168.1.115 from > the dhcp server running on my network. Virtual Machine Manager seems to > be creating it''s very own dhcp server and assigning network addresses of > 192.168.122.2 and higher. So I can''t ping the guest I just created from > a host on the 192.168.1.0 network. > > The networking behavior VMWare gives me results in my virtual machines > getting their addresses from the dhcp server on the 192.168.1.0 network, > so the host IP I''m expecting for a machine is the one that is assigned > and used. > > How do I change the networking in Virtual Machine Manager to simply pass > all the dhcp calls to my network? Or is there a good reason to let the > Manager do its own 192.168.122.x network? >I don''t know specifically about Virtual Machine Manager and don''t have it handy, but for the basic concepts of KVM networking and also the libvirt style and nomenclature see the following links: http://wiki.libvirt.org/page/Networking http://kvm.qumranet.com/kvmwiki/Networking The Virtual Machine Manager page may have some information that could help you: http://virt-manager.et.redhat.com/screenshots/networking.html Hope that helps. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com
Todd Deshane wrote:> On Sat, Dec 13, 2008 at 10:33 PM, Robert L Cochran > <cochranb@speakeasy.net> wrote: > >> To my pleasure, I was able to get two different virtual machines running >> pretty quickly. I installed Fedora 10 x86_64 on my new laptop with the >> Virtualization package group and as little else as possible. Then I >> updated the system (so now I''m using kvm-74-6-fc10.x86_64), started the >> graphical Virtual Machine Manager, and built a guest for Windows XP >> Professional and a second guest for Fedora 10 x86_64. >> >> I want the Fedora 10 guest to fetch an IP address of 192.168.1.115 from >> the dhcp server running on my network. Virtual Machine Manager seems to >> be creating it''s very own dhcp server and assigning network addresses of >> 192.168.122.2 and higher. So I can''t ping the guest I just created from >> a host on the 192.168.1.0 network. >> >> The networking behavior VMWare gives me results in my virtual machines >> getting their addresses from the dhcp server on the 192.168.1.0 network, >> so the host IP I''m expecting for a machine is the one that is assigned >> and used. >> >> How do I change the networking in Virtual Machine Manager to simply pass >> all the dhcp calls to my network? Or is there a good reason to let the >> Manager do its own 192.168.122.x network? >> >> > > I don''t know specifically about Virtual Machine Manager and don''t have it > handy, but for the basic concepts of KVM networking and also the libvirt > style and nomenclature see the following links: > > http://wiki.libvirt.org/page/Networking > http://kvm.qumranet.com/kvmwiki/Networking > > The Virtual Machine Manager page may have some information that > could help you: > > http://virt-manager.et.redhat.com/screenshots/networking.html > > Hope that helps. > > Cheers, > Todd > >Todd, Thank you. This is very useful and helpful. It looks like I need to configure bridged networking. From the Fedora 10 release notes, Network Manager does not support virtual devices, so I''ll have to disable it and roll my own. Bob
hi Robert, On Sun, Dec 14, 2008 at 4:33 AM, Robert L Cochran <cochranb@speakeasy.net>wrote:> How do I change the networking in Virtual Machine Manager to simply pass > all the dhcp calls to my network? Or is there a good reason to let the > Manager do its own 192.168.122.x network? >I''m not using Fedora 10 but Pardus. Nevertheless, I had a similar problem with bridged networking, I couldn''t get it to work with Virtual Machine Manager. Maybe the support was missing from my version. Basically, what you need to do is: 1) Create a network bridge 2) Create an ifup script 3) when starting kvm, start it with tap networking and then use the script (2) to add that tap adapter to the bridge (1). I use qtemu svn as a graphic frontend, until things get easier with Virt-Manager, with this bridged networking and virtio stuff. Emre
Robert L Cochran wrote:> Todd Deshane wrote: > >> On Sat, Dec 13, 2008 at 10:33 PM, Robert L Cochran >> <cochranb@speakeasy.net> wrote: >> >> >>> To my pleasure, I was able to get two different virtual machines running >>> pretty quickly. I installed Fedora 10 x86_64 on my new laptop with the >>> Virtualization package group and as little else as possible. Then I >>> updated the system (so now I''m using kvm-74-6-fc10.x86_64), started the >>> graphical Virtual Machine Manager, and built a guest for Windows XP >>> Professional and a second guest for Fedora 10 x86_64. >>> >>> I want the Fedora 10 guest to fetch an IP address of 192.168.1.115 from >>> the dhcp server running on my network. Virtual Machine Manager seems to >>> be creating it''s very own dhcp server and assigning network addresses of >>> 192.168.122.2 and higher. So I can''t ping the guest I just created from >>> a host on the 192.168.1.0 network. >>> >>> The networking behavior VMWare gives me results in my virtual machines >>> getting their addresses from the dhcp server on the 192.168.1.0 network, >>> so the host IP I''m expecting for a machine is the one that is assigned >>> and used. >>> >>> How do I change the networking in Virtual Machine Manager to simply pass >>> all the dhcp calls to my network? Or is there a good reason to let the >>> Manager do its own 192.168.122.x network? >>> >>> >>> >> I don''t know specifically about Virtual Machine Manager and don''t have it >> handy, but for the basic concepts of KVM networking and also the libvirt >> style and nomenclature see the following links: >> >> http://wiki.libvirt.org/page/Networking >> http://kvm.qumranet.com/kvmwiki/Networking >> >> The Virtual Machine Manager page may have some information that >> could help you: >> >> http://virt-manager.et.redhat.com/screenshots/networking.html >> >> Hope that helps. >> >> Cheers, >> Todd >> >> >> > Todd, > > Thank you. This is very useful and helpful. It looks like I need to > configure bridged networking. From the Fedora 10 release notes, Network > Manager does not support virtual devices, so I''ll have to disable it and > roll my own. > > Bob >I have it working, thanks very much! The XML format stuff was quite helpful ( --> http://libvirt.org/formatdomain.html#elementsNICS ) Bob