stubdom

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

stubdom

席康杰

Hi,

    I read slide Performance Tuning Xen, find stubdom can boost HVM performance,

so I try it, the wiki Device_Model_Stub_Domains says use the ‘device_model_stubdomain_override’

option in guest configuration file:

    device_model_stubdomain_override = 1

 

This is my cfg file:

 

name = "test_stubdom"

builder = "hvm"

vcpus = 2

memory = 1024

disk = ["tap:qcow2:test_stubdom.img,hda,w"]

vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]

boot = "c"

pae = 1

acpi = 1

apic = 1

localtime = 1

vga="stdvga"

vgaram=64

vnc = 1

vnclisten = "0.0.0.0"

vncdisplay = 128

vncunused = 0

vncpasswd = "test"

device_model_linux_stubdomain_override = 1

 

The vm can start, but it has no difference with “device_model_linux_stubdomain_override = 0”.

The dom0 also has backend qemu-system-i386 process for domain test_stubdom.

 

Did I use stubdom wrong? or how to use stubdom? anyone has an idea?

 

 

Thanks!


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: stubdom

George Dunlap
On Tue, May 17, 2016 at 1:37 PM, 席康杰 <[hidden email]> wrote:

> Hi,
>
>     I read slide Performance Tuning Xen, find stubdom can boost HVM
> performance,
>
> so I try it, the wiki Device_Model_Stub_Domains says use the
> ‘device_model_stubdomain_override’
>
> option in guest configuration file:
>
>     device_model_stubdomain_override = 1
>
>
>
> This is my cfg file:
>
>
>
> name = "test_stubdom"
>
> builder = "hvm"
>
> vcpus = 2
>
> memory = 1024
>
> disk = ["tap:qcow2:test_stubdom.img,hda,w"]
>
> vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]
>
> boot = "c"
>
> pae = 1
>
> acpi = 1
>
> apic = 1
>
> localtime = 1
>
> vga="stdvga"
>
> vgaram=64
>
> vnc = 1
>
> vnclisten = "0.0.0.0"
>
> vncdisplay = 128
>
> vncunused = 0
>
> vncpasswd = "test"
>
> device_model_linux_stubdomain_override = 1
>
>
>
> The vm can start, but it has no difference with
> “device_model_linux_stubdomain_override = 0”.
>
> The dom0 also has backend qemu-system-i386 process for domain test_stubdom.
>
>
>
> Did I use stubdom wrong? or how to use stubdom? anyone has an idea?

Why did you add "linux" in the middle of that option?
device_model_linux_stubdomain_override is not a parameter that xl
knows, so it just ignores it.

 -George

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: stubdom

Manuel Knitza


Von meinem iPhone gesendet

> Am 18.05.2016 um 11:45 schrieb George Dunlap <[hidden email]>:
>
>> On Tue, May 17, 2016 at 1:37 PM, 席康杰 <[hidden email]> wrote:
>> Hi,
>>
>>    I read slide Performance Tuning Xen, find stubdom can boost HVM
>> performance,
>>
>> so I try it, the wiki Device_Model_Stub_Domains says use the
>> ‘device_model_stubdomain_override’
>>
>> option in guest configuration file:
>>
>>    device_model_stubdomain_override = 1
>>
>>
>>
>> This is my cfg file:
>>
>>
>>
>> name = "test_stubdom"
>>
>> builder = "hvm"
>>
>> vcpus = 2
>>
>> memory = 1024
>>
>> disk = ["tap:qcow2:test_stubdom.img,hda,w"]
>>
>> vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]
>>
>> boot = "c"
>>
>> pae = 1
>>
>> acpi = 1
>>
>> apic = 1
>>
>> localtime = 1
>>
>> vga="stdvga"
>>
>> vgaram=64
>>
>> vnc = 1
>>
>> vnclisten = "0.0.0.0"
>>
>> vncdisplay = 128
>>
>> vncunused = 0
>>
>> vncpasswd = "test"
>>
>> device_model_linux_stubdomain_override = 1
>>
>>
>>
>> The vm can start, but it has no difference with
>> “device_model_linux_stubdomain_override = 0”.
>>
>> The dom0 also has backend qemu-system-i386 process for domain test_stubdom.
>>
>>
>>
>> Did I use stubdom wrong? or how to use stubdom? anyone has an idea?
>
> Why did you add "linux" in the middle of that option?
> device_model_linux_stubdomain_override is not a parameter that xl
> knows, so it just ignores it.
>
> -George
>
> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: stubdom

Manuel Knitza
In reply to this post by George Dunlap


Von meinem iPhone gesendet

