qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows Update on guest
Date: Tue, 23 Nov 2004 00:05:26 +1300	[thread overview]
Message-ID: <1101121526.3726.4.camel@localhost.localdomain> (raw)
In-Reply-To: <16801.49902.808845.86465@client83.comlab>

[-- Attachment #1: Type: text/plain, Size: 2972 bytes --]

Hi William,

    I have successfully used Windows Update for both a Windows 98 guest
and Windows 2003 guest (Linux host).  I have posted to this list
previously the setup that I use, but briefly:
tun/tap enabled in host kernel (most distros this is a default)
run qemu with -n qemu-ifup
contents of qemu-ifup:
#!/bin/bash

/sbin/iptables --flush      #Clear out all old rules.  You will want to
customise this step.

echo 1 >/proc/sys/net/ipv4/ip_forward       #Enable IP Forwarding for
the host OS

/sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE   #Enable
MASQUERADEing on the real eth0 NIC

/sbin/ifconfig $1 192.168.0.254         #Bring up tun0 - guest OS NIC
should be on the same subnet with
                                        #a different address; tun0
should be its gateway.


After that just manually configure your guest to use a static IP address
and some external DNS servers and you're away.

Cheers,
D

On Mon, 2004-11-22 at 10:43 +0000, William Greenland wrote:

> Well, I've tried various versions, including the 0.6.0 and 0.6.1
> snapshots, and the CVS over the last couple of months.  Admittedly, I
> haven't tried the very recent slirp patch you refer to, but then the
> problem remains the same with tun/tap networking.
> 
> Anyway, I'm doubtful that this is just an "off by one" downloading
> error, particularly since I have no problems downloading files.
> 
> I think that this issue is a more general networking one.  Do QEMU
> processes appear on the network "exactly like machines"?  If so, it
> could well be that the problem is not with QEMU, but with the host
> providing the network connection.
> 
> I will try the slirp patch and see if it helps.  But still, if anyone
> HAS got Windows Update to work, I'd be interested to hear about it.
> 
> I'd really like to have a detailed account of a working Linux host /
> MS guest setup, with complete details (for example) of what networking
> options are enabled in the host kernel, etc.
> 
> Thanks,
> Will.
> 
> Hetz Ben Hamo writes:
>  > Hi William,
>  > 
>  > Which version of QEMU have you tried? I would suggest to try the
>  > latest CVS or a snapshot from my web site since there was a networking
>  > bug which Fabrice fixed yesterday, and that should let you use the
>  > windows update.
>  > 
>  > Thanks,
>  > Hetz
>  > 
>  > > Has anyone had any success running "Windows Update" via IE on (any)
>  > > MS guest?  I'm using a (Gentoo) Linux host, and I've tried all the
>  > > networking configurations I can think of.
>  > > 
>  > > Is this even the kind of thing that *should* be working at the moment?
>  > > 
>  > > If anyone has this working with a similar setup, I'd be VERY glad to
>  > > hear details of how they set up networking.
>  > > 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 5218 bytes --]

  reply	other threads:[~2004-11-22 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 10:05 [Qemu-devel] Windows Update on guest William Greenland
2004-11-22 10:14 ` Hetz Ben Hamo
2004-11-22 10:43   ` William Greenland
2004-11-22 11:05     ` Darryl Dixon [this message]
2004-11-23  9:26       ` William Greenland
2004-11-22 14:21 ` Joshua Root
     [not found] <41A21B63.2070104@acwsinc.net>
2004-11-22 19:20 ` Darryl Dixon

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=1101121526.3726.4.camel@localhost.localdomain \
    --to=esrever_otua@pythonhacker.is-a-geek.net \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).