Skip to main content

linux - Setting up Windows network on Xen



I'm trying to install a Windows XP server in a Xen environment. The OS is booting fine. Unfortunately I can't figure out how to set up the network settings.



Dom0 is a Debian Lenny currently hosting around 10 Linux virtual servers.



Windows tells me I have a "limited connection". It can't get any DHCP response, nor access other hosts in the network




Here is the Xen's client config file:




kernel = '/usr/lib/xen-3.2-1/boot/hvmloader'
builder = 'hvm'
memory = '1024'
device_model='/usr/lib/xen-3.2-1/bin/qemu-dm'
acpi=1
apic=1
pae=1

vcpus=1
name = 'winexchange'
# Disks
disk = [
'phy:/dev/wnghosts/exchange-disk,ioemu:hda,w',
'file:/mnt/freespace/ISO/DVD1_Installation.iso,ioemu:hdc:cdrom,r'
]
# Networking
vif = [ 'mac=00:16:3E:0A:D0:1B, type=ioemu, bridge=xenbr0']
# video

stdvga=0
serial='pty'
ne2000=0
# Behaviour
boot='c'
sdl=0
# VNC
vfb = [ 'type=vnc' ]
vnc=1
vncdisplay=1

vncunused=1
usbdevice='tablet'



  • Server config (/etc/xen/xend-config.sxp)




(network-script network-bridge)

(vif-script vif-bridge)
(dom0-min-mem 512)
(dom0-cpus 0)
(vnc-listen '0.0.0.0')


ifconfig (cleaned up):




eth0 Link encap:Ethernet HWaddr 00:30:48:c7:90:34

inet addr:10.20.10.9 Bcast:10.20.255.255 Mask:255.255.0.0
inet6 addr: fe80::230:48ff:fec7:9034/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9124214 errors:0 dropped:0 overruns:0 frame:0
TX packets:5560279 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1501725024 (1.3 GiB) TX bytes:3721460671 (3.4 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8700 (8.4 KiB) TX bytes:8700 (8.4 KiB)

peth0 Link encap:Ethernet HWaddr 00:30:48:c7:90:34
inet6 addr: fe80::230:48ff:fec7:9034/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1

RX packets:2574257469 errors:1 dropped:0 overruns:0 frame:1
TX packets:1798883882 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2351005981 (2.1 GiB) TX bytes:3255923331 (3.0 GiB)
Memory:de220000-de240000

tap0 Link encap:Ethernet HWaddr 00:ff:e8:e4:b1:43
inet6 addr: fe80::2ff:e8ff:fee4:b143/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:8205 (8.0 KiB) TX bytes:468 (468.0 B)

vif116.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1854 overruns:0 carrier:0
collisions:0 txqueuelen:32

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


The xm-network list command gave me an unusual output:




# xm network-list winxp01
Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path
0 0 00:16:3E:0A:D0:1C 0 1 -1 -1 /-1 /local/domain/0/backend/vif/116/0



What do these elements stand for? "state evt-ch tx-/rx-ring-ref"



What did I do wrong?
Please tell me if you want some more info (logs, etc)


Answer



Found after three weeks of searching.



Had to download some "Xen" network driver here: http://www.meadowcourt.org/downloads/




Pfew... glad it's resolved.


Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able