All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2519737 ] DHCP/NAT: Vista fails to get IP from NAT engine
Date: Wed, 21 Jan 2009 07:06:13 +0000	[thread overview]
Message-ID: <E1LPXAD-0002t7-TR@665xhf1.ch3.sourceforge.com> (raw)

Bugs item #2519737, was opened at 2009-01-19 22:07
Message generated for change (Comment added) made by danv
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2519737&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Technologov (technologov)
Assigned to: Nobody/Anonymous (nobody)
Summary: DHCP/NAT: Vista fails to get IP from NAT engine

Initial Comment:

Host: Fedora7/x64, KVM-83, Intel Core 2
Guest: Windows Vista 32-bit

Problem: When I use userspace networking - Qemu NAT engine with DHCP - Vista VM fails to reconginze it.

The only way for Vista to work is to manually set IP address:
IP: 10.0.2.2
Gateway: 10.0.2.15
DNS: 10.0.2.3

This problem does not happen with Windows XP VM.
It happens with older KVMs too... tested since KVM-75...

./qemu-kvm -hda /isos/disks-vm/alexeye/WindowsVista-32-mypc.qcow2 -m 512 -snapshot -name Vista-32-mypc

-Alexey, 19.1.2008.

----------------------------------------------------------------------

Comment By: Daniel van Vugt (danv)
Date: 2009-01-21 16:06

Message:
I've found this problem is common (but not consistent) on both Vista and
Windows 7 guests, using kvm-82 and kvm-83, with rtl8139, e1000 or virtio.
There's something about these specific Windows releases that breaks with
KVM/QEMU DHCP.

----------------------------------------------------------------------

Comment By: Technologov (technologov)
Date: 2009-01-20 00:35

Message:
Since this also happens with -no-kvm , I opened a similar bug in Qemu
bugzilla:
https://bugs.launchpad.net/qemu/+bug/318824

----------------------------------------------------------------------

Comment By: Technologov (technologov)
Date: 2009-01-20 00:25

Message:
Same happens with -no-kvm (Qemu) and with e1000 NIC (instead of RTL8139).

----------------------------------------------------------------------

Comment By: Technologov (technologov)
Date: 2009-01-19 22:08

Message:
btw: NAT itself works - after IPs are manually configured. Emulated NIC is
RTL8139.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2519737&group_id=180599

             reply	other threads:[~2009-01-21  7:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  7:06 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-03 10:09 [ kvm-Bugs-2519737 ] DHCP/NAT: Vista fails to get IP from NAT engine SourceForge.net
2009-01-21  7:42 SourceForge.net
2009-01-19 15:35 SourceForge.net
2009-01-19 15:25 SourceForge.net
2009-01-19 13:08 SourceForge.net
2009-01-19 13:07 SourceForge.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LPXAD-0002t7-TR@665xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.