rebooting a domU

Hi,

I've got a 4.99.4 dom0, with xenkernel30-3.0.3. 
When I 'shutdown -r now' in a 3.1 domU, or
'xm reboot foo' in the dom0, the domain doesn't come back.

In xend.log:

[2007-02-22 00:30:18 xend.XendDomainInfo 98] INFO
(XendDomainInfo:892) Domain has shutdown: name=web-vhost-0
id=17 reason=reboot.
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:1457) XendDomainInfo.destroyDomain(17)
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:190) XendDomainInfo.create(['domain',
['domid', 17], ['uuid',
'23eddb63-0442-816b-a880-628204bc6988'], ['vcpus', 1],
['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 128],
['shadow_memory', 0], ['maxmem', 128], ['features', ''],
['name', 'web-vhost-0'], ['on_poweroff', 'destroy'],
['on_reboot', 'restart'], ['on_crash', 'restart'], ['image',
['linux', ['kernel', '/local/3.1/netbsd-XEN3_DOMU.gz']]],
['device', ['vif', ['backend', 0], ['script', 'vif-bridge'],
['bridge', 'bridge0'], ['mac', '00:13:10:6c:b3:02']]],
['device', ['vbd', ['backend', 0], ['dev', 'xbd0d:disk'],
['uname', 'file:/lacol/web-vhost-0_slash.img'], ['mode',
'w']]], ['device', ['vbd', ['backend', 0], ['dev',
'xbd1d:disk'], ['uname',
'file:/lacol/web-vhost-0_local.img'], ['mode', 'w']]],
['device', ['vbd', ['backend', 0], ['dev', 'xbd2d:disk'],
['uname', 'file:/lacol/web-vhost-0_vice.img'], ['mode',
'w']]], ['state', '---s--'], ['shutdown_reason', 'reboot'],
['cpu_time', 5.8140563309999997], ['online_vcpus', 1],
['up_time', '529.956332922'], ['start_time',
'1172103688.38'], ['store_mfn', 63238], ['console_mfn',
63237]])
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:296) parseConfig: config is ['domain',
['domid', 17], ['uuid',
'23eddb63-0442-816b-a880-628204bc6988'], ['vcpus', 1],
['vcpu_avail', 1], ['cpu_weight', 1.0], ['memory', 128],
['shadow_memory', 0], ['maxmem', 128], ['features', ''],
['name', 'web-vhost-0'], ['on_poweroff', 'destroy'],
['on_reboot', 'restart'], ['on_crash', 'restart'], ['image',
['linux', ['kernel', '/local/3.1/netbsd-XEN3_DOMU.gz']]],
['device', ['vif', ['backend', 0], ['script', 'vif-bridge'],
['bridge', 'bridge0'], ['mac', '00:13:10:6c:b3:02']]],
['device', ['vbd', ['backend', 0], ['dev', 'xbd0d:disk'],
['uname', 'file:/lacol/web-vhost-0_slash.img'], ['mode',
'w']]], ['device', ['vbd', ['backend', 0], ['dev',
'xbd1d:disk'], ['uname',
'file:/lacol/web-vhost-0_local.img'], ['mode', 'w']]],
['device', ['vbd', ['backend', 0], ['dev', 'xbd2d:disk'],
['uname', 'file:/lacol/web-vhost-0_vice.img'], ['mode',
'w']]], ['state', '---s--'], ['shutdown_reason', 'reboot'],
['cpu_time', 5.8140563309999997], ['online_vcpus', 1],
['up_time', '529.956332922'], ['start_time',
'1172103688.38'], ['store_mfn', 63238], ['console_mfn',
63237]]
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:395) parseConfig: result is
{'shadow_memory': 0, 'uuid':
'23eddb63-0442-816b-a880-628204bc6988', 'on_crash':
'restart', 'on_reboot': 'restart', 'localtime': None,
'image': ['linux', ['kernel',
'/local/3.1/netbsd-XEN3_DOMU.gz']], 'on_poweroff':
'destroy', 'bootloader_args': None, 'cpus': None, 'name':
'web-vhost-0', 'backend': [], 'vcpus': 1, 'cpu_weight': 1.0,
'features': '', 'vcpu_avail': 1, 'memory': 128, 'device':
[('vif', ['vif', ['backend', 0], ['script', 'vif-bridge'],
['bridge', 'bridge0'], ['mac', '00:13:10:6c:b3:02']]),
('vbd', ['vbd', ['backend', 0], ['dev', 'xbd0d:disk'],
['uname', 'file:/lacol/web-vhost-0_slash.img'], ['mode',
'w']]), ('vbd', ['vbd', ['backend', 0], ['dev',
'xbd1d:disk'], ['uname',
'file:/lacol/web-vhost-0_local.img'], ['mode', 'w']]),
('vbd', ['vbd', ['backend', 0], ['dev', 'xbd2d:disk'],
['uname', 'file:/lacol/web-vhost-0_vice.img'], ['mode',
'w']])], 'bootloader': None, 'cpu': None, 'maxmem': 128}
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:1253) XendDomainInfo.construct: None
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:1285) XendDomainInfo.initDomain: 18 1.0
[2007-02-22 00:30:18 xend 98] DEBUG (balloon:133) Balloon:
35732 KiB free; 120252 to scrub; need 131072; retries: 20.
[2007-02-22 00:30:18 xend.XendDomainInfo 98] ERROR
(XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
inInfo.py", line 195, in create
    vm.initDomain()
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
inInfo.py", line 1335, in initDomain
    balloon.free(memory + shadow)
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 136, in free
    dom0_alloc = get_dom0_current_alloc()
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 71, in get_dom0_current_alloc
    kb = _get_proc_balloon(labels['current'])
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 54, in _get_proc_balloon
    f = file(PROC_XEN_BALLOON, 'r')
IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:1449) XendDomainInfo.destroy: domid=18
[2007-02-22 00:30:18 xend.XendDomainInfo 98] DEBUG
(XendDomainInfo:1457) XendDomainInfo.destroyDomain(18)
[2007-02-22 00:30:18 xend.XendDomainInfo 98] ERROR
(XendDomainInfo:1696) Failed to restart domain 17.
Traceback (most recent call last):
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
inInfo.py", line 1682, in restart
    new_dom = XendDomain.instance().domain_create(config)
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
in.py", line 228, in domain_create
    dominfo = XendDomainInfo.create(config)
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
inInfo.py", line 195, in create
    vm.initDomain()
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/XendDoma
inInfo.py", line 1335, in initDomain
    balloon.free(memory + shadow)
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 136, in free
    dom0_alloc = get_dom0_current_alloc()
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 71, in get_dom0_current_alloc
    kb = _get_proc_balloon(labels['current'])
  File
