[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

çåï Re: çåï RE: çåïRE: [Xen-devel] start stubdom issue



Hi all, 

     I have started stubdom, thank all of you. But I still met a problem, that 
is I found stubdom block when it run 107s. the message in "xm li" :
                    Domain-0                                     0  1719     2  
   r-----    171.9
                    hvmachine                                    1   256     1  
   -b----    110.6
                     hvmachine-dm                                 2    32     1 
    -b----      8.2  
and qemu.log :

                  
Using config file "/etc/xen/vm/hvmachine-dm".
Started domain hvmachine-dm
Xen Minimal OS!
^Mstart_info:   0x311000
^M  nr_pages:   8192  shared_inf: 001d1000
^M  pt_base:    0x314000  mod_start:  0x0
^M  mod_len:    0
^M  flags:      0x0
^M  cmd_line:    -d 1
^M  stack:      0x2e8620-0x308620
^MMM: Init
^M  _text:        0x0
^M  _etext:       0xd8828
^M  _erodata:     0x105000
^M  _edata:       0x1101e8
^M  stack start:  0x2e8620
^M  _end:         0x308db8
^M  start_pfn:    31c
^M  max_pfn:      2000
^MMapping memory range 0x400000 - 0x2000000
^Msetting 0x0-0x105000 readonly
^Mskipped 0x1000
^MMM: Initialise page allocator for 32a000(32a000)-0(2000000)
^MMM: done
^MDemand map pfns at 2001000-82001000.
^MHeap resides at 82002000-c2002000.
^MInitialising timer interface
^MInitialising console ... done.
^Mgnttab_table mapped at 0x2001000.
^MInitialising scheduler
^MThread "Idle": pointer: 0x82002008, stack: 0x350000
^MInitialising xenbus
^MThread "xenstore": pointer: 0x82002478, stack: 0x360000
^MDummy main: start_info=0x308720
^MThread "main": pointer: 0x820028e8, stack: 0x370000
^M[main] Waiting for network.
^M************************ NETFRONT for device/vif/0 **********
best regards,
-- James
>>> Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> 08å09æ19æ äå 19:40 >>>
James Song, le Fri 19 Sep 2008 03:12:24 -0600, a Ãcrit :
> Path changed backend/vfs/exports/requests/10/0/frontend
> Handling connection from dom=10, for export=0
> Frontend found at: /local/domain/10/device/vfs/0 (gref=1789, evtchn=5)
> Our own dom_id=0
> ERROR Internal error: Could not open grant table interface (22 = Invalid 
> argument)
> fs-backend: fs-backend.c:239: handle_connection: Assertion `mount->gnth != 
> -1' failed.

Mmm, are you perhaps running an old version of the dom0 kernel?  Could
you strace fs-backend to know which precise syscall is failing?
M
^Mnet TX ring size 256
^Mnet RX ring size 256
^Mbackend at /local/domain/0/backend/vif/2/0
^Mmac is 00:16:3e:61:e0:fb
^M**************************
^M[main] IP 9302cf2c netmask ffff0000 gateway 0.
^M[main] TCP/IP bringup begins.
^MThread "tcpip_thread": pointer: 0x82004190, stack: 0x480000
^M[tcpip_thread] TCP/IP bringup ends.
^M[main] Network is ready.
^MIniting FS fronend(s).
^MFS export [dom=0, id=0] found
^MInitialising FS fortend to backend dom 0
^MAllocating request array for import 0, nr_entries = 128.
^MOur own id is 2
^MBackend found at /local/domain/0/backend/vfs/0
^MBackend ready.
^Mdom vm is at /vm/345a524f-1139-9722-f455-a643e8f95d5a
^M"main" "-d" "1" "-domain-name" "hvmachine" "-vnc" "147.2.207.44:0" 
"-vncunused" "-vcpus" "1" "-boot" "c" "-acpi" "-net" 
"nic,vlan=1,macaddr=00:16:3e:6a:65:
2c,model=rtl8139" "-net" "tap,vlan=1,ifname=tap1.0,bridge=eth0"
^Mdomid: 1
^Mqemu: the number of cpus is 1
^Mxs_daemon_open -> 4, 0x10e1a4
^Mxs_read(/local/domain/2/device/vbd/768/phantom_vbd): ENOENT
^M******************* BLKFRONT for /local/domain/2/device/vbd/768 **********
^M
^M
^Mbackend at /local/domain/0/backend/vbd/2/768
^MFailed to read /local/domain/0/backend/vbd/2/768/feature-flush-cache.
^M16777216 sectors of 0 bytes
^M**************************
^Mblk_open(/local/domain/2/device/vbd/768) -> 5
^Mxs_directory(/local/domain/2/device/vkbd): ENOENT
^Mxs_directory(/local/domain/2/device/vfb): ENOENT
^Mxs_watch(/local/domain/0/device-model/1/logdirty/next-active, logdirty)
^MWatching /local/domain/0/device-model/1/logdirty/next-active
^Mxs_watch(/local/domain/0/device-model/1/command, dm-command)
Watching /local/^M************************ NETFRONT for device/vif/1 **********
^M
^M
^Mnet TX ring size 256
^Mnet RX ring size 256
^Mbackend at /local/domain/0/backend/vif/2/1
^Mmac is 00:16:3e:21:a2:94
^M**************************
^Mtap_open(device/vif/1) -> 6
^Mopen(/usr/share/xen/qemu/keymaps/en-us, 0)-> 7
^Mopen(/usr/share/xen/qemu/keymaps/common, 0)-> 8
^Mopen(/usr/share/xen/qemu/keymaps/modifiers, 0)-> 9
^Mclose(9)
^Mclose(8)
^Mclose(7)
^Mxs_read(/vm/345a524f-1139-9722-f455-a643e8f95d5a/vncpasswd): EACCES
^Mxs_read(): vncpasswd get error. 
/vm/345a524f-1139-9722-f455-a643e8f95d5a/vncpasswd.
^Msocket -> 7
^Mcan't store dev null name for domid 1 in /monitor from a stub domain
^Mcan't store dev vc name for domid 1 in /parallel/0 from a stub domain
^Mqemu_map_cache_init nr_buckets = 4000 size 196608
^Mshared page at pfn fffe
^Mxc_map_foreign_range(fffe, 4096)
^Mbuffered io page at pfn fffc
^Mxc_map_foreign_range(fffc, 4096)
^MTime offset set 0
^Mevtchn_open() -> 8
^Mxc_evtchn_bind_interdomain(1, 4) = 0
^M******************* PCIFRONT for device/pci/0 **********
^M
^M
^MFailed to read device/pci/0/backend-id.
^Mno backend
^Mpcilib: minios_init open failed
^MRegister xen platform.
Done register platform.
^Mxs_read_watch() -> /local/domain/0/device-model/1/command dm-command
^Mxs_read(/local/domain/0/device-model/1/command): ENOENT
^Mxs_read_watch() -> /local/domain/0/device-model/1/logdirty/next-active 
logdirty
^Mxs_read(/local/domain/0/device-model/1/logdirty/key): ENOENT
^MFailed allocation for dom 1: 2048 extents of order 0
^MFailed to populate physmap
^MFailed set_mm_mapping
^MNULL vram_pointer
^Maccepted on 7 -> 9
^Mgpe_en_write: addr=0x1f6c, val=0x0.
^Mgpe_sts_write: addr=0x1f68, val=0xff.
^Mgpe_en_write: addr=0x1f6d, val=0x0.
^Mgpe_sts_write: addr=0x1f69, val=0xff.
^Mgpe_en_write: addr=0x1f6e, val=0x0.
^Mgpe_sts_write: addr=0x1f6a, val=0xff.
^Mgpe_en_write: addr=0x1f6f, val=0x0.
^Mgpe_sts_write: addr=0x1f6b, val=0xff.
^Mgpe_en_write: addr=0x1f6c, val=0x8.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^MACPI PCI hotplug: read addr=0x10c1, val=0x0.
^MACPI PCI hotplug: read addr=0x10c2, val=0x0.
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
^Mblock error -2 for op 2
..

It seems that pci backend not working.  But I have insmod pciback.ko. what's 
wrong I make. Moreover, I can't connet studbom via vnc. attatchment is my 
configure file:

Samuel

Attachment: hvmachine
Description: Binary data

Attachment: hvmachine-dm
Description: Binary data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.