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] Re: Device 0 couldnt be connected

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Device 0 couldnt be connected
From: Jun Koi <junkoi2004@xxxxxxxxx>
Date: Sat, 20 Jun 2009 09:36:46 +0900
Delivery-date: Fri, 19 Jun 2009 17:37:12 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=mOiVHWD9lrNzCAf5UgL5YIJb1FzADlZ0w6YVfvxiV4A=; b=DEVeJKpPeoYMw5yRURJZ+q99ErbrGUQwv1B0YHBlof0HLzYDLXLsrmnnQX3UU0QT8B AVUiw0KxuMammOlkmHgRTVJ8suIb9PamAbR3DCLucwFU3joHPdfJP+8OwIsRJSnWNtpp k5AcGeHf7sEvHHdXZKgcpozUUzaRpCrAhglt0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=o7ocr++gVEpZ1LP56oGbEQ3SxZjXhuKtWFMsrYMSi2CrQ/FWIqILE+2VZuK/X5vPSE 50yvY6KgPH3gjjpTKDVr5g8jjJQP5f4tC+NBQV5yk593pc3sBofyebLdMrpksSU91J1H otm5V63WPVM9Ei6Wen0D7TYi++1kogrfX/AAE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdaac4d50906191735w57cd7216hecb80e6c332527c@xxxxxxxxxxxxxx>
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>
References: <fdaac4d50906191735w57cd7216hecb80e6c332527c@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Jun 20, 2009 at 9:35 AM, Jun Koi<junkoi2004@xxxxxxxxx> wrote:
> hi,
>
> I am trying to use latest stage tree (C/S 19806), but got error like:
>
> "Error: Device 0 (vif) could not be connected. Hotplug scripts not working."
>
> The qemu log doesnt say much about problem, like below. Any idea?

Sorry, the correct qemu log is like this:

# cat /var/log/xen/qemu-dm-ubuntu904.log
domid: 3
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap3.0 xenbr0
bridge xenbr0 does not exist!
Strip off blktap sub-type prefix to /home/xen/img.qcow2.ubuntu904 (drv 'qcow2')
Watching /local/domain/0/device-model/3/logdirty/next-active
Watching /local/domain/0/device-model/3/command
qemu_map_cache_init nr_buckets = 4000 size 327680
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 550b4387-22fe-b050-5b4c-1bd985cea190
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/550b4387-22fe-b050-5b4c-1bd985cea190/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/3/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/550b4387-22fe-b050-5b4c-1bd985cea190/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

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

<Prev in Thread] Current Thread [Next in Thread>