"/usr/pkg/lib/python2.4/site-packages/xen/xend/balloon.
py", line 54, in _get_proc_balloon
    f = file(PROC_XEN_BALLOON, 'r')
IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'


	Jonathan Kollasch

On 2/21/07, Jonathan A. Kollasch <jakllschkollasch.net> wrote:
> I've got a 4.99.4 dom0, with xenkernel30-3.0.3.
> When I 'shutdown -r now' in a 3.1 domU, or
> 'xm reboot foo' in the dom0, the domain doesn't come
back.
>
> In xend.log:

> IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'

Looks like you need to mount /kern.  Make sure the following
is in
/etc/fstab in the dom0:

kernfs /kern kernfs rw

and then "mount /kern" (or reboot the dom0) to get
the filesystem.

-- 
-- Todd Vierling <tvduh.org> <tvpobox.com> <toddvierling.name>

Jonathan A. Kollasch wrote:
> IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'

I mildly understand the use of 'balloon' but have never had
it exist for 
me. When I have received this error it is usually because I
have 
assigned more memory to the domu than is available at that
point in time.

In some instances I was able to manually load the domu with
the 
problematic amount of memory assigned but it would not start

automatically on boot nor on a restart.

Whether this has ever worked, I don't know. I just reduced
my memory by 
a few MB and forgot about it.

Sarton

On 2/21/07, Jonathan A. Kollasch <jakllschkollasch.net> wrote:
> I've got a 4.99.4 dom0, with xenkernel30-3.0.3.
> When I 'shutdown -r now' in a 3.1 domU, or
> 'xm reboot foo' in the dom0, the domain doesn't come
back.
>
> In xend.log:

> IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'

Looks like you need to mount /kern.  Make sure the following
is in
/etc/fstab in the dom0:

kernfs /kern kernfs rw

