[Xen-bugs] [Bug 1468] New: Wrong use of vnclisten="xx.xx.xx.xx"

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1468

           Summary: Wrong use of vnclisten="xx.xx.xx.xx"
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: winxent1@xxxxxxxxx


When specifiying a ip-address that does not belong to the dom0 machine in
/etc/xen/domU.conf, the machine locks up when trying to start that domU with
'xm create domU.cfg'

I am using xen 3.4.0 and 2.6.18.8-xen

/var/log/kern.log:

May 22 23:02:21  kernel: PM: Adding info for xen-backend:vfb-3-0
May 22 23:02:21  kernel: PM: Adding info for xen-backend:vbd-3-768
May 22 23:02:21  kernel: PM: Adding info for xen-backend:vbd-3-5632
May 22 23:02:21  kernel: PM: Adding info for xen-backend:vif-3-0
May 22 23:02:21  kernel: device vif3.0 entered promiscuous mode
May 22 23:02:21  kernel: audit(1243026141.680:11): dev=vif3.0 prom=256
old_prom=0 auid=4294967295
May 22 23:02:21  kernel: eth0: port 2(vif3.0) entering learning state
May 22 23:02:21  kernel: eth0: topology change detected, propagating
May 22 23:02:21  kernel: eth0: port 2(vif3.0) entering forwarding state
May 22 23:02:21  kernel: PM: Adding info for xen-backend:pci-3-0
May 22 23:02:21  kernel: device tap3.0 entered promiscuous mode
May 22 23:02:21  kernel: audit(1243026141.730:12): dev=tap3.0 prom=256
old_prom=0 auid=4294967295
May 22 23:02:21  kernel: eth0: port 3(tap3.0) entering disabled state
May 22 23:02:21  kernel: device tap3.0 left promiscuous mode
May 22 23:02:21  kernel: audit(1243026141.870:13): dev=tap3.0 prom=0
old_prom=256 auid=4294967295
May 22 23:02:21  kernel: eth0: port 3(tap3.0) entering disabled state
May 22 23:02:21  kernel: Unable to handle kernel NULL pointer dereference at
0000000000000008 RIP:
May 22 23:02:21  kernel: [<ffffffff8023ffb5>] run_workqueue+0x70/0xec
May 22 23:02:21  kernel: PGD 1ef4c4067 PUD 1edd54067 PMD 0
May 22 23:02:21  kernel: Oops: 0002 [1] SMP
May 22 23:02:21  kernel: CPU 2
May 22 23:02:21  kernel: Modules linked in: xt_tcpudp xt_state ip_conntrack
nfnetlink xt_physdev tun iptable_filter ip_tables x_tables bridge ppdev
parport_pc lp parport ipv6 i2c_i801 pcspkr usbhid serio_raw i2c_core ext3 jbd
dm_mirror dm_snapshot dm_mod raid1 sg sd_mod sr_mod cdrom ahci floppy uhci_hcd
libata scsi_mod ehci_hcd usbcore e1000e thermal processor fan pciback
May 22 23:02:21  kernel: Pid: 16, comm: events/2 Tainted: GF     2.6.18.8-xen
#1
May 22 23:02:21  kernel: RIP: e030:[<ffffffff8023ffb5>]  [<ffffffff8023ffb5>]
run_workqueue+0x70/0xec
May 22 23:02:21  kernel: RSP: e02b:ffff8801ef633e40  EFLAGS: 00010006
May 22 23:02:21  kernel: RAX: 0000000000000000 RBX: ffff8801f0e78548 RCX:
0000000300000000
May 22 23:02:21  kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI:
ffff8801efaa3640
May 22 23:02:21  kernel: RBP: ffff8801efaa3640 R08: 0000000000000000 R09:
0000000000000014
May 22 23:02:21  kernel: R10: ffff8801f08f7800 R11: ffff8801f08f7940 R12:
ffff8801f0e78540
May 22 23:02:21  kernel: R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000000
May 22 23:02:21  kernel: FS:  00002ab93df30380(0000) GS:ffffffff804dc100(0000)
knlGS:0000000000000000
May 22 23:02:21  kernel: CS:  e033 DS: 0000 ES: 0000
May 22 23:02:21  kernel: Process events/2 (pid: 16, threadinfo
ffff8801ef632000, task ffff8801ef6117e0)
May 22 23:02:21  kernel: Stack:  0000000000000000 ffff8801efaa3680
ffff8801efaa3658 ffff8801efaa3640
May 22 23:02:21  kernel: ffff8801efaa3658 ffff8801efaa3668 0000000000000000
0000000000000001
May 22 23:02:21  kernel: 0000000000000000 ffffffff8024013c 0000000000000000
ffff8801ef6117e0
May 22 23:02:21  kernel: Call Trace:
May 22 23:02:21  kernel: [<ffffffff8024013c>] worker_thread+0x10b/0x142
May 22 23:02:21  kernel: [<ffffffff80228ba0>] default_wake_function+0x0/0xe
May 22 23:02:21  kernel: [<ffffffff80240031>] worker_thread+0x0/0x142
May 22 23:02:21  kernel: [<ffffffff80243884>] kthread+0xd4/0x108
May 22 23:02:21  kernel: [<ffffffff8020b070>] child_rip+0xa/0x12
May 22 23:02:21  kernel: [<ffffffff80214927>] xen_send_IPI_mask+0x0/0x11e
May 22 23:02:21  kernel: [<ffffffff80240031>] worker_thread+0x0/0x142
May 22 23:02:21  kernel: [<ffffffff802437b0>] kthread+0x0/0x108
May 22 23:02:21  kernel: [<ffffffff8020b066>] child_rip+0x0/0x12
May 22 23:02:21  kernel:
May 22 23:02:21  kernel:
May 22 23:02:21  kernel: Code: 48 89 42 08 48 89 10 48 89 5b 08 48 89 1b e8 a8
fd 1b 00 49
May 22 23:02:21  kernel: RIP  [<ffffffff8023ffb5>] run_workqueue+0x70/0xec
May 22 23:02:21  kernel: RSP <ffff8801ef633e40>
May 22 23:02:21  kernel: CR2: 0000000000000008

'xm info':

host                   : mainframe
release                : 2.6.18.8-xen
version                : #1 SMP Thu May 21 13:32:44 CEST 2009
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2826
hw_caps                :
bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 8189
free_memory            : 9
node_to_cpu            : node0:0-3
node_to_memory         : node0:9
xen_major              : 3
xen_minor              : 4
xen_extra              : .0
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by          : root
cc_compile_domain      : local
cc_compile_date        : Thu May 21 12:11:11 CEST 2009
xend_config_format     : 4


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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