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-bugs

[Xen-bugs] [Bug 1628] New: xen networking does not work

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1628] New: xen networking does not work
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 28 Jun 2010 06:30:18 -0700
Delivery-date: Mon, 28 Jun 2010 06:30:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1628

           Summary: xen networking does not work
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: darkbasic4@xxxxxxxxx


I pulled latest version of xen-4.0-testing and both 2.6.32 and 2.6.31 git
kernels.

With kernel 2.6.32 networking is very problematic: the vast majority of times I
get a backtrace and I cannot start another domU.
Anyway, if I can start the domU the networking (bridge) works.

With 2.6.31 I never managed to boot the domU and I get the following backtrace.
I also tried netchannel2 but it does not work too (please see
http://permalink.gmane.org/gmane.comp.emulators.xen.user/59780)

This is the config:
memory = 1000

vif = ['bridge=eth0']

disk =  [
       'tap2:tapdisk:aio:/srv/xen/webserver2.img,hda,w',
#       'file:/root/debian-testing-amd64-businesscard.iso,hdc:cdrom,r',
#       'phy:/dev/cdrom,hdc:cdrom,r',
       ]

#boot = "dc"
#device_model = '/usr/lib/xen/bin/qemu-dm'
#kernel = "/usr/lib/xen/boot/hvmloader"
#builder='hvm'
#sdl=0
#vnc=1
#vnclisten="0.0.0.0"
#vncpasswd=''

kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0,0)/boot/grub/menu.lst"




root@dom0-firewall:~# xm create /srv/xen/profiles/prova.cfg -c
Using config file "/srv/xen/profiles/prova.cfg".

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.968631] Oops: 0000 [#1] SMP 

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.968729] last sysfs file: /sys/devices/vif-2-0/uevent

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.971447] Stack:

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.972058] Call Trace:

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.972734] Code: 1b 66 45 81 55 48 89 f5 53 48 89 fb 48 83 ec 18 65
48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8b 87 c8 00 00 00 48 8b 77 08
<4c> 8b 60 08 31 ff e8 30 6c ff ff 49 89 c5 48 3d 00 f0 ff ff 76 

Message from syslogd@dom0-firewall at Jun 28 15:04:00 ...
 kernel:[  123.974651] CR2: 0000000000000008
root@dom0-firewall:~# tail -50 /var/log/messages 
Jun 28 15:02:57 dom0-firewall kernel: [   60.221063] blktap_ring_mmap: blktap:
mapping pid is 1638
Jun 28 15:02:57 dom0-firewall kernel: [   60.221083] blktap_validate_params:
aio:/srv/xen/webserver2.img: capacity: 20971520, sector-size: 512
Jun 28 15:02:57 dom0-firewall kernel: [   60.221088] blktap_validate_params:
aio:/srv/xen/webserver2.img: capacity: 20971520, sector-size: 512
Jun 28 15:02:57 dom0-firewall kernel: [   60.221092] blktap_device_create:
minor 0 sectors 20971520 sector-size 512
Jun 28 15:02:57 dom0-firewall kernel: [   60.221217] blktap_device_create:
creation of 254:0: 0
Jun 28 15:02:57 dom0-firewall kernel: [   60.921488] blkback: ring-ref 2047,
event-channel 4, protocol 1 (x86_64-abi)
Jun 28 15:03:58 dom0-firewall kernel: [  121.314577] blktap_device_destroy:
destroy device 0 users 0
Jun 28 15:03:58 dom0-firewall kernel: [  121.741044] blktap_ring_vm_close:
unmapping ring 0
Jun 28 15:03:58 dom0-firewall kernel: [  121.741056] blktap_ring_release:
freeing device 0
Jun 28 15:04:00 dom0-firewall kernel: [  123.929283]
blktap_control_allocate_tap: allocated tap ffff88016db87800
Jun 28 15:04:00 dom0-firewall kernel: [  123.930148] blktap_ring_open: opening
device blktap0
Jun 28 15:04:00 dom0-firewall kernel: [  123.930153] blktap_ring_open: opened
device 0
Jun 28 15:04:00 dom0-firewall kernel: [  123.930168] blktap_ring_mmap: blktap:
mapping pid is 1779
Jun 28 15:04:00 dom0-firewall kernel: [  123.930184] blktap_validate_params:
aio:/srv/xen/webserver2.img: capacity: 20971520, sector-size: 512
Jun 28 15:04:00 dom0-firewall kernel: [  123.930187] blktap_validate_params:
aio:/srv/xen/webserver2.img: capacity: 20971520, sector-size: 512
Jun 28 15:04:00 dom0-firewall kernel: [  123.930191] blktap_device_create:
minor 0 sectors 20971520 sector-size 512
Jun 28 15:04:00 dom0-firewall kernel: [  123.968504] PGD 16ec35067 PUD
16d88a067 PMD 0 
Jun 28 15:04:00 dom0-firewall kernel: [  123.968779] CPU 0 
Jun 28 15:04:00 dom0-firewall kernel: [  123.968849] Modules linked in: bridge
stp xenfs blktap xen_evtchn loop firewire_sbp2 snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer joydev evdev snd
i2c_i801 i2c_core soundcore snd_page_alloc pcspkr psmouse button serio_raw
shpchp pci_hotplug wmi processor acpi_processor ext4 mbcache jbd2 crc16 usbhid
hid sd_mod crc_t10dif ata_generic ahci firewire_ohci megaraid_sas pata_via tg3
ata_piix firewire_core crc_itu_t libata libphy uhci_hcd ehci_hcd thermal r8169
mii thermal_sys usbcore nls_base scsi_mod [last unloaded: scsi_wait_scan]
Jun 28 15:04:00 dom0-firewall kernel: [  123.970616] Pid: 498, comm: udevd Not
tainted 2.6.31.13 #1 To Be Filled By O.E.M.
Jun 28 15:04:00 dom0-firewall kernel: [  123.970684] RIP:
e030:[<ffffffff8124e230>]  [<ffffffff8124e230>] netback_uevent+0x34/0xd5
Jun 28 15:04:00 dom0-firewall kernel: [  123.970779] RSP: e02b:ffff88016e16fda8
 EFLAGS: 00010246