Am 18.05.2016 um 11:45 schrieb George Dunlap <[hidden email]>:

On Tue, May 17, 2016 at 1:37 PM, 席康杰 <[hidden email]> wrote:
Hi,

   I read slide Performance Tuning Xen, find stubdom can boost HVM
performance,

so I try it, the wiki Device_Model_Stub_Domains says use the
‘device_model_stubdomain_override’

option in guest configuration file:

   device_model_stubdomain_override = 1



This is my cfg file:



name = "test_stubdom"

builder = "hvm"

vcpus = 2

memory = 1024

disk = ["tap:qcow2:test_stubdom.img,hda,w"]

vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]

boot = "c"

pae = 1

acpi = 1

apic = 1

localtime = 1

vga="stdvga"

vgaram=64

vnc = 1

vnclisten = "0.0.0.0"

vncdisplay = 128

vncunused = 0

vncpasswd = "test"

device_model_linux_stubdomain_override = 1



The vm can start, but it has no difference with
“device_model_linux_stubdomain_override = 0”.

The dom0 also has backend qemu-system-i386 process for domain test_stubdom.



Did I use stubdom wrong? or how to use stubdom? anyone has an idea?

Why did you add "linux" in the middle of that option?
device_model_linux_stubdomain_override is not a parameter that xl
knows, so it just ignores it.
Seems to be a somehow orphaned wrong configuration parameter:

Then, to run the stubdom, add this to your xl configuration file: device_model_linux_stubdomain_override = 1
(c.f. https://blog.xenproject.org/2012/12/12/linux-stub-domain/)

-George

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

答复: stubdom

席康杰
In reply to this post by George Dunlap
Sorry, I referenced this blog https://blog.xenproject.org/2012/12/12/linux-stub-domain/.

Now my guest configuration file:

name = "test_stubdom"
builder = "hvm"
vcpus = 2
memory = 1024
disk = ["tap:qcow2:test_stubdom.img,hda,w"]
vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
vga="stdvga"
vgaram=64
vnc = 1
vnclisten = "0.0.0.0"
vncdisplay = 128
vncunused = 0
vncpasswd = "test"
device_model_version = "qemu-xen-traditional"
device_model_stubdomain_override = 1

However, after creating guest, I use vnc to view the guest, the screen is black.

# xl list
Name                                ID   Mem VCPUs      State   Time(s)
Domain-0                                     0 50162    24     r-----  687163.0
test_stubdom-dm                       2    32     1     -b----       0.0
test_xp_stubdom                       6028  1015     1     ------       0.0

The guest os is windows xp.

Do you have any idea?

Thanks!

-----邮件原件-----
发件人: [hidden email] [mailto:[hidden email]] 代表 George Dunlap
发送时间: 2016年5月18日 17:45
收件人: 席康杰
抄送: [hidden email]
主题: Re: [Xen-users] stubdom

On Tue, May 17, 2016 at 1:37 PM, 席康杰 <[hidden email]> wrote:

> Hi,
>
>     I read slide Performance Tuning Xen, find stubdom can boost HVM
> performance,
>
> so I try it, the wiki Device_Model_Stub_Domains says use the
> ‘device_model_stubdomain_override’
>
> option in guest configuration file:
>
>     device_model_stubdomain_override = 1
>
>
>
> This is my cfg file:
>
>
>
> name = "test_stubdom"
>
> builder = "hvm"
>
> vcpus = 2
>
> memory = 1024
>
> disk = ["tap:qcow2:test_stubdom.img,hda,w"]
>
> vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]
>
> boot = "c"
>
> pae = 1
>
> acpi = 1
>
> apic = 1
>
> localtime = 1
>
> vga="stdvga"
>
> vgaram=64
>
> vnc = 1
>
> vnclisten = "0.0.0.0"
>
> vncdisplay = 128
>
> vncunused = 0
>
> vncpasswd = "test"
>
> device_model_linux_stubdomain_override = 1
>
>
>
> The vm can start, but it has no difference with
> “device_model_linux_stubdomain_override = 0”.
>
> The dom0 also has backend qemu-system-i386 process for domain test_stubdom.
>
>
>
> Did I use stubdom wrong? or how to use stubdom? anyone has an idea?

Why did you add "linux" in the middle of that option?
device_model_linux_stubdomain_override is not a parameter that xl knows, so it just ignores it.

 -George
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: 答复: stubdom

Wei Liu-2
On Wed, May 18, 2016 at 11:24:44AM +0000, 席康杰 wrote:
> Sorry, I referenced this blog https://blog.xenproject.org/2012/12/12/linux-stub-domain/.

Sadly that work is not yet completed.

