http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c1 --- Comment #1 from Harald Koenig 2010-05-18 19:31:05 UTC --- Created an attachment (id=363042) --> (http://bugzilla.novell.com/attachment.cgi?id=363042) xend.log -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c3 --- Comment #3 from Harald Koenig 2010-05-18 19:31:47 UTC --- Created an attachment (id=363044) --> (http://bugzilla.novell.com/attachment.cgi?id=363044) domain-builder-ng.log -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #363044|text/x-log |text/plain mime type| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c5 Harald Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|koenig@linux.de | --- Comment #5 from Harald Koenig 2010-05-20 19:01:03 UTC --- (In reply to comment #4)

These same domUs started fine before updating your dom0 to Factory? In

yes. all 12 domUs started up fine before that last update.

xend.log I see the vbd uname for os2-sles11 is file:/etc/xen/images/os2-sles11-flat.vmdk. That's not an actual vmdk image correct?

it was converted from a vmdk to a flat file, now it's just a plain disk image, nothing special except for the file name extension;)

I assume it is just a raw file with '.vmdk' extension. For vmdk images you would need to use 'tap:vmdk:/path/to/vmdk-image' - but I'd not recommend use of the vmdk subdriver in production environments yet. IIRC, there are known issues/limitations in the vmdk subdriver upstream.

ah, interesting. I didn't know that tap:vmdk:... feature -- nce to know;) but no, I won't use it in the future anyway... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c Ihno Krumreich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ihno@novell.com OS/Version|Other |openSUSE 11.3 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c8 Thomas E. Schreiner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netadm@messe.de --- Comment #8 from Thomas E. Schreiner 2010-06-25 11:58:20 UTC --- starting a Dom-U with a Networkinterface definitio like : vif=[ 'mac=00:16:3e:2b:c8:c6,bridge=br0', ] generates the following error messages: kernel:[ 276.870699] Oops: 0000 [#1] SMP kernel:[ 276.870702] last sysfs file: /sys/devices/xen-backend/vif-1-0/uevent kernel:[ 276.870807] Stack: kernel:[ 276.870823] Call Trace: kernel:[ 276.870885] Code: 28 48 89 5c 24 08 48 89 fb 48 8d 7f 48 48 89 6c 24 10 4c 89 64 24 18 48 89 f5 4c 89 6c 24 20 e8 e9 30 d8 df f6 05 b5 13 33 e0 02 <4c> 8b 60 08 75 75 48 8b 73 08 31 c9 31 ff 48 c7 c2 6f 5f 54 a0 kernel:[ 276.870933] CR2: 0000000000000008 Error: Device 0 (vif) could not be connected. Hotplug scripts not working. more informations ar in my file xen-log.txt . -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c10 --- Comment #10 from Harald Koenig 2010-06-29 15:44:57 UTC --- (In reply to comment #9)

I've tested with Milestone 7 and RC1 and the problem with the DomU's still exist. When I delete the line with the vif= declaration in the configuration file, the DomU starts without errors.

