domU destroy/create requires reboot [was: current dom0 panic on domu launch]

[Sarton O'Brien <bsd-xen%roguewrt.org@localhost>]

On 20/10/2009 12:49 PM, Sarton O'Brien wrote:
> [2009-10-20 12:37:25 318] ERROR (XendDomainInfo:1973) Device release
> failed: babylon; vif; vif/0
> Traceback (most recent call last):
>    File
> "usr/pkg/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
> 1967, in _releaseDevices
>      self.destroyDevice(true_devclass, dev, False);
>    File
> "usr/pkg/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
> 924, in destroyDevice
>      rc = self.getDeviceController(deviceClass).destroyDevice(devid, force)
>    File
> "/usr/pkg/lib/python2.5/site-packages/xen/xend/server/DevController.py",
> line 255, in destroyDevice
>      self.writeBackend(dev, 'online', "0")
>    File
> "/usr/pkg/lib/python2.5/site-packages/xen/xend/server/DevController.py",
> line 501, in writeBackend
>      raise VmError("Device %s not connected" % devid)
> VmError: Device 0 not connected
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:1966) Removing vbd/0
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:910)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/0
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:1966) Removing console/0
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:910)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> xenstore-read: couldn't read path /local/domain/0/backend/console/5/0/type
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:1951) No device model
> [2009-10-20 12:37:25 318] DEBUG (XendDomainInfo:1953) Releasing devices
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working

Needless to say, this makes testing debian rather painful, although at 
least possible.

I'm just looking for that one current snapshot where everything xen 
works! ... with the debian installer supported of course :)

Awaiting instruction ...

Sarton