Bug#607141: xm block-attach failed on domU
Peter Viskup wrote: Hello Jonathan, thanks for taking care. I was not experiencing this issue since then. Interesting. Thanks for the update. [...] I am still using the system and going to update it to squeeze within next two weeks. Best of luck. :) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120209221449.GB3188@burratino
Bug#607141: xm block-attach failed on domU
Peter Viskup skupko...@gmail.com writes:
'xm block-attach domain phy:data/disk /dev/xvda6 w'
I can attach a block device
$ sudo xm block-attach 27 file:/local/xen/lindi-exp1/disk.img /dev/xvda w
$ sudo xm block-list 27
Vdev BE handle state evt-ch ring-ref BE-path
51712 00 4 9 770 /local/domain/0/backend/vbd/27/51712
[ 81.988522] blkfront: xvda: barriers enabled
[ 81.988852] xvda: xvda1
[ 81.988969] xvda: p1 size 979902 exceeds device capacity, limited to end of
disk
and also detach it:
$ sudo xm block-detach 27 51712
This particular domU was started with
name = 'lindi-exp1'
vcpus = '1'
memory = '256'
kernel = '/local/xen/lindi-exp1/vmlinuz-2.6.32-5-amd64'
ramdisk = '/local/xen/lindi-exp1/initrd.img-2.6.32-5-amd64'
nfs_server = '10.7.2.17'
nfs_root = '/tftpboot/lindi-exp1'
extra = 'root=/dev/nfs ip=dhcp'
vif = [ 'mac=52:54:00:12:35:09' ]
cpuid = [ '0:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
'1:eax=0x0f61,ecx=0xx00x0x,edx=xxx0',
'0x8000:eax=0x8004,ebx=0x0,ecx=0x0,edx=0x0',
'0x8001:eax=0x0f61,ecx=xx0x,edx=00xx000xx0xxx0xx'
]
# up to leaf _0003/8000_0004
# family 15 model 6 stepping 1 (Intel P4 Prescott, AMD K8)
# disable POPCNT, SSE4.[12], SSSE3
# disable HTT
# disable CMPLEGACY, SVM, EXTAPIC, ALTMOVCR8, ABM, SSE4a, MisAlignSSE,
# 3DNOWPrefetch, OSVW, IBS, SSE5, SKINIT, WDT
# disable 3DNOW, 3DNOWEXT, RDTSCP, Page1GB, FFXSR, MMXExt, MP
#
# Source: Cross-Vendor Migration
# AMD Operating Systems Research Center
# Uwe Dannowski Andre Przywara
# {firstname.lastna...@amd.com
# 2010 Advanced Micro Devices, Inc. All rights reserved.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/84y66tcglr@sauna.l.org
Bug#607141: xm block-attach failed on domU
Hello Timo, for some reason I didn't received your question and I found it just now on bugs.debian.org pages. I didn't record my previous commands but I used standard xm block-attach syntax from vhost config like: 'xm block-attach domain phy:data/disk /dev/xvda6 w' I am mapping LVM LV's from VG named 'data' to my vhosts. -- Peter Viskup -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2a392c.3030...@gmail.com
Bug#607141: xm block-attach failed on domU
Peter Viskup skupko...@gmail.com writes: Execution of xm block-attach to PV domU failed and I have got Ooops kernel messages in attachment. Can you tell me the exact block-attach command so that I can at least test that it works with squeeze? (I doubt it can be fixed for lenny.) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84y67cwpcr@sauna.l.org
Bug#607141: xm block-attach failed on domU
Package: linux-image-2.6-xen-amd64 Version: 2.6.26-26lenny1 Severity: critical Tags: lenny Execution of xm block-attach to PV domU failed and I have got Ooops kernel messages in attachment. After that domU wasn't manageable from dom0 - all xm commands were not successful and I had to shutdown the domU from the pty (ssh) console. Both dom0 and domU were running same kernel version. -- Peter Viskup Dec 13 16:29:04 tis kernel: [83118.676876] BUG: unable to handle kernel NULL pointer dereference at Dec 13 16:29:04 tis kernel: [83118.676898] IP: [8038d104] backend_changed+0x1bf/0x23a Dec 13 16:29:04 tis kernel: [83118.676920] PGD 1e82f067 PUD 1f1a8067 PMD 0 Dec 13 16:29:04 tis kernel: [83118.676933] Oops: [1] SMP Dec 13 16:29:04 tis kernel: [83118.676941] CPU 0 Dec 13 16:29:04 tis kernel: [83118.676948] Modules linked in: iptable_filter ip_tables x_tables ipv6 xfs evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod thermal_sys cciss scsi_mod Dec 13 16:29:04 tis kernel: [83118.676991] Pid: 19, comm: xenwatch Not tainted 2.6.26-2-xen-amd64 #1 Dec 13 16:29:04 tis kernel: [83118.677000] RIP: e030:[8038d104] [8038d104] backend_changed+0x1bf/0x23a Dec 13 16:29:04 tis kernel: [83118.677015] RSP: e02b:88001fd11e60 EFLAGS: 00010246 Dec 13 16:29:04 tis kernel: [83118.677023] RAX: RBX: 880006dec000 RCX: Dec 13 16:29:04 tis kernel: [83118.677032] RDX: 88001fd11de8 RSI: 0005 RDI: 88001f12c400 Dec 13 16:29:04 tis kernel: [83118.677041] RBP: 8038327f R08: 0005 R09: Dec 13 16:29:04 tis kernel: [83118.677050] R10: 8800850bb000 R11: 8038cf45 R12: 88001f12c400 Dec 13 16:29:04 tis kernel: [83118.677059] R13: 8057c580 R14: 8057d1c0 R15: Dec 13 16:29:04 tis kernel: [83118.677070] FS: 7f53a5d766e0() GS:8053a000() knlGS: Dec 13 16:29:04 tis kernel: [83118.677080] CS: e033 DS: ES: Dec 13 16:29:04 tis kernel: [83118.677087] DR0: DR1: DR2: Dec 13 16:29:04 tis kernel: [83118.677097] DR3: DR6: 0ff0 DR7: 0400 Dec 13 16:29:04 tis kernel: [83118.677106] Process xenwatch (pid: 19, threadinfo 88001fd1, task 88001fd08140) Dec 13 16:29:04 tis kernel: [83118.677116] Stack: 8057c580 80383a01 88001f059c40 88001f12c400 Dec 13 16:29:04 tis kernel: [83118.677133] 8052a968 8057c580 8057d1c0 80381c19 Dec 13 16:29:04 tis kernel: [83118.677148] 00058038327f 88001f1f2d80 Dec 13 16:29:04 tis kernel: [83118.677161] Call Trace: Dec 13 16:29:04 tis kernel: [83118.677172] [80383a01] ? xenbus_device_find+0x28/0x31 Dec 13 16:29:04 tis kernel: [83118.677184] [80381c19] ? xenbus_read_driver_state+0x26/0x3b Dec 13 16:29:04 tis kernel: [83118.677195] [8038327f] ? xenwatch_thread+0x0/0x186 Dec 13 16:29:04 tis kernel: [83118.677206] [8038295d] ? xenwatch_handle_callback+0x15/0x48 Dec 13 16:29:04 tis kernel: [83118.677216] [803833ec] ? xenwatch_thread+0x16d/0x186 Dec 13 16:29:04 tis kernel: [83118.677227] [8023f6ad] ? autoremove_wake_function+0x0/0x2e Dec 13 16:29:04 tis kernel: [83118.677237] [8023f57f] ? kthread+0x47/0x74 Dec 13 16:29:04 tis kernel: [83118.677247] [802282ec] ? schedule_tail+0x27/0x5c Dec 13 16:29:04 tis kernel: [83118.677257] [8020be28] ? child_rip+0xa/0x12 Dec 13 16:29:04 tis kernel: [83118.677268] [8023f538] ? kthread+0x0/0x74 Dec 13 16:29:04 tis kernel: [83118.677276] [8020be1e] ? child_rip+0x0/0x12 Dec 13 16:29:04 tis kernel: [83118.677283] Dec 13 16:29:04 tis kernel: [83118.677287] Dec 13 16:29:04 tis kernel: [83118.677291] Code: 23 3e 17 00 c6 40 01 00 80 38 00 74 05 e8 f1 00 ff ff 48 8b 7b 08 e8 56 8e f7 ff c7 83 9c 1a 00 00 01 00 00 00 eb 74 48 8b 43 08 8b 38 c1 e7 14 0b 78 04 e8 10 40 f2 ff 48 85 c0 48 89 c5 75 16 Dec 13 16:29:04 tis kernel: [83118.677391] RIP [8038d104] backend_changed+0x1bf/0x23a Dec 13 16:29:04 tis kernel: [83118.677402] RSP 88001fd11e60 Dec 13 16:29:04 tis kernel: [83118.677408] CR2: Dec 13 16:29:04 tis kernel: [83118.677419] ---[ end trace 75e2ecdeadd46e28 ]---