Jun 28 15:04:00 dom0-firewall kernel: [  123.970829] RAX: 0000000000000000 RBX:
ffff88016d918400 RCX: 0000000000000000
Jun 28 15:04:00 dom0-firewall kernel: [  123.970882] RDX: ffffffff8145661b RSI:
ffff88016d9185c0 RDI: ffff88016d918400
Jun 28 15:04:00 dom0-firewall kernel: [  123.970935] RBP: ffff88016e144000 R08:
0000000000000002 R09: 0000000000000000
Jun 28 15:04:00 dom0-firewall kernel: [  123.970989] R10: 0000000000000401 R11:
00000000000286ec R12: ffff88017203e120
Jun 28 15:04:00 dom0-firewall kernel: [  123.971042] R13: ffff88016d918450 R14:
ffff88012803f000 R15: ffffffff81507550
Jun 28 15:04:00 dom0-firewall kernel: [  123.971097] FS: 
00007f5a46bf77a0(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
Jun 28 15:04:00 dom0-firewall kernel: [  123.971166] CS:  e033 DS: 0000 ES:
0000 CR0: 000000008005003b
Jun 28 15:04:00 dom0-firewall kernel: [  123.971217] CR2: 0000000000000008 CR3:
000000016e160000 CR4: 0000000000002660
Jun 28 15:04:00 dom0-firewall kernel: [  123.971271] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Jun 28 15:04:00 dom0-firewall kernel: [  123.971325] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Jun 28 15:04:00 dom0-firewall kernel: [  123.971379] Process udevd (pid: 498,
threadinfo ffff88016e16e000, task ffff88016db7a880)
Jun 28 15:04:00 dom0-firewall kernel: [  123.971491]  ffffffff81464f6c
00000000eff20557 00000000000080d0 ffff88016d918440
Jun 28 15:04:00 dom0-firewall kernel: [  123.971623] <0> ffff88016e144000
ffff88017203e120 ffff88016d918450 ffffffff8128694d
Jun 28 15:04:00 dom0-firewall kernel: [  123.971820] <0> ffff88016e16ff50
00000000eff20557 ffff88016d918450 0000000000000000
Jun 28 15:04:00 dom0-firewall kernel: [  123.972105]  [<ffffffff8128694d>] ?
dev_uevent+0xdd/0x134
Jun 28 15:04:00 dom0-firewall kernel: [  123.972157]  [<ffffffff81287983>] ?
show_uevent+0x92/0xff
Jun 28 15:04:00 dom0-firewall kernel: [  123.972208]  [<ffffffff812865a5>] ?
dev_attr_show+0x2e/0x6b
Jun 28 15:04:00 dom0-firewall kernel: [  123.972261]  [<ffffffff810d1460>] ?
get_zeroed_page+0x21/0x76
Jun 28 15:04:00 dom0-firewall kernel: [  123.972316]  [<ffffffff81167217>] ?
sysfs_read_file+0xbb/0x156
Jun 28 15:04:00 dom0-firewall kernel: [  123.972369]  [<ffffffff8100e301>] ?
xen_force_evtchn_callback+0x1d/0x37
Jun 28 15:04:00 dom0-firewall kernel: [  123.972422]  [<ffffffff8100edf2>] ?
check_events+0x12/0x20
Jun 28 15:04:00 dom0-firewall kernel: [  123.972474]  [<ffffffff81108fdc>] ?
vfs_read+0xb1/0x123
Jun 28 15:04:00 dom0-firewall kernel: [  123.972525]  [<ffffffff8100eddf>] ?
xen_restore_fl_direct_end+0x0/0x1
Jun 28 15:04:00 dom0-firewall kernel: [  123.972578]  [<ffffffff81387053>] ?
_spin_unlock_irqrestore+0x24/0x3e
Jun 28 15:04:00 dom0-firewall kernel: [  123.972631]  [<ffffffff81109136>] ?
sys_read+0x55/0x90
Jun 28 15:04:00 dom0-firewall kernel: [  123.972682]  [<ffffffff81013e02>] ?
system_call_fastpath+0x16/0x1b
Jun 28 15:04:00 dom0-firewall kernel: [  123.974604]  RSP <ffff88016e16fda8>
Jun 28 15:04:00 dom0-firewall kernel: [  123.974698] ---[ end trace
c9847565b3c746b5 ]---
root@dom0-firewall:~# Error: Device 0 (vif) could not be connected. Hotplug
scripts not working.


-- 
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