Re: [Xen-users] Windows "modern.ie" Network Problem

[Wanderson Camargo <wandersonwhcr@xxxxxxxxx>]

I don't know why, but when I paste my source inside the forum editor, it prefix the mac with "1". My current vif configuration is:

vif = [ 'mac=13:D3:93:36:40:37,bridge=xenbr0,type=ioemu' ]

Yesterday I found a typo, "bridge-ports" is "bridge_ports", with underscore. I change it, but it didn't fix my problem.

I'll check my "auto eth0 [...]", thanks for the point.

My instance log:

$Âcat /var/log/xen/qemu-dm-ie9-win7.log

domid: 11

-c config qemu network with xen bridge forÂ

vif11.0-emu xenbr0

Using file /dev/vg0/ie9-win7 in read-write mode

Watching /local/domain/0/device-model/11/logdirty/cmd

Watching /local/domain/0/device-model/11/command

Watching /local/domain/11/cpu

char device redirected to /dev/pts/8

qemu_map_cache_init nr_buckets = 10000 size 4194304

shared page at pfn feffd

buffered io page at pfn feffb

Guest uuid = 7c0581f1-89c6-3ed2-42fc-863170f42d1e

Time offset set 0

populating video RAM at ff000000

mapping video RAM from ff000000

Register xen platform.

Done register platform.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

xs_read(/local/domain/0/device-model/11/xen_extended_power_mgmt): read error

xs_read(): vncpasswd get error. /vm/7c0581f1-89c6-3ed2-42fc-863170f42d1e/vncpasswd.

Log-dirty: no command yet.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

vcpu-set: watch node error.

char device redirected to /dev/pts/9

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xs_read(/local/domain/11/log-throttling): read error

qemu: ignoring not-understood drive `/local/domain/11/log-throttling'

medium change watch on `/local/domain/11/log-throttling' - unknown device, ignored

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

vga s->lfb_addr = f0000000 s->lfb_end = f1000000Â

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

mapping vram to f0000000 - f1000000

Unknown PV product 2 loaded in guest

PV driver build 1

region type 1 at [c100,c200).

region type 0 at [f2000000,f2000100).

squash iomem [f1000000, f2000000).

vga s->lfb_addr = f0000000 s->lfb_end = f1000000Â

vga s->lfb_addr = f0000000 s->lfb_end = f1000000

Verifying it, qemu opens a vif named "vif11.0-emu". But when I execute "ifconfig" after "xm create", there's not interface named like that.

$ ifconfigÂvif11.0-emu

vif11.0-emu: error fetching interface information: Device not found

There's a VNC password error, so I need to configure it.

We can see a lot of console errors. I'll find a way to disable it.

My current configuration source is:

$ cat /etc/xen/ie9-win7.cfg | grep -v '^$'

kernel = '/usr/lib/xen-4.1/boot/hvmloader'

builder = 'hvm'

vcpus = '1'

memory = '2048'

name = 'ie9-win7'

vnc = '1'

vif = [ 'mac=13:D3:93:36:40:37,bridge=xenbr0,type=ioemu' ]

vfb = [ 'vnclisten=0.0.0.0,vncpasswd=123456,vncdisplay=90' ]

stdvga=1

videoram=16

disk = [

'phy:/dev/vg0/ie9-win7,hda,w'

]

acpi = '1'

sdl = '0'

serial = 'pty'

device_model = 'qemu-dm'

usb = 1

usbdevice = 'tablet'

boot = 'c'

About network interfaces:

Domain-0:

$ lspci | grep Ethernet

01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20)

01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet (rev 20)

ie9-win7:

ipconfig /all

[...]

Description ... : Realtek RTL9139C+ Fast Ethernet NIC

[...]

The network is configured with DHCP. If I configure it manually, network keeps with the same problem.

Thinking about that, there's a way to check if my guest is configured with NAT instead of bridge?

--
Wanderson Henrique Camargo Rosa

http://www.wanderson.camargo.nom.br/

On Tue, Jan 20, 2015 at 7:53 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

On Mon, 2015-01-19 at 17:03 -0200, Wanderson Camargo wrote:

> vif = [ 'mac=133:93:36:40:37,bridge=xenbr0,type=ioemu' ]

Not sure if will be the issue, but 133 is not a valid value for a byte
in a mac address. I don't know if this will fail or silently truncate or
what.

You might also find some interesting data in the logs
under /var/log/xen.

> auto eth0
> iface eth0 inet manual

You can drop this, since the xenbr0 stanza will do it, although I doubt
this relates to your issue.

The other thing to check is the in-guest network device configuration,
firstly is it detected at all and secondly for static vs DHCP type
issues.

Ian.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users