WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] windows XP Guest network doesn't work

To: David Morris <david.morris@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] windows XP Guest network doesn't work
From: Martin Goldstone <m.j.goldstone@xxxxxxxxxxxxxxx>
Date: Thu, 30 Aug 2007 10:10:54 +0100
Delivery-date: Thu, 30 Aug 2007 02:11:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <76BB7F270C366D47AA79851BB0B39D8101A68EB5@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <76BB7F270C366D47AA79851BB0B39D8101A68EB5@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The MAC address for the Windows guest seems odd.  The Xen Wiki recommends:

- ---

Virtualised network interfaces in domains are given Ethernet MAC
addresses. By default xend will select a random address, this will
differ between instantiations of the domain. If it is required to have a
fixed MAC address for a domain (e.g. for using with DHCP) then this can
be configured using the mac= option to the vif configuration directive
(e.g. vif = ['mac=aa:00:00:00:00:11']).

When choosing MAC addresses to use, ensure you choose a unicast address.
That is, one with the low bit of the first octet set to zero. For
example, an address starting aa: is OK but ab: is not. It is best to
keep to the range of addresses declared to be "locally assigned" (rather
than allocated globally to hardware vendors). These have the second
lowest bit set to one in the first octet. For example, aa: is OK, a8: isn't.

In summary, an address of the following form should be OK:

XY:XX:XX:XX:XX:XX

where X is any hexadecimal digit, and Y is one of 2, 6, A or E.

- ---
(The full article is here: http://wiki.xensource.com/xenwiki/XenNetworking)

Your MAC starts with 11 - 00010001 in binary, which makes it a multicast
address (I think). Starting it with 12 would give 00010010, which I
think should be fine.  The MAC on the RH guest starts 00, which is also
unicast, but I don't think its defined as a locally administered MAC.

So far, that's the only thing I've noticed that could be problem.

I'd suggest trying changing the MAC and seeing if that has any effect.

Martin



David Morris wrote:
> Thanks for the followup ... the domUs were initially created using 
> virt-manager which gave me workable config files for this Xen version. I then 
> tweaked the files as needed and use xm to manipulate the VMs.
> 
> It appears the Xen is emulating a RealTek ethernet adapter, so I downloaded 
> the latest drivers for the 8139 device and created an iso which you will note 
> as the current CD. Unfortunately, windows couldn't correlate any of the 
> devices in the cd image with its view of the adapter. I forced the install 
> and the adapter didn't come up. I reverted the driver. 
> 
> Attachments:
>   infoOutput.txt -- script capture of the xenhost console as I was displaying 
>                     the configs, xm list outputs, ifconfig, brctl,            
>         
>                     and the current route table.
>   winxpTest      -- config file for the windows guest
>   dwm3           -- config file for my RHEL5 guest
>   winxpTestIPCONFIG.gif -- screen capture of ipconfig /all on win guest, also 
> ping and
>                     tracert output
>   dwm3PingTracert.gif   -- screen capture of ping test on the RH guest to 
> show that
>                     the basic environment routes to the ping target.
> 
> Dave Morris  
> 
> 
>> -----Original Message-----
>> From: Martin Goldstone [mailto:m.j.goldstone@xxxxxxxxxxxxxxx]
>> Sent: Wednesday, August 29, 2007 1:07 AM
>>
>> Are you creating the VMs through virt-install/virt-manager or 
>> using xm?
>>
>> Either way, can you post the config for the XP guest (either the file
>> used with xm or the output from 'virsh dumpxml <domID>')?
>>
>> Also, can you post the output from ifconfig and brctl show?
>>
>> Martin
>>
>> David Morris wrote:
>>> I have Xen 3.0.3 installed on RH EL5 via RedHat RPMs. 
>>>
>>> I have a Win/XP Pro HVM and a Linux rh5 HVM. I can create 
>> both w/o a problem and
>>> can interact with the VNC based console for both VMs.
>>>
>>> The Linux VM interacts via DHCP, obtains an IP and seems to 
>> work fine on the network.
>>> The Win/XP VM doesn't work with either DHCP or a static IP 
>> address assignment.
>>> I can see the virtual interfaces with 'brctl show' and 
>> don't recognize a difference.
>>> The hardware devices dialog on WinXP shows the network in the green.
>>>
>>> What am I missing here?
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG1omeRnwIDhcMR9MRAoT1AJ4vg6SYjv3ZQ5uv0HxjWaXKwru8OwCfVWt0
i50iStdr0ljY0HXat4NnsDc=
=47DW
-----END PGP SIGNATURE-----

Attachment: m.j.goldstone.vcf
Description: Vcard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users