just a short "me too" from my cuurent test of 11.3: with vif=... line being commented out, a test domU starts (with no net, so not useful), but with vif=... I'm still in trouble: # rpm -q kernel-xen xen kernel-xen-2.6.34-9.5.x86_64 xen-4.0.0_21091_05-6.2.x86_64 # xm cre -c os-centos3u6 Using config file "./os-centos3u6". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. xend.log doesn't give any real information (not even an error msg): [2010-06-29 17:05:05 4222] DEBUG (DevController:139) Waiting for devices tap2. [2010-06-29 17:05:05 4222] DEBUG (XendDomainInfo:1922) XendDomainInfo.handleShutdownWatch [2010-06-29 17:05:05 4222] DEBUG (DevController:139) Waiting for devices vif. [2010-06-29 17:05:05 4222] DEBUG (DevController:144) Waiting for 0. [2010-06-29 17:05:05 4222] DEBUG (DevController:653) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [ ... waiting for 100 secs ... ] [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:3111) XendDomainInfo.destroy: domid=3 [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:2446) Destroying device model [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:2453) Releasing devices [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:2459) Removing vif/0 [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:1289) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2010-06-29 17:06:45 4222] DEBUG (XendDomainInfo:2459) Removing console/0 .. BUT there is a kernel oops for that time stamp in udevd / netback_uevent -- from /var/log/messages, hopefully this can help to fiure out what's going wrong ?!? Jun 29 17:05:03 os4 kernel: [ 1204.644580] kjournald starting. Commit interval 15 seconds Jun 29 17:05:03 os4 kernel: [ 1204.644594] EXT3-fs (dm-0): mounted filesystem with ordered data mode Jun 29 17:05:05 os4 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/3/768 Jun 29 17:05:05 os4 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/3/832 Jun 29 17:05:05 os4 kernel: [ 1205.844787] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Jun 29 17:05:05 os4 kernel: [ 1205.845157] IP: [<ffffffffa079a9ce>] netback_uevent+0x2e/0x100 [netbk] Jun 29 17:05:05 os4 kernel: [ 1205.845385] PGD 3e896d067 PUD 3ea605067 PMD 0 Jun 29 17:05:05 os4 kernel: [ 1205.845741] Oops: 0000 [#1] SMP Jun 29 17:05:05 os4 kernel: [ 1205.846023] last sysfs file: /sys/devices/xen-backend/vif-3-0/uevent Jun 29 17:05:05 os4 kernel: [ 1205.846180] CPU 1 Jun 29 17:05:05 os4 kernel: [ 1205.846262] Modules linked in: ib_iser rdma_cm ib_cm iw_cm ib_sa ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi iscsi_trgt crc32c nfs fscache ip6table_filter ip6_tables iptable_filter ip_tables x_tables usbbk gntdev netbk blkbk blkback_pagemap blktap domctl xenbus_be evtchn autofs4 nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs binfmt_misc bridge stp llc joydev usbhid fuse hid loop dm_mod iTCO_wdt 8250_pnp ib_mthca iTCO_vendor_support i5k_amb 8250 floppy serial_core ib_mad ioatdma i5000_edac sg sr_mod shpchp ib_core i2c_i801 intel_rng container button dca edac_core pci_hotplug pcspkr e1000e uhci_hcd radeon ttm drm_kms_helper ehci_hcd drm agpgart i2c_algo_bit i2c_core sd_mod usbcore xenblk cdrom xennet edd fan ata_generic ata_piix ahci libata scsi_mod thermal processor thermal_sys hwmon [last unloaded: scsi_transport_iscsi] Jun 29 17:05:05 os4 kernel: [ 1205.848591] Jun 29 17:05:05 os4 kernel: [ 1205.848591] Pid: 499, comm: udevd Not tainted 2.6.34-9-xen #1 X7DBR-3/X7DBR-3 Jun 29 17:05:05 os4 kernel: [ 1205.854497] RIP: e030:[<ffffffffa079a9ce>] [<ffffffffa079a9ce>] netback_uevent+0x2e/0x100 [netbk] Jun 29 17:05:05 os4 kernel: [ 1205.854497] RSP: e02b:ffff8803e92dbde8 EFLAGS: 00010246 Jun 29 17:05:05 os4 kernel: [ 1205.854914] RAX: 0000000000000000 RBX: ffff8803e1d01400 RCX: ffff8803d929513b Jun 29 17:05:05 os4 kernel: [ 1205.854914] RDX: ffff8803e8451840 RSI: ffff8803d9295000 RDI: ffff8803e1d01448 Jun 29 17:05:05 os4 kernel: [ 1205.854914] RBP: ffff8803d9295000 R08: 0000000000000000 R09: ffff8803d9295000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] R10: dead000000200200 R11: dead000000100100 R12: ffff8803d9295000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] R13: ffff8803d9295000 R14: ffff8803d9295000 R15: 0000000000000000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] FS: 00007fe99a03b7a0(0000) GS:ffff880004026000(0000) knlGS:0000000000000000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 29 17:05:05 os4 kernel: [ 1205.854914] CR2: 0000000000000008 CR3: 00000003ea612000 CR4: 0000000000002660 Jun 29 17:05:05 os4 kernel: [ 1205.854914] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Jun 29 17:05:05 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/node /dev/loop0 to xenstore. Jun 29 17:05:05 os4 kernel: [ 1205.854914] Process udevd (pid: 499, threadinfo ffff8803e92da000, task ffff8803e8954180) Jun 29 17:05:05 os4 kernel: [ 1205.854914] Stack: Jun 29 17:05:05 os4 kernel: [ 1205.854914] ffff8803d9295000 ffff8803e1d01448 0000000000000000 ffff8803d9295000 Jun 29 17:05:05 os4 kernel: [ 1205.854914] <0> ffff8803d9295000 ffffffff802c3301 0000000000100073 ffff8803ec199f40 Jun 29 17:05:05 os4 kernel: [ 1205.854914] <0> ffff8803ec199f40 ffff8803e1d01458 ffff8803a12d7000 ffffffff802c28e3 Jun 29 17:05:05 os4 kernel: [ 1205.854914] Call Trace: Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff802c3301>] dev_uevent+0x81/0x250 Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff802c28e3>] show_uevent+0xf3/0x190 Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff802c1ece>] dev_attr_show+0x1e/0x50 Jun 29 17:05:05 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/physical-device 7:0 to xenstore. Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff8017f9a1>] sysfs_read_file+0x111/0x1f0 Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff801134c3>] vfs_read+0xb3/0x190 Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff801135ee>] sys_read+0x4e/0x90 Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<ffffffff80007438>] system_call_fastpath+0x16/0x1b Jun 29 17:05:05 os4 kernel: [ 1205.854914] [<00007fe9999a83e0>] 0x7fe9999a83e0 Jun 29 17:05:05 os4 kernel: [ 1205.854914] Code: 28 48 89 5c 24 08 48 89 fb 48 8d 7f 48 48 89 6c 24 10 4c 89 64 24 18 48 89 f5 4c 89 6c 24 20 e8 e9 b0 b2 df f6 05 b5 93 0d e0 02 <4c> 8b 60 08 75 75 48 8b 73 08 31 c9 31 ff 48 c7 c2 6f df 79 a0 Jun 29 17:05:05 os4 kernel: [ 1205.854914] RIP [<ffffffffa079a9ce>] netback_uevent+0x2e/0x100 [netbk] Jun 29 17:05:05 os4 kernel: [ 1205.854914] RSP <ffff8803e92dbde8> Jun 29 17:05:05 os4 kernel: [ 1205.854914] CR2: 0000000000000008 Jun 29 17:05:05 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/hotplug-status connected to xenstore. Jun 29 17:05:05 os4 kernel: [ 1205.865505] ---[ end trace a50cffe5bd685bfd ]--- Jun 29 17:05:05 os4 kernel: [ 1206.384407] (cdrom_add_media_watch() file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/3/768 Jun 29 17:05:05 os4 kernel: [ 1206.384719] (cdrom_is_type() file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c, line=95) type:0 Jun 29 17:05:06 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/832/node /dev/loop1 to xenstore. Jun 29 17:05:06 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/832/physical-device 7:1 to xenstore. Jun 29 17:05:06 os4 logger: /etc/xen/scripts/block: Writing backend/vbd/3/832/hotplug-status connected to xenstore. Jun 29 17:05:06 os4 kernel: [ 1206.990894] (cdrom_add_media_watch() file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/3/832 Jun 29 17:05:06 os4 kernel: [ 1206.991217] (cdrom_is_type() file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c, line=95) type:0 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED Found By|--- |Community User AssignedTo|jdouglas@novell.com |jbeulich@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c13 --- Comment #13 from Harald Koenig 2010-06-30 08:06:30 UTC --- good to know! does kernel-xen-2.6.34-12.1 already include this fix, is this moning's update worth testing ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c15 --- Comment #15 from Harald Koenig 2010-06-30 12:45:54 UTC --- ACK! with dom0 kernel 2.6.34-12-xen vif in domU works again. thanks! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c17 --- Comment #17 from Harald Koenig 2010-08-03 17:27:32 UTC --- (In reply to comment #16)

