Dominik Klein
2008-Feb-08 07:58 UTC
[Xen-users] Cannot shutdown domain (xen 3.2, domU on drbd)
Hi
I set up Xen 3.2 in my test system in order to see wether everything
works as expected before I deploy it to my production systems.
dom0 and domU is debian etch 32 bit.
domU disk is block-drbd with drbd 8.0.10 (also tried 8.0.8 (which is
running in my production system) and 8.0.9)
Here''s my domU config:
kernel=''/boot/vmlinuz-2.6.18.8-xen''
ramdisk=''/boot/initrd-2.6.18.8-xen.img''
disk = [ ''drbd:drbd1,hda1,w'' ]
memory = 256
maxmem = 512
builder = ''linux''
name = ''dktestvmxen''
vif = [ ''mac=00:16:3e:13:71:7b,bridge=eth1'' ]
localtime = 0
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
root = ''/dev/hda1''
extra=''TERM=xterm xencons=tty console=tty1''
I ran into the following problem:
Starting the domU works just fine. Logging into it and testing the
basics also looks okay.
But I cannot shutdown the domain.
It does not matter if I use "halt" from domU or "xm
shutdown" in dom0. I
see the domain shuts down, reports "Halted" on its console, but the
"xm
list" status is:
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 256 1 r-----
17.2
dktestvmxen 1 256 1 ---s--
9.5
DRBD is still in primary state at this time.
I could not find errors in the logs, here''s a tail of the xen logs. If
you need more from a specific file, just ask please.
/var/log/xen# tail *
==> domain-builder-ng.log <= anon mmap : 0 bytes
mapped
file mmap : 5639 kB
domU mmap : 13988 kB
arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x237
shared_info_x86_32: called
vcpu_x86_32: called
vcpu_x86_32: cr3: pfn 0xea1 mfn 0x4f81e
launch_vm: called, ctxt=0x82cd5cc
xc_dom_release: called
==> xend-debug.log <=Xend started at Thu Feb 7 12:33:18 2008.
Xend started at Thu Feb 7 12:35:06 2008.
Xend started at Thu Feb 7 12:46:02 2008.
Xend started at Thu Feb 7 14:35:24 2008.
Xend started at Thu Feb 7 15:27:34 2008.
Xend started at Fri Feb 8 08:42:52 2008.
==> xend.log <=[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting
for devices irq.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices vkbd.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices vfb.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices
console.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for 0.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices pci.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices
ioports.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices tap.
[2008-02-08 08:48:36 3909] DEBUG (__init__:1072) Waiting for devices vtpm.
[2008-02-08 08:48:36 3909] INFO (__init__:1072) Domain dktestvmxen (1)
unpaused.
==> xen-hotplug.log <=Nothing to flush.
Nothing to flush.
Nothing to flush.
Nothing to flush.
Nothing to flush.
can''t add vif9.0 to bridge eth0: Operation not supported
Nothing to flush.
Nothing to flush.
Nothing to flush.
Nothing to flush.
Glad if someone could help.
Regards
Dominik
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Dominik Klein
2008-Feb-08 12:29 UTC
Re: [Xen-users] Cannot shutdown domain (xen 3.2, domU on drbd)
> # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 256 1 r----- > 17.2 > dktestvmxen 1 256 1 ---s-- > 9.5I just read "man xm" again and it states: s - shutdown FIXME: Why would you ever see this state? Did I hit a bug? Is it worth trying another version? Is there a newer version? Regards Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users