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 1192] New: Using lvsnapshot as the physical disk causes

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1192] New: Using lvsnapshot as the physical disk causes kernel OOPS
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 18 Mar 2008 19:57:50 -0700
Delivery-date: Tue, 18 Mar 2008 19:58:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/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=1192

           Summary: Using lvsnapshot as the physical disk causes kernel OOPS
           Product: Xen
           Version: 3.0.4
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: nick.wilkens@xxxxxxxxxxxxxxxx


I created a master installation on a logical volume, masterlv.  An lvsnapshot
of the masterlv was created, and called xen09lv.  When booting the domU of
xen09lv the system panics. Below are more details:

# uname -r
2.6.18-53.1.14.el5xen

# cat /etc/redhat-release
CentOS release 5 (Final)

# rpm -qa|grep -i xen
xen-libs-3.0.3-41.el5
xen-libs-3.0.3-41.el5
kernel-xen-2.6.18-53.1.14.el5
xen-3.0.3-41.el5

# cat /etc/xen/xen09
name = "xen09"
uuid = "88f56570-0d6c-48c5-94ec-76172346ec09"
maxmem = 128
memory = 128
vcpus = 1
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [  ]
disk = [ "phy:/dev/xenvg/xen09lv,xvda,w" ]
vif = ['mac=00:16:3e:f3:57:a8 bridge=xenbr0', 'mac=00:16:3e:e3:f2:a2,
bridge=xenbr1']

When removing the vif entries from the xen09 config file, the system boots
properly.

# xm create /etc/xen/xen09 -c
Using config file "/etc/xen/xen09".
Started domain xen09
Bootdata ok (command line is  ro root=/dev/VolGroup00/LogVol00 console=xvc0)
Linux version 2.6.18-53.1.14.el5xen (mockbuild@xxxxxxxxxxxxxxxxxxx) (gcc
version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000008800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 34816
Kernel command line:  ro root=/dev/VolGroup00/LogVol00 console=xvc0
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 8192 bytes)
Xen reported: 2000.070 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Software IO TLB disabled
Memory: 115956k/139264k available (2358k kernel code, 14964k reserved, 1325k
data, 172k init)
Calibrating delay using timer specific routine.. 5002.68 BogoMIPS
(lpj=10005373)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 157A0 could not acquire
Mutex [2] [20060707]
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 157A0 could not acquire
Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 8192 (order: 5, 131072 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1205895031.647:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key F8170EB5CF71EF90
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Bootdata ok (command line is  ro root=/dev/VolGroup00/LogVol00 console=xvc0)
Linux version 2.6.18-53.1.14.el5xen (mockbuild@xxxxxxxxxxxxxxxxxxx) (gcc
version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 12:08:17 EST 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000008800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 34816
Kernel command line:  ro root=/dev/VolGroup00/LogVol00 console=xvc0
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 8192 bytes)
Xen reported: 2000.070 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Software IO TLB disabled
Memory: 115956k/139264k available (2358k kernel code, 14964k reserved, 1325k
data, 172k init)
Calibrating delay using timer specific routine.. 5002.68 BogoMIPS
(lpj=10005373)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
(SMP-)alternatives turned off
Brought up 1 CPUs
checking if image is initramfs... it is
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 157A0 could not acquire
Mutex [2] [20060707]
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 157A0 could not acquire
Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 8192 (order: 5, 131072 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1205895031.647:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key F8170EB5CF71EF90
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/vif/1
Write protecting the kernel read-only data: 445k
Red Hat nash version 5.1.19.6 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading ohci-hcd.ko module
Loading ehci-hcd.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading xenblk.ko module
Registering block device major 202
 xvda: xvda1 xvda2
Loading dm-mod.ko module
device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised:
dm-devel@xxxxxxxxxx
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Scanning and configuring dmraid supported devices
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "VolGroup00" now active
Creating root device.
Mounting root filesystem.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
audit(1205895041.760:2): enforcing=1 old_enforcing=0 auid=4294967295
audit(1205895042.680:3): policy loaded auid=4294967295
INIT: version 2.86 booting
                Welcome to  CentOS release 5 (Final)
                Press 'I' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Setting clock  (utc): Tue Mar 18 22:50:54 EDT 2008 [  OK  ]
Starting udev: [  OK  ]
Setting hostname master.dynamic-venture.com:  [  OK  ]
Setting up Logical Volume Management:   2 logical volume(s) in volume group
"VolGroup00" now active
[  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 34030/2450400 files, 386402/2449408 blocks
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/xvda1
/boot: clean, 43/26104 files, 23610/104388 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Starting monitoring for VG VolGroup00:   2 logical volume(s) in volume group
"VolGroup00" monitored
[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  ----------- [cut here ] --------- [please bite
here ] ---------
Kernel BUG at net/core/dev.c:3298
invalid opcode: 0000 [1] SMP
last sysfs file: /class/net/lo/type
CPU 0
Modules linked in: xennet dm_multipath parport_pc lp parport pcspkr dm_snapshot
dm_zero dm_mirror dm_mod xenblk ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 9, comm: xenwatch Not tainted 2.6.18-53.1.14.el5xen #1
RIP: e030:[<ffffffff803fc858>]  [<ffffffff803fc858>] free_netdev+0x1e/0x3e
RSP: e02b:ffff880007eb7e18  EFLAGS: 00010293
RAX: 0000000000000001 RBX: ffff8800058853cf RCX: 000000018020b2d4
RDX: ffffffffff578000 RSI: 0000000000000000 RDI: ffff880005460000
RBP: ffff8800058853c0 R08: ffff880007eb6000 R09: 0000000000000000
R10: ffff880007eaf320 R11: ffff880007eaf7a0 R12: ffff880005460500
R13: ffff880007ebcc00 R14: 0000000000000005 R15: ffff880005460000
FS:  00002aaaab0166e0(0000) GS:ffffffff80599000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process xenwatch (pid: 9, threadinfo ffff880007eb6000, task ffff880007eaf7a0)
Stack:  ffffffff8810f2b7  ffff880007ebcc00  ffff880005460500  ffff8800074757c0
 ffff880005461e90  ffffffff88114608  ffff8800058853d1  ffff880000019ce0
 0000000100000001  ffff880007eaf7a0
Call Trace:
 [<ffffffff8810f2b7>] :xennet:backend_changed+0x81d/0x854
 [<ffffffff8039c453>] xenwatch_thread+0x0/0x135
 [<ffffffff802940b3>] keventd_create_kthread+0x0/0x61
 [<ffffffff8039b8b4>] xenwatch_handle_callback+0x15/0x48
 [<ffffffff8039c56f>] xenwatch_thread+0x11c/0x135
 [<ffffffff80294276>] autoremove_wake_function+0x0/0x2e
 [<ffffffff802940b3>] keventd_create_kthread+0x0/0x61
 [<ffffffff8023288d>] kthread+0xfe/0x132
 [<ffffffff8025db24>] child_rip+0xa/0x12
 [<ffffffff802940b3>] keventd_create_kthread+0x0/0x61
 [<ffffffff8023278f>] kthread+0x0/0x132
 [<ffffffff8025db1a>] child_rip+0x0/0x12


Code: 0f 0b 68 b2 8d 49 80 c2 e2 0c c7 87 28 03 00 00 04 00 00 00
RIP  [<ffffffff803fc858>] free_netdev+0x1e/0x3e
 RSP <ffff880007eb7e18>
 <0>Kernel panic - not syncing: Fatal exception


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

<Prev in Thread] Current Thread [Next in Thread>