>
> Now my guest configuration file:
>
> name = "test_stubdom"
> builder = "hvm"
> vcpus = 2
> memory = 1024
> disk = ["tap:qcow2:test_stubdom.img,hda,w"]
> vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"]
> boot = "c"
> pae = 1
> acpi = 1
> apic = 1
> localtime = 1
> vga="stdvga"
> vgaram=64
> vnc = 1
> vnclisten = "0.0.0.0"
> vncdisplay = 128
> vncunused = 0
> vncpasswd = "test"
> device_model_version = "qemu-xen-traditional"
> device_model_stubdomain_override = 1
>
> However, after creating guest, I use vnc to view the guest, the screen is black.
>
> # xl list
> Name                                ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0 50162    24     r-----  687163.0
> test_stubdom-dm                       2    32     1     -b----       0.0
> test_xp_stubdom                       6028  1015     1     ------       0.0
>

Your guest doesn't appear to be running. The CPU time is 0.0. What
version of xen do you use?

Wei.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

答复: 答复: stubdom

席康杰
xen4.5.1 on centos6.5, I compiled it from source code. kernel is 3.10.20-11.el6.centos.alt.x86_64


# xl -vvv create test_stubdom.cfg

Formatting 'test_stubdom.img', fmt=qcow2 size=32212254720 encryption=off cluster_size=65536 lazy_refcounts=off
Parsing config from test_stubdom.cfg
libxl: debug: libxl_create.c:1507:do_domain_create: ao 0x16fa3e0: create: how=(nil) callback=(nil) poller=0x16faac0
libxl: info: libxl_create.c:773:initiate_domain_create: change domid to vncdisplay + 5900: 6028
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:252:disk_try_backend: Disk vdev=hda, backend phy unsuitable due to format qcow2
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=hda, using backend qdisk
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=unknown
libxl: debug: libxl_device.c:215:disk_try_backend: Disk vdev=hdc, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=hdc, using backend qdisk
libxl: debug: libxl_create.c:910:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:323:libxl__bootloader_run: not a PV domain, skipping bootloader
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fb270: deregister unregistered
libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=12, nr_vcpus=26, free_memkb=39841
libxl: detail: libxl_dom.c:196:numa_place_domain: NUMA placement candidate with 1 nodes, 12 cpus and 39841 KB free selected
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbd484
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bd484
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
xc: detail:   Loader:   0000000000100000->00000000001bd484
xc: detail:   Modules:  0000000000000000->0000000000000000
xc: detail:   TOTAL:    0000000000000000->000000003f800000
xc: detail:   ENTRY:    0000000000100000
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail:   4KB PAGES: 0x0000000000000200
xc: detail:   2MB PAGES: 0x00000000000001fb
xc: detail:   1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x7f806de0b000 -> 0x7f806debf2f4
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=qdisk
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fccf0: deregister unregistered
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16f3500: deregister unregistered
libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=12, nr_vcpus=27, free_memkb=38816
libxl: detail: libxl_dom.c:196:numa_place_domain: NUMA placement candidate with 1 nodes, 12 cpus and 38816 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline=" -d 6028", features=""
libxl: debug: libxl_dom.c:533:libxl__build_pv: pv kernel mapped 0 path /usr/local/lib/xen/boot/ioemu-stubdom.gz
domainbuilder: detail: xc_dom_kernel_file: filename="/usr/local/lib/xen/boot/ioemu-stubdom.gz"
domainbuilder: detail: xc_dom_malloc_filemap    : 2247 kB
domainbuilder: detail: xc_dom_malloc            : 13516 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x231da8 -> 0xd33260
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.5, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ...
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x565008
xc: detail: elf_parse_binary: memory: 0x0 -> 0x565008
xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic"
xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS"
xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0"
xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0"
xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0"
xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2"
xc: detail: elf_xen_parse_guest_info: LOADER="generic"
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail:     virt_base        = 0x0
xc: detail:     elf_paddr_offset = 0x0
xc: detail:     virt_offset      = 0x0
xc: detail:     virt_kstart      = 0x0
xc: detail:     virt_kend        = 0x565008
xc: detail:     virt_entry       = 0x0
xc: detail:     p2m_base         = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x565008
domainbuilder: detail: xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x2000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x0 -> 0x566000  (pfn 0x0 + 0x566 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x0+0x566 at 0x7f806a8ef000
xc: detail: elf_load_binary: phdr 0 at 0x7f806a8ef000 -> 0x7f806ae54008
domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 0x566000 -> 0x576000  (pfn 0x566 + 0x10 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x566+0x10 at 0x7f806deb9000
domainbuilder: detail: xc_dom_alloc_page   :   start info   : 0x576000 (pfn 0x576)
domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 0x577000 (pfn 0x577)
domainbuilder: detail: xc_dom_alloc_page   :   console      : 0x578000 (pfn 0x578)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x0000000000000000 -> 0x000000003fffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x0000000000000000 -> 0x00000000007fffff, 4 table(s)
domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 0x579000 -> 0x580000  (pfn 0x579 + 0x7 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x579+0x7 at 0x7f806ded1000
domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 0x580000 (pfn 0x580)
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x581000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x800000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x2000
domainbuilder: detail: clear_page: pfn 0x578, mfn 0xe37c6e
domainbuilder: detail: clear_page: pfn 0x577, mfn 0xe37c6f
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x576+0x1 at 0x7f806deda000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 13616 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 2247 kB
domainbuilder: detail:       domU mmap          : 5624 kB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x7da91
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x579 mfn 0xe37c6d
domainbuilder: detail: launch_vm: called, ctxt=0x7f806dedb004
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=qdisk
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16f67b0: deregister unregistered
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16f74a0: deregister unregistered
libxl: debug: libxl_dm.c:1430:libxl__spawn_local_dm: Spawning device-model /usr/local/lib/xen/bin/qemu-dm with arguments:
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   /usr/local/lib/xen/bin/qemu-dm
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   -d
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   5
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   -domain-name
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   test_stubdom-dm
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   -vnc
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   0.0.0.0:128,password
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   -M
libxl: debug: libxl_dm.c:1432:libxl__spawn_local_dm:   xenpv
libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x16fb9e8 wpath=/local/domain/0/device-model/5/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1523:do_domain_create: ao 0x16fa3e0: inprogress: poller=0x16faac0, flags=i
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x16fb9e8 wpath=/local/domain/0/device-model/5/state token=3/0: event epath=/local/domain/0/device-model/5/state
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x16fb9e8 wpath=/local/domain/0/device-model/5/state token=3/0: event epath=/local/domain/0/device-model/5/state
libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x16fb9e8 wpath=/local/domain/0/device-model/5/state token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fb9e8: deregister unregistered
libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x16fedd8 wpath=/local/domain/0/backend/vif/5/0/state token=3/1: register slotnum=3
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x16fedd8 wpath=/local/domain/0/backend/vif/5/0/state token=3/1: event epath=/local/domain/0/backend/vif/5/0/state
libxl: debug: libxl_event.c:834:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x16fedd8 wpath=/local/domain/0/backend/vif/5/0/state token=3/1: event epath=/local/domain/0/backend/vif/5/0/state
libxl: debug: libxl_event.c:830:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 ok
libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x16fedd8 wpath=/local/domain/0/backend/vif/5/0/state token=3/1: deregister slotnum=3
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fedd8: deregister unregistered
libxl: debug: libxl_device.c:1028:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_aoutils.c:513:libxl__async_exec_start: forking to execute: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fee60: deregister unregistered
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x16fee60: deregister unregistered
libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x1700078 wpath=/local/domain/0/backend/vif/6028/0/state token=3/2: register slotnum=3
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x1700078 wpath=/local/domain/0/backend/vif/6028/0/state token=3/2: event epath=/local/domain/0/backend/vif/6028/0/state
libxl: debug: libxl_event.c:834:devstate_watch_callback: backend /local/domain/0/backend/vif/6028/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x1700078 wpath=/local/domain/0/backend/vif/6028/0/state token=3/2: event epath=/local/domain/0/backend/vif/6028/0/state
libxl: debug: libxl_event.c:830:devstate_watch_callback: backend /local/domain/0/backend/vif/6028/0/state wanted state 2 ok
libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x1700078 wpath=/local/domain/0/backend/vif/6028/0/state token=3/2: deregister slotnum=3
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x1700078: deregister unregistered
libxl: debug: libxl_device.c:1028:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_aoutils.c:513:libxl__async_exec_start: forking to execute: /etc/xen/scripts/vif-bridge online
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x1700100: deregister unregistered
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x1700100: deregister unregistered
libxl: debug: libxl_event.c:1941:libxl__ao_progress_report: ao 0x16fa3e0: progress report: ignored
libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x16fa3e0: complete, rc=0
libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x16fa3e0: destroy
xc: debug: hypercall buffer: total allocations:1423 total releases:1423
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:1389 misses:4 toobig:30

-----邮件原件-----
发件人: Wei Liu [mailto:[hidden email]]
发送时间: 2016年5月18日 22:49
收件人: 席康杰
抄送: George Dunlap; [hidden email]; Wei Liu
主题: Re: [Xen-users] 答复: stubdom

On Wed, May 18, 2016 at 11:24:44AM +0000, 席康杰 wrote:
> Sorry, I referenced this blog https://blog.xenproject.org/2012/12/12/linux-stub-domain/.

Sadly that work is not yet completed.

>
> Now my guest configuration file:
>
> name = "test_stubdom"
> builder = "hvm"
> vcpus = 2
> memory = 1024
> disk = ["tap:qcow2:test_stubdom.img,hda,w"]
> vif = ["type=ioemu, bridge=xenbr0, mac=00:16:3e:eb:ca:80"] boot = "c"
> pae = 1
> acpi = 1
> apic = 1
> localtime = 1
> vga="stdvga"
> vgaram=64
> vnc = 1
> vnclisten = "0.0.0.0"
> vncdisplay = 128
> vncunused = 0
> vncpasswd = "test"
> device_model_version = "qemu-xen-traditional"
> device_model_stubdomain_override = 1
>
> However, after creating guest, I use vnc to view the guest, the screen is black.
>
> # xl list
> Name                                ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0 50162    24     r-----  687163.0
> test_stubdom-dm                       2    32     1     -b----       0.0
> test_xp_stubdom                       6028  1015     1     ------       0.0
>

Your guest doesn't appear to be running. The CPU time is 0.0. What version of xen do you use?

Wei.
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: 答复: 答复: stubdom

Wei Liu-2
On Wed, May 18, 2016 at 03:07:39PM +0000, 席康杰 wrote:
> xen4.5.1 on centos6.5, I compiled it from source code. kernel is 3.10.20-11.el6.centos.alt.x86_64
>
>
> # xl -vvv create test_stubdom.cfg
>

I think the domain creation worked fine.

Anything interesting in xl dmesg? Note that you might need to bump log
level.

Add the following options to xen command line to bump log level:
loglvl=all guest_loglvl=all.

Wei.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

答复: 答复: 答复: stubdom

席康杰
sorry

In my /boot/grub/grub.conf:
kernel /xen.gz dom0_mem=51366096 loglvl=all guest_loglvl=all

Firstly I run 'xl dmesg -c', then run 'xl -vvv create test_stubdom.cfg'
There is no output from 'xl dmesg'


-----邮件原件-----
发件人: Wei Liu [mailto:[hidden email]]
发送时间: 2016年5月18日 23:49
收件人: 席康杰
抄送: Wei Liu; George Dunlap; [hidden email]
主题: Re: 答复: [Xen-users] 答复: stubdom

On Wed, May 18, 2016 at 03:07:39PM +0000, 席康杰 wrote:
> xen4.5.1 on centos6.5, I compiled it from source code. kernel is
> 3.10.20-11.el6.centos.alt.x86_64
>
>
> # xl -vvv create test_stubdom.cfg
>

I think the domain creation worked fine.

Anything interesting in xl dmesg? Note that you might need to bump log level.

Add the following options to xen command line to bump log level:
loglvl=all guest_loglvl=all.

Wei.
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: 答复: 答复: 答复: stubdom

Wei Liu-2
On Thu, May 19, 2016 at 03:38:18AM +0000, 席康杰 wrote:
> sorry
>
> In my /boot/grub/grub.conf:
> kernel /xen.gz dom0_mem=51366096 loglvl=all guest_loglvl=all
>

Yes, something like this.

Mine has "loglvl=all guest_loglvl=all com1=115200,8n1 console=com1,vga
console_to_ring sync_console".

You can try mine as well.

> Firstly I run 'xl dmesg -c', then run 'xl -vvv create test_stubdom.cfg'
> There is no output from 'xl dmesg'
>

Not even output from hvmloader and stubdom?  That's not very normal. You
can as least have some output. Please try my command line and see if it
makes a difference.

Wei.



>
> -----邮件原件-----
> 发件人: Wei Liu [mailto:[hidden email]]
> 发送时间: 2016年5月18日 23:49
> 收件人: 席康杰
> 抄送: Wei Liu; George Dunlap; [hidden email]
> 主题: Re: 答复: [Xen-users] 答复: stubdom
>
> On Wed, May 18, 2016 at 03:07:39PM +0000, 席康杰 wrote:
> > xen4.5.1 on centos6.5, I compiled it from source code. kernel is
> > 3.10.20-11.el6.centos.alt.x86_64
> >
> >
> > # xl -vvv create test_stubdom.cfg
> >
>
> I think the domain creation worked fine.
>
> Anything interesting in xl dmesg? Note that you might need to bump log level.
>
> Add the following options to xen command line to bump log level:
> loglvl=all guest_loglvl=all.
>
> Wei.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users