[Xen-users] Xen4.1, domU hang (state b), how to interpret this qemu log after xm create

[Guangning YU <yugn@xxxxxx>]

Hi there,

I have been following a online tutorial to create my home server.  

Reference: http://linux-bsd-sharing.blogspot.com.au/2012/10/howto-xen-413-windows-8-hvm-domu-with.html

I have followed the guide and xm create my .cfg file. The vm went into state b. VNC into the vm, only see black screen. I don’t quite understand the log file. Could anyone please help me interpret the log and point me to the right direction? Thank you very much!!!

Cheers,

Jason

===Here is my .cfg file

kernel = 'hvmloader'

builder = 'hvm'

vcpus = '4'

memory = '4096'

disk = ['file:/etc/xen/images/HVM_M7_x64.img,hda,w','file:/etc/xen/ISO/Micro_7_Ultimate_SP1_x64.iso,hdc:cdrom,r']

name = 'Micro7-x64'

vif = [ 'mac=00:16:3E:51:20:01,bridge=xenbr0,model=e1000' ]

boot = 'dc'

acpi = '1'

apic = '1'

viridian = '1'

xen_platform_pci='1'

sdl = '0'

vnc = '1'

vnclisten = '0.0.0.0'

vncpasswd = ''

stdvga = '0'

usb = '1'

usbdevice = 'tablet'

===Here is the xm list result

root@DB-XEN:/etc/xen# xm list

Name                                        ID   Mem VCPUs      State   Time(s)

Domain-0                                     0  1540     4     r-----     91.2

Micro7-x64                                   4  4096     4     -b----     34.8

    

===uname –a 

Linux DB-XEN 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

===Here is /var/log/xen/Qemu-dm-Micro7_x64.log content

domid: 4

-c config qemu network with xen bridge for 

vif4.0-emu xenbr0

Using file /etc/xen/images/HVM_M7_x64.img in read-write mode

Using file /etc/xen/ISO/Micro_7_Ultimate_SP1_x64.iso in read-only mode

Watching /local/domain/0/device-model/4/logdirty/cmd

Watching /local/domain/0/device-model/4/command

Watching /local/domain/4/cpu

qemu_map_cache_init nr_buckets = 10000 size 4194304

shared page at pfn feffd

buffered io page at pfn feffb

Guest uuid = 17603b76-104d-b21d-f630-fbdc1814e48f

Time offset set 0

populating video RAM at ff000000

mapping video RAM from ff000000

Register xen platform.

Done register platform.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

xs_read(/local/domain/0/device-model/4/xen_extended_power_mgmt): read error

xs_read(): vncpasswd get error. /vm/17603b76-104d-b21d-f630-fbdc1814e48f/vncpasswd.

medium change watch on `hdc' (index: 1): /etc/xen/ISO/Micro_7_Ultimate_SP1_x64.iso

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

Log-dirty: no command yet.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

char device redirected to /dev/pts/1

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

vcpu-set: watch node error.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xs_read(/local/domain/4/log-throttling): read error

qemu: ignoring not-understood drive `/local/domain/4/log-throttling'

medium change watch on `/local/domain/4/log-throttling' - unknown device, ignored

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

xen be: console-0: xen be: console-0: initialise() failed

initialise() failed

cirrus vga map change while on lfb mode

mapping vram to f0000000 - f0400000

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

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