[Xen-bugs] [Bug 407] New: Cannot reboot domU

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=407

           Summary: Cannot reboot domU
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: berni@xxxxxxxxxxxxx


When I /sbin/reboot domU it is not automatically restarted despite the settings

on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

in /etc/xen/ubuntu. The following error messages are logged in 
/var/log/xend.log:

[2005-11-14 02:16:57 xend] INFO (XendDomain:349) Domain vs01 (4) unpaused.
[2005-11-14 02:17:44 xend.XendDomainInfo] INFO (XendDomainInfo:701) Domain has
shutdown: name=vs01 id=4 reason=reboot.
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:1130)
XendDomainInfo.destroyDomain(4)
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:151)
XendDomainInfo.create(['domain', ['domid', 4], ['name', 'vs01'], ['uuid',
'45ca1ce3-b7b0-f2d8-76cd-aae204404fc0'], ['ssidref', 0], ['vcpus', 1],
['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 512], ['maxmem', 512],
['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'],
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12-xenU'], ['root', '/dev/hda1
ro'], ['args', '4'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c']]], ['device',
['vbd', ['uname', 'phy:evms/vs01'], ['dev', 'hda1'], ['mode', 'w']]], ['device',
['vif', ['mac', '00:aa:00:00:02:01'], ['bridge', 'xenbr0']]], ['state',
'---s--'], ['shutdown_reason', 'reboot'], ['cpu_time', 3.2929311979999998],
['vcpus', 1], ['up_time', '47.1283710003'], ['start_time', '1131934617.04'],
['store_mfn', 93219], ['console_mfn', 93218]])
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:254)
parseConfig: config is ['domain', ['domid', 4], ['name', 'vs01'], ['uuid',
'45ca1ce3-b7b0-f2d8-76cd-aae204404fc0'], ['ssidref', 0], ['vcpus', 1],
['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 512], ['maxmem', 512],
['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'],
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12-xenU'], ['root', '/dev/hda1
ro'], ['args', '4'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c']]], ['device',
['vbd', ['uname', 'phy:evms/vs01'], ['dev', 'hda1'], ['mode', 'w']]], ['device',
['vif', ['mac', '00:aa:00:00:02:01'], ['bridge', 'xenbr0']]], ['state',
'---s--'], ['shutdown_reason', 'reboot'], ['cpu_time', 3.2929311979999998],
['vcpus', 1], ['up_time', '47.1283710003'], ['start_time', '1131934617.04'],
['store_mfn', 93219], ['console_mfn', 93218]]
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:308)
parseConfig: result is {'ssidref': 0, 'name': 'vs01', 'bootloader': None,
'on_reboot': 'restart', 'image': ['linux', ['kernel',
'/boot/vmlinuz-2.6.12-xenU'], ['root', '/dev/hda1 ro'], ['args', '4'], ['vcpus',
'1'], ['vcpus', '1'], ['boot', 'c']], 'on_poweroff': 'destroy', 'on_crash':
'restart', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0, 'vcpu_avail': 1,
'memory': 512, 'device': [('vbd', ['vbd', ['uname', 'phy:evms/vs01'], ['dev',
'hda1'], ['mode', 'w']]), ('vif', ['vif', ['mac', '00:aa:00:00:02:01'],
['bridge', 'xenbr0']])], 'maxmem': 512, 'cpu': None, 'uuid':
'45ca1ce3-b7b0-f2d8-76cd-aae204404fc0'}
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:1011)
XendDomainInfo.construct: None 0
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:1043)
XendDomainInfo.initDomain: 5 1.0
[2005-11-14 02:17:44 xend.XendDomainInfo] ERROR (XendDomainInfo:162) Domain
construction failed
Traceback (most recent call last):
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 156, in create
    vm.initDomain()
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 1059, in initDomain
    xc.domain_memory_increase_reservation(self.domid, m, 0, 0)
error: (12, 'Cannot allocate memory')
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:1122)
XendDomainInfo.destroy: domid=5
[2005-11-14 02:17:44 xend.XendDomainInfo] DEBUG (XendDomainInfo:1130)
XendDomainInfo.destroyDomain(5)
[2005-11-14 02:17:44 xend.XendDomainInfo] ERROR (XendDomainInfo:1293) Failed to
restart domain 4.
Traceback (most recent call last):
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 1282, in restart
    new_dom = xd.domain_create(config)
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomain.py",
line 215, in domain_create
    dominfo = XendDomainInfo.create(config)
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 156, in create
    vm.initDomain()
  File
"/home/berni/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
line 1059, in initDomain
    xc.domain_memory_increase_reservation(self.domid, m, 0, 0)
error: (12, 'Cannot allocate memory')


domU can be recreated immediately after this logmessage by doing the appropriate
 xm create call in dom0.

berni@svr02:~$ sudo xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      120     1 r-----    34.6
vs02                               2      256     1 -b----   460.8
vs01                               6      512     1 -b----     2.5

dom0 and domU are Ubuntu breezy x86_64, dom0 has 1GB physical memory and 2GB
swap. The latest changeset in my source tree is

changeset:   7772:995e94c4802e5c0376b0483f3b2473a8f7d7808e
tag:         tip
user:        smh22@xxxxxxxxxxxxxxxxxxxx
date:        Fri Nov 11 18:11:13 2005
summary:     Attached patch allows PAE xenlinux to run in the shadow mode using

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