and then "mount /kern" (or reboot the dom0) to get
the filesystem.

-- 
-- Todd Vierling <tvduh.org> <tvpobox.com> <toddvierling.name>

Jonathan A. Kollasch wrote:
> IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'

I mildly understand the use of 'balloon' but have never had
it exist for 
me. When I have received this error it is usually because I
have 
assigned more memory to the domu than is available at that
point in time.

In some instances I was able to manually load the domu with
the 
problematic amount of memory assigned but it would not start

automatically on boot nor on a restart.

Whether this has ever worked, I don't know. I just reduced
my memory by 
a few MB and forgot about it.

Sarton

On Thu, Feb 22, 2007 at 03:50:09PM +1100, Sarton O'Brien
wrote:
> Jonathan A. Kollasch wrote:
> >IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'
> 
> I mildly understand the use of 'balloon' but have never
had it exist for 
> me. When I have received this error it is usually
because I have 
> assigned more memory to the domu than is available at
that point in time.
> 
> In some instances I was able to manually load the domu
with the 
> problematic amount of memory assigned but it would not
start 
> automatically on boot nor on a restart.
> 
> Whether this has ever worked, I don't know. I just
reduced my memory by 
> a few MB and forgot about it.

Yes, there is no baloon driver on NetBSD yet. What I suspect
happens
in this case is that on reboot, the new domain tries to
start before the
old one has released all memory, so there's not enough
memory for the new
domain.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Thu, Feb 22, 2007 at 03:50:09PM +1100, Sarton O'Brien
wrote:
> Jonathan A. Kollasch wrote:
> >IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'
> 
> I mildly understand the use of 'balloon' but have never
had it exist for 
> me. When I have received this error it is usually
because I have 
> assigned more memory to the domu than is available at
that point in time.
> 
> In some instances I was able to manually load the domu
with the 
> problematic amount of memory assigned but it would not
start 
> automatically on boot nor on a restart.
> 
> Whether this has ever worked, I don't know. I just
reduced my memory by 
> a few MB and forgot about it.

Yes, there is no baloon driver on NetBSD yet. What I suspect
happens
in this case is that on reboot, the new domain tries to
start before the
old one has released all memory, so there's not enough
memory for the new
domain.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

Manuel Bouyer wrote:
> Yes, there is no baloon driver on NetBSD yet. What I
suspect happens
> in this case is that on reboot, the new domain tries to
start before the
> old one has released all memory, so there's not enough
memory for the new
> domain.

I suspected something along these lines. It's never been an
issue for me.

Thanks for the info Manuel.

Sarton

Manuel Bouyer wrote:
> Yes, there is no baloon driver on NetBSD yet. What I
suspect happens
> in this case is that on reboot, the new domain tries to
start before the
> old one has released all memory, so there's not enough
memory for the new
> domain.

I suspected something along these lines. It's never been an
issue for me.

Thanks for the info Manuel.

Sarton

On Thu, Feb 22, 2007 at 01:04:34PM +0100, Manuel Bouyer
wrote:
> On Thu, Feb 22, 2007 at 03:50:09PM +1100, Sarton
O'Brien wrote:
> > Jonathan A. Kollasch wrote:
> > >IOError: [Errno 2] No such file or directory:
'/kern/xen/balloon'
> > 
> > I mildly understand the use of 'balloon' but have
never had it exist for 
> > me. When I have received this error it is usually
because I have 
> > assigned more memory to the domu than is available
at that point in time.
> > 
> > In some instances I was able to manually load the
domu with the 
> > problematic amount of memory assigned but it would
not start 
> > automatically on boot nor on a restart.
> > 
> > Whether this has ever worked, I don't know. I just
reduced my memory by 
> > a few MB and forgot about it.
> 
> Yes, there is no baloon driver on NetBSD yet. What I
suspect happens
> in this case is that on reboot, the new domain tries to
start before the
> old one has released all memory, so there's not enough
memory for the new
> domain.

Yeah, that's kinda what I was thinking :(  Unfortunately, I
want
all these separate domUs, and the boxes i want to use for
Xen
only really support 1/2GiB of RAM.  (P3 Katmai and
Coppermines
with i443something and i81x chipset.  The newer boxes I
want for workstations. )

Oh well, I can live with this I guess.

	Jonathan Kollasch