[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: Device 0 couldnt be connected
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |