Pkg xen devel - Feb 2013 - Bug#701213: Hvm domU doesn't boot after dom0 reboot under Debian Wheezy

Package: xen-hypervisor-4.1-amd64
Version: 4.1.4-2

Hi,

Hvm domU does not starts up afer dom0 reboot.

Bridge br0 is set up manually.

Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC
2012 x86_64 GNU/Linux
config:
===<=======kernel = '/usr/lib/xen-4.1/boot/hvmloader'
builder = 'hvm'
vcpus = '1'
memory = '512'
maxmem = '512'
disk = ['phy:/dev/vg0/hvm1.disk,hda,w']

name = 'hvm1'

vif = [ 'mac=xx:xx:xx:xx:xx:xx, bridge=br0, model=e1000' ]

boot = 'c'
acpi = '1'
apic = '1'
xen_platform_pci='1'
sdl = '0'
vnc = '0'
#vnclisten = '0.0.0.0'
usb = '1'
usbdevice = 'host:12d1:1003'

on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
===>====
/var/log/xen/qemu-dm-hvm1.log:
domid: 8
-c config qemu network with xen bridge for
vif8.0-emu br0
RTNETLINK answers: Device or resource busy
device vif8.0-emu is already a member of a bridge; can't enslave it to
bridge br0.
/etc/xen/scripts/qemu-ifup: could not launch network script
Could not initialize device 'tap'

Starting hvm domU manually works as expected.

--
T

Control: tag -1 +moreinfo

On Fri, 22 Feb 2013 22:50:53 +0100 T <hex445 at gmail.com>
wrote:
> Package: xen-hypervisor-4.1-amd64
> Version: 4.1.4-2
> 
> Hi,
> 
> Hvm domU does not starts up afer dom0 reboot.
You mean automatically? What process is supposed to cause that to happen
i.e. xendomains iniscript or something else?

[...]
> device vif8.0-emu is already a member of a bridge; can't enslave it to
> bridge br0.
> /etc/xen/scripts/qemu-ifup: could not launch network script
> Could not initialize device 'tap'
*If* this is a fatal error which is causing the issue you are seeing
(I'm not sure) then I know that this is much changed Xen 4.4 (now in
Jessie). In which case it would be worth trying the newer version.

If not then other logs than qemu.log would be interesting, e.g. the main
toolstack logs, any logs produced by whatever command is supposed to
start the domain.
> Starting hvm domU manually works as expected.
Manually how? (I can take a pretty good guess, but just to be sure!)

Ian.

Processing control commands:
> tag -1 +moreinfo
Bug #701213 [xen-hypervisor-4.1-amd64] Hvm domU doesn't boot after dom0
reboot under Debian Wheezy
Added tag(s) moreinfo.

-- 
701213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701213
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

Processing control commands:
> tag -1 +moreinfo
Bug #701213 [xen-hypervisor-4.1-amd64] Hvm domU doesn't boot after dom0
reboot under Debian Wheezy
Ignoring request to alter tags of bug #701213 to the same tags previously set

-- 
701213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701213
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems

Hi T,

This is about the bug report (#701213) about a HVM domU that you filed
before in the Debian bug tracker, against the Xen packages.

Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).

Can you please help us by confirming that any of the following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a while from now, we
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
Hans van Kranenburg

Your message dated Mon, 11 Mar 2019 00:44:15 +0100
with message-id <3dee1d48-50b5-1481-014d-52f9e01c6dc0 at knorrie.org>
and subject line Re: Hvm domU doesn't boot after dom0 reboot under Debian
Wheezy
has caused the Debian Bug report #701213,
regarding Hvm domU doesn't boot after dom0 reboot under Debian Wheezy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
701213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701213
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: T <hex445 at gmail.com>
Subject: Hvm domU doesn't boot after dom0 reboot under Debian Wheezy
Date: Fri, 22 Feb 2013 22:50:53 +0100
Size: 3313
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190310/33b8a3dd/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Hans van Kranenburg <hans at knorrie.org>
Subject: Re: Hvm domU doesn't boot after dom0 reboot under Debian Wheezy
Date: Mon, 11 Mar 2019 00:44:15 +0100
Size: 7481
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190310/33b8a3dd/attachment-0003.mht>