WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Fail to create VM with unstable stage code

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Fail to create VM with unstable stage code
From: Jun Koi <junkoi2004@xxxxxxxxx>
Date: Thu, 25 Jun 2009 19:13:07 +0900
Delivery-date: Thu, 25 Jun 2009 03:13:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type:content-transfer-encoding; bh=uxN5coO8nKwmz4G0+Jofd0pJpxPf9wLJRuLLaCmNwCw=; b=Lgynf9G/7NNBY+pQiuYEotVjvRjJBw+Z9zsAZfxLOW5YIXxLx9sgnbX+U8l6+417J1 iwBQcrCDDQk4amh/IUYBL9LfKFSdEpoQxy0qRPmF0uD/k3mlxvWmAGx8fiTwnGEfjMSx VycLnmVRUOm3l0V3NtoYfHmggMruyT/UWaQQI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=Z5icRIbgUukUloBk320qSyqUIWPxCMJq+EUnw6KX7GY+Y6AIkH6pVI/Y0s656YOB/d DWNoY6Py+t7aOQDiwr+lirt0mvs+BMYuLB2H1HC7RBfagB1ciAYw/arwUT7u0lICJTyd hJHHvFdYlOImGFMhNwzauPYOJaeIYfHLO3dng=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I tried to create a VM with latest stage code (C/S 19833), but always
get error:

"Error: Device 768 (vbd) could not be connected. Hotplug scripts not working."

Below is the qemu log, and xend.log. Any idea?

I get this problem for last few days, and cannot fix that. This turns
frustrated now :-((

Thanks,
J

QEMU log
----------
domid: 2
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap2.0 xenbr0
Strip off blktap sub-type prefix to /home/xenvms/img.qcow2.ubuntu904
(drv 'qcow2')
Watching /local/domain/0/device-model/2/logdirty/next-active
Watching /local/domain/0/device-model/2/command
qemu_map_cache_init nr_buckets = 4000 size 327680
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = e7dcb3dc-6739-4943-a165-b91b347dde02
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/e7dcb3dc-6739-4943-a165-b91b347dde02/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/e7dcb3dc-6739-4943-a165-b91b347dde02/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0


xend.log
--------
.....
[2009-06-25 18:49:01 4484] DEBUG (XendDomainInfo:1624) Storing domain
details: {'console/port': '3', 'name': 'ubuntu904', 'console/limit':
'1048576', 'store/port': '2', 'vm':
'/vm/e7dcb3dc-6739-4943-a165-b91b347dde02', 'domid': '2',
'image/suspend-cancel': '1', 'cpu/0/availability': 'online',
'memory/target': '921600',
'control/platform-feature-multiprocessor-suspend': '1',
'store/ring-ref': '1044476', 'console/type': 'ioemu'}
[2009-06-25 18:49:01 4484] DEBUG (DevController:95) DevController:
writing {'state': '1', 'backend-id': '0', 'backend':
'/local/domain/0/backend/console/2/0'} to
/local/domain/2/device/console/0.
[2009-06-25 18:49:01 4484] DEBUG (DevController:97) DevController:
writing {'domain': 'ubuntu904', 'frontend':
'/local/domain/2/device/console/0', 'uuid':
'68447c2d-be39-3aab-e20d-177f9a17f044', 'frontend-id': '2', 'state':
'1', 'location': '3', 'online': '1', 'protocol': 'vt100'} to
/local/domain/0/backend/console/2/0.
[2009-06-25 18:49:01 4484] DEBUG (XendDomainInfo:1711)
XendDomainInfo.handleShutdownWatch
[2009-06-25 18:49:01 4484] DEBUG (DevController:139) Waiting for devices vif.
[2009-06-25 18:49:01 4484] DEBUG (DevController:144) Waiting for 0.
[2009-06-25 18:49:01 4484] DEBUG (DevController:657)
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2009-06-25 18:49:01 4484] DEBUG (DevController:671) hotplugStatusCallback 1.
[2009-06-25 18:49:01 4484] DEBUG (DevController:139) Waiting for devices vscsi.
[2009-06-25 18:49:01 4484] DEBUG (DevController:139) Waiting for devices vbd.
[2009-06-25 18:49:01 4484] DEBUG (DevController:144) Waiting for 768.
[2009-06-25 18:49:01 4484] DEBUG (DevController:657)
hotplugStatusCallback
/local/domain/0/backend/tap/2/768/hotplug-status.
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2727)
XendDomainInfo.destroy: domid=2
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2201) Destroying device model
[2009-06-25 18:50:41 4484] INFO (image:580) ubuntu904 device model terminated
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2208) Releasing devices
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2221) Removing vif/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:1137)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2221) Removing vbd/768
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:1137)
XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/768
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2221) Removing vfb/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:1137)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2221) Removing console/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:1137)
XendDomainInfo.destroyDevice: deviceClass = console, device =
console/0
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2206) No device model
[2009-06-25 18:50:41 4484] DEBUG (XendDomainInfo:2208) Releasing devices

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Fail to create VM with unstable stage code, Jun Koi <=