All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Benaguev <abenaguev@gmail.com>
To: xen-devel@lists.xensource.com
Subject: I have killed hypervisor. wow
Date: Sun, 16 Nov 2008 03:25:46 +0300	[thread overview]
Message-ID: <491F688A.4030004@gmail.com> (raw)

Greetings

all my pv domains have failed today after reboot (hvm domains are ok). I 
found out that virtual block devices just stopped mounting to guests. 
Then I tried to destroy failed domains and got a lot of messages to 
dmesg like:
blk_tap: Bad number of segments in request (179)
#snip 1511 messages
blk_tap: unknown operation [152]
#snip 1526 messages

Then dom0 froze dead producing the above output only. After the reboot 
everything was the same except dom0 kept produce same output for a 
couple of minutes, and domU finally was destroyed. after 'xm create -c 
ubuntu810' (domain falls into initramfs shell) hypervisor dmesg shows:

blktap: ring-ref 2047, event-channel 4, protocol 1 (x86_64-abi)
tap_frontend_changed: backend/tap/1/51712: prepare for reconnect
blktap: ring-ref 8, event-channel 9, protocol 1 (x86_64-abi)

guest dmesg:
0.403082] device-mapper: uevent: version 1.0.3
[    0.403297] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) 
initialised: dm-devel@redhat.com
[    0.535802]  xvda:
#it's not mistake. dmesg just ends output.

I destroyed domain again and everything repeats.

I think this is caused by 8.10 kernel, which has updated to 2.6.27.7.14 
or 16 recently.
But I have no idea why this keeps crashing the system.
Any ideas?

domU config:
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0,0)/grub/menu.lst"
memory = 2048
vcpus = 2
name = "postgres1"
uuid = "5bb1d470-ae11-389f-b49a-49ff2a84a9f3"
vif = [ 'mac=00:16:3e:36:7f:a9, bridge=eth0' ]
disk = [ 'tap:aio:/var/lib/xen/images/postgres1.img,xvda,w' ]

p.s. please, tell me, if I should provide more information
p.p.s. thanks to Mikhail Kozyrev for spelling

                 reply	other threads:[~2008-11-16  0:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=491F688A.4030004@gmail.com \
    --to=abenaguev@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.