Re: qemu-kvm: qns regarding network and usb keyboard setup

2009/2/17 Bill Davidsen <davidsen@xxxxxxx>:
suvayu ali wrote:

Hi all,

Recently I started experimenting with kvm with F10 as the host, and I
have been having some problems.

I need to login to my virtual machine from the shell from the host
itself and/or from another machine remotely over the internet. I went
through the man pages but couldn't make anything out of it. I am a
newbie so could someone please point me to a resource where I can read
up more on this which is a little more understandable?

No.

On the other hand I can tell you what I did, a better way to do it (which I
didn't know when I started), and it should get you started. You may have joy
from virt-manager, it's on my list of things to try when I have time to look
at better solutions to problems to problems for which I have an ugly working
solution.

The secret is to have your NIC attached to a bridge on the host, and use
that for networking. So instead of having eth0 be your device for default
route, you have the bridge, and the physical bridge is attached to the
bridge. Now you can use either a fixed IP or a known DHCP assigned IP for
your virtual machine.

I have: NIC(eth0)---[bridge(br0)]---default route

I don't quite follow you here.

Start the kvm machine with: "-net nic,macaddr=$MAC -net tap" to do DHCP IP
assignment, or "-net nic -net tap" to use a static IP or random IP from
DHCP.
I run my own DNS, DHCP, mail, http, so I can control everything, but you may
not wish to do so.

The better way: I have seen posted the suggestion that you name the NIC
"peth0" and the bridge "eth0" to make the default Fedora firewall and
routing work. Haven't tried it.

Hope this gets you started, I read the kvm list and I just beat on it until
it worked "back when" without much doc, and haven't changed anything.

When I tried "-net nic -net tap", I get this error,

/etc/qemu-ifup: could not launch network script
Could not initialize device 'tap'

So I tried just using nic, that did boot up the system but I did not
have any network connection. I tried using macaddr=<my active
network>, that too ended up with no network. I don't know whether this
is relevant, I have 2 network cards but none of them are in use. I
have to use a USB wifi receiver to connect to the internet. (don't ask
why, its because of the landlord). So the macaddr I used was for the
wifi receiver (wlan0).

Without either of those the machine boots up with network access and I
can log into the system using the gui. I can do system updates and
browse the internet, however when i try to (from the host) ping the ip
I get from ifconfig on the guest, there is 100% packet loss.

I hope I am not doing something stupid ... :-o

--
Suvayu

Open source is the future. It sets us free.

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Relevant Pages

  • kvm hypervisor host network problem during VM startup/shutdown
    ... I have been running kvm on this host for almost two years now. ... There is one bridge, br1 (there is an unused br0 which has no connection ... providing DHCP to the whole network. ... Every time, the hypervisor briefly (5-10 ...
    (Debian-User)
  • Re: Win2K3E & Multiple NICs
    ... When you install VPC or Virtual Server, extra code is added to the device drivers for the NICs in the host. ... Ther extra code reroutes packets addressed to a vm to the the OS running in the vm, not the network stack in the host. ... Bearing in mind I'm only just starting to get a handle on Microsoft's virtual machine app, my impression of the virtual environment is that I can set up actual, physical NICs on the server that go to entirely different network segments then bind a virtual machine to those separate NICs. ...
    (microsoft.public.windows.server.networking)
  • Re: qemu-kvm: qns regarding network and usb keyboard setup
    ... Recently I started experimenting with kvm with F10 as the host, ... So instead of having eth0 be your device for default route, you have the bridge, and the physical bridge is attached to the bridge. ... Now you can use either a fixed IP or a known DHCP assigned IP for your virtual machine. ... Hope this gets you started, I read the kvm list and I just beat on it until it worked "back when" without much doc, and haven't changed anything. ...
    (Fedora)
  • Re: [opensuse] VirtualBox bridged connection in OpenSuse 10.3
    ... Virtualbox 1.6 host networking doesn't work correctly ... I have tried to add eth0 to the bridge: ... Then restarted network and lost inet on the host system (even without ...
    (SuSE)
  • Re: New Machine on Network Cant See Other Machines Files
    ... the network at the same time. ... I am configuring the new machine as a Virtual PC host, ... >> (and then eventually a second virtual machine) running under that host ... >> Greg Dunn ...
    (microsoft.public.windowsxp.security_admin)