Still experiencing problems with 2.6.34-12-xen. In particular, xend-debug.log still shows the crash/backtrace as before.

see bug #618678: http://bugzilla.novell.com/show_bug.cgi?id=618678#c29 that newer "kernel of the day" includes a patch which fixes all my problems. from that kernel-xen.rpm changelog: * Tue Jul 06 2010 jbeulich@novell.com - patches.xen/xen3-patch-2.6.22: Fix a uevent deadlock in netback (secondary issue from bnc#618678). * Tue Jul 06 2010 gregkh@suse.de - patches.xen/xen3-fixup-xen: Refresh for 2.6.34.1 update (parts of it were already in the .1 patch.) unfortunately there is still not kernel update for 11.3 so 11.3 xen support remains broken for now:-(( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c19 --- Comment #19 from Jan Engelhardt 2010-08-05 10:53:21 UTC --- Newly created domus seem to work fine though. One thing I noticed is that on 11.3, /etc/xen/vm/mine contains, for example: vif=[ 'mac=00:16:3e:59:89:12,bridge=br0', ] whereas on 11.2, if I remember correctly, it was just: vif=[ 'bridge=br0', ] -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=606921 http://bugzilla.novell.com/show_bug.cgi?id=606921#c21 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED Target Milestone|RC 2 |--- --- Comment #21 from Jan Beulich 2010-08-06 10:30:56 UTC --- according to #17 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.