Re: [Xen-devel] no console when using xl toolstack xen 4.1.2

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>]

On Thu, 26 Apr 2012, Sam Mulvey wrote:
> On Apr 25, 2012, at 8:50 AM, Stefano Stabellini wrote:
> 
>       It looks like the disk was opened correctly, maybe more logging will
>       tell us what is going wrong.
>       Could you please try the following patch?
> 
> domid: 1
> Warning: vlan 0 is not connected to host network
> -videoram option does not work with cirrus vga device model. Videoram set to 
> 4M.
> /home/sam/build/debug/xen/src/xen-4.1.2/tools/ioemu-qemu-xen/hw/xen_blktap.c:628:
>  Init blktap pipes
> /home/sam/build/debug/xen/src/xen-4.1.2/tools/ioemu-qemu-xen/hw/xen_blktap.c:603:
>  Created /var/run/tap directory
> Could not open /var/run/tap/qemu-read-1
> xen be: console-0: backend state: Unknown -> Initialising
> char device redirected to /dev/pts/2
> xen be: console-0: backend state: Initialising -> InitWait
> xen be: console-0: frontend not ready, ignoring
> xen be: console-0: bind evtchn port 70
> xen be: console-0: ring mfn 412787, remote port 2, local port 70, limit 
> 1048576
> xen be: console-0: backend state: InitWait -> Connected
> xen be: qdisk-51712: backend state: Unknown -> Initialising
> xen be: qdisk-51712: frontend state: Unknown -> Initialising
> DEBUG blk_init 587
> DEBUG blk_init 602 filename=/var/finnix/finnix-104.iso
> DEBUG blk_init 613 protocol=raw
> DEBUG blk_init 622
> DEBUG blk_init 636
> xen be: qdisk-51712: create new bdrv (xenbus setup)
> DEBUG blk_init 659
> xen be: qdisk-51712: type "tap", fileproto "raw", filename 
> "/var/finnix/finnix-104.iso", size 121708544 (116 MB)
> xen be: qdisk-51712: backend state: Initialising -> InitWait
> xen be: qdisk-51712: frontend not ready (yet)
> xs_read(): target get error. /local/domain/1/target.
> xen be: console-0: backend update: state
> xen be: console-0: frontend update: tty
> xen be: console-0: backend update: hotplug-status
> xen be: console-0: backend update: state
> xen be: console-0: backend update: state
> xen be: qdisk-51712: backend update: state
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: feature-barrier
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: info
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: sector-size
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: sectors
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: hotplug-status
> xen be: qdisk-51712: frontend not ready (yet)
> xen be: qdisk-51712: backend update: state
> xen be: qdisk-51712: frontend not ready (yet)
> xen be core: displaystate setup failed
> (qemu) (qemu) xen be: console-0: backlog piling up, nobody listening?
 
It looks like the backend (QEMU) is waiting for the client to connect,
but it never happens.
Are you sure that blkfront is compiled in the guest's kernel?
I fail to see how this could work with XenD but not with Xl.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel