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

Re: [Xen-users] can't start hvm/pvhvm on xen 4.4 or xen4.6


  • To: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • From: James Okken <James.Okken@xxxxxxxxxxxx>
  • Date: Thu, 20 Apr 2017 20:05:08 +0000
  • Accept-language: en-US
  • Delivery-date: Thu, 20 Apr 2017 20:06:18 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AdK5KFyC/NTK9XC4Rs6jcww0eC9snAAwSsRwAAlAzUA=
  • Thread-topic: can't start hvm/pvhvm on xen 4.4 or xen4.6

These systems are pretty brand new Intel E5 –v3s

 

TXT is disabled in the BIOS.

 

[root@xen ~]# xl dmesg | grep -i virt

(XEN) I/O virtualisation enabled

(XEN)  - APIC MMIO access virtualisation

(XEN)  - Virtual-Processor Identifiers (VPID)

(XEN)  - Virtual NMI

(XEN) VIRTUAL MEMORY ARRANGEMENT:

 

 

[root@xen ~]# xl dmesg | grep -i hvm

(XEN) HVM: ASIDs enabled.

(XEN) HVM: VMX enabled

(XEN) HVM: Hardware Assisted Paging (HAP) detected

(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB

 

[root@xen~]# xl info

host                   : xen

release                : 4.9.13-22.el7.x86_64

version                : #1 SMP Sun Feb 26 22:15:59 UTC 2017

machine                : x86_64

nr_cpus                : 32

max_cpu_id             : 31

nr_nodes               : 2

cores_per_socket       : 8

threads_per_core       : 2

cpu_mhz                : 2400

hw_caps                : bfebfbff:2c100800:00000000:00003f00:17bee3ff:00000000:00000001:00000000

virt_caps              : hvm hvm_directio

total_memory           : 65490

free_memory            : 63619

sharing_freed_memory   : 0

sharing_used_memory    : 0

outstanding_claims     : 0

free_cpus              : 0

xen_major              : 4

xen_minor              : 6

xen_extra              : .3-8.el7

xen_version            : 4.6.3-8.el7

xen_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

xen_scheduler          : credit

xen_pagesize           : 4096

platform_params        : virt_start=0xffff800000000000

xen_changeset          : Wed Feb 15 02:12:22 2017 -0600 git:149e51c-dirty

xen_commandline        : placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all

cc_compiler            : gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11)

cc_compile_by          : mockbuild

cc_compile_domain      : centos.org

cc_compile_date        : Tue Feb 28 14:33:09 UTC 2017

xend_config_format     : 4

 

James Okken

Lab Manager

Dialogic Research Inc.
4 Gatehall Drive

Parsippany
NJ 07054
USA

Tel:       973 967 5179
Email:   james.okken@dialogic.com

Web:    www.dialogic.comThe Network Fuel Company

This e-mail is intended only for the named recipient(s) and may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. No waiver of privilege, confidence or otherwise is intended by virtue of communication via the internet. Any unauthorized use, dissemination or copying is strictly prohibited. If you have received this e-mail in error, or are not named as a recipient, please immediately notify the sender and destroy all copies of this e-mail.

 

From: James Okken
Sent: Thursday, April 20, 2017 11:27 AM
To: 'xen-users@xxxxxxxxxxxxx'
Subject: RE: can't start hvm/pvhvm on xen 4.4 or xen4.6

 

Hi again

 

Just a bit more info

 

The same thing occurs when I use the hvm template cfg file: xlexample.hvm

Also “xl dmesg” does not show any messages.

 

 

And one quick question: do I need a hard drive or cdrom defined in order for a domain to start? Can I comment the disk  = [‘ line until I get the domain to start?

 

thanks

 

 

 

From: James Okken
Sent: Wednesday, April 19, 2017 1:29 PM
To: 'xen-users@xxxxxxxxxxxxx'
Subject: can't start hvm/pvhvm on xen 4.4 or xen4.6

 

Hi all,

 

Sorry for the novice question which is probably answered somewhere I just can’t find.

 

I am trying create a hvm/pvhvm but keep getting errors. Any suggestions would be appreciated!

 

I’m using two hosts Ubuntu 14.4 with xen 4.4, and Centos 7.2 with xen4.6. Both seem to have the same error.

 

I’ve tried a number of different settings shown on different online threads, to no avail.

Usually I get the error:

libxl: error: libxl_dm.c:1872:device_model_spawn_outcome: domain 87 device model: spawn failed (rc=-3)

libxl: error: libxl_create.c:1344:domcreate_devmodel_started: device model did not start: -3

 

 

here is one basic iteration of my cfg file, you can see by the commented out lines some of the settings I’ve tried.

(this is on the Centos 7.2 with xen4.6 host)

vi basic.cfg

builder="hvm"

vcpus=4

memory=4096

name="basic"

#bootloader="pygrub"

#firmware_override = "/usr/lib64/xen/boot/hvmloader"

#device_model_version="qemu-xen-traditional"

#device_model = 'qemu-dm'

#device_model_override = '/usr/lib64/xen/bin/qemu-dm'

vif = ["mac=00:15:3f:11:21:30,bridge=xenbr0,rate=100Mb/s"]

disk = [ "raw:/var/lib/xen/images/centos/xen_hvm.img,ioemu:xvda,w" ]

vfb = [ "type=vnc,vnclisten=127.0.0.1,vncdisplay=14,vncpasswd=password" ]

serial="pty"

boot = "c"

sdl=0

monitor=1

pae=1

acpi=1

apic=1

localtime=0

#xen_platform_pci=1

stdvga=1

videoram=16

gfx_passthru=0

_on_poweroff_="destroy"

_on_reboot_="restart"

_on_crash_="restart"

 

 

cat qemu-dm-basic.log

/usr/lib64/xen/bin/qemu-system-i386: symbol lookup error: /usr/lib64/xen/bin/qemu-system-i386: undefined symbol: libusb_free_ss_endpoint_companion_descriptor

 

 

Some command outputs

[root@ xen]# rpm -qa | grep qemu

libvirt-daemon-driver-qemu-1.1.1-29.el7.x86_64

ipxe-roms-qemu-20130517-5.gitc4bce43.el7.noarch

qemu-kvm-1.5.3-60.el7.x86_64

qemu-kvm-common-1.5.3-60.el7.x86_64

qemu-img-1.5.3-60.el7.x86_64

 

[root@xen]# /usr/libexec/qemu-kvm -version

(process:22014): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported

QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-60.el7), Copyright (c) 2003-2008 Fabrice Bellard

[root@sut-1241 xen]#

 

 

 

Finally, the full output of the create:

[root@ xen]# xl -vvvv create -c /etc/xen/basic.cfg

Parsing config from /etc/xen/basic.cfg

libxl: debug: libxl_create.c:1563:do_domain_create: ao 0x157ac00: create: how=(nil) callback=(nil) poller=0x157b2a0

libxl: debug: libxl_device.c:337:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown

libxl: debug: libxl_device.c:366:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy

libxl: debug: libxl_create.c:947:initiate_domain_create: running bootloader

libxl: debug: libxl_bootloader.c:324:libxl__bootloader_run: not a PV domain, skipping bootloader

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x157cf08: deregister unregistered

libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=16, nr_vcpus=36, free_memkb=32127

libxl: detail: libxl_dom.c:181:numa_place_domain: NUMA placement candidate with 1 nodes, 16 cpus and 32127 KB free selected

xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbad44

xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bad44

xc: detail: VIRTUAL MEMORY ARRANGEMENT:

xc: detail:   Loader:   0000000000100000->00000000001bad44

xc: detail:   Modules:  0000000000000000->0000000000000000

xc: detail:   TOTAL:    0000000000000000->00000000ff000000

xc: detail:   ENTRY:    0000000000100610

xc: detail: PHYSICAL MEMORY ALLOCATION:

xc: detail:   4KB PAGES: 0x0000000000000200

xc: detail:   2MB PAGES: 0x00000000000003f7

xc: detail:   1GB PAGES: 0x0000000000000002

xc: detail: elf_load_binary: phdr 0 at 0x7f0c606da000 -> 0x7f0c6078b191

domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x10f000

libxl: debug: libxl_device.c:337:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy

libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch w=0x157df30 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/0: register slotnum=3

libxl: debug: libxl_create.c:1586:do_domain_create: ao 0x157ac00: inprogress: poller=0x157b2a0, flags=i

libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x157df30 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/88/51712/state

libxl: debug: libxl_event.c:884:devstate_callback: backend /local/domain/0/backend/vbd/88/51712/state wanted state 2 still waiting state 1

libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x157df30 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/0: event epath=/local/domain/0/backend/vbd/88/51712/state

libxl: debug: libxl_event.c:880:devstate_callback: backend /local/domain/0/backend/vbd/88/51712/state wanted state 2 ok

libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch w=0x157df30 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/0: deregister slotnum=3

libxl: debug: libxl_device.c:991:device_backend_callback: calling device_backend_cleanup

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x157df30: deregister unregistered

libxl: debug: libxl_linux.c:229:libxl__hotplug_disk: Args and environment ready

libxl: debug: libxl_device.c:1088:device_hotplug: calling hotplug script: /etc/xen/scripts/block add

libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block add

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x157e030: deregister unregistered

libxl: debug: libxl_linux.c:246:libxl__get_hotplug_script_info: num_exec 1, not running hotplug scripts

libxl: debug: libxl_device.c:1075:device_hotplug: No hotplug script to execute

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x157e030: deregister unregistered

libxl: debug: libxl_dm.c:1796:libxl__spawn_local_dm: Spawning device-model /usr/lib64/xen/bin/qemu-system-i386 with arguments:

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   /usr/lib64/xen/bin/qemu-system-i386

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -xen-domid

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   88

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -chardev

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-88,server,nowait

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -no-shutdown

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -mon

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   chardev=libxl-cmd,mode=control

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -chardev

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-88,server,nowait

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -mon

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   chardev=libxenstat-cmd,mode=control

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -nodefaults

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -name

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   basic

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -vnc

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   127.0.0.1:0,to=99

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -display

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   none

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -serial

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   pty

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -device

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   VGA,vgamem_mb=16

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -boot

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   order=c

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -smp

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   4,maxcpus=4

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -device

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   rtl8139,id=nic0,netdev=net0,mac=00:16:3e:10:20:30

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -netdev

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   type=tap,id=net0,ifname=vif88.0-emu,script=no,downscript=no

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -machine

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   xenfv

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -m

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   4080

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   -drive

libxl: debug: libxl_dm.c:1798:libxl__spawn_local_dm:   file=/var/lib/xen/images/centos/xen_1241_hvm_domU3.img,if=ide,index=0,media=disk,format=raw,cache=writeback

libxl: debug: libxl_dm.c:1800:libxl__spawn_local_dm: Spawning device-model /usr/lib64/xen/bin/qemu-system-i386 with additional environment:

libxl: debug: libxl_dm.c:1802:libxl__spawn_local_dm:   XEN_QEMU_CONSOLE_LIMIT=1048576

libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch w=0x157d200 wpath=/local/domain/0/device-model/88/state token=3/1: register slotnum=3

libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x157d200 wpath=/local/domain/0/device-model/88/state token=3/1: event epath=/local/domain/0/device-model/88/state

libxl: debug: libxl_exec.c:399:spawn_watch_event: domain 88 device model: spawn watch p=(null)

libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch w=0x157d200 wpath=/local/domain/0/device-model/88/state token=3/1: deregister slotnum=3

libxl: error: libxl_dm.c:1872:device_model_spawn_outcome: domain 88 device model: spawn failed (rc=-3)

libxl: error: libxl_create.c:1344:domcreate_devmodel_started: device model did not start: -3

libxl: error: libxl_dm.c:1987:kill_device_model: Device Model already exited

libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch w=0x1581bc0 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/2: register slotnum=3

libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x1581bc0 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/2: event epath=/local/domain/0/backend/vbd/88/51712/state

libxl: debug: libxl_event.c:880:devstate_callback: backend /local/domain/0/backend/vbd/88/51712/state wanted state 6 ok

libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch w=0x1581bc0 wpath=/local/domain/0/backend/vbd/88/51712/state token=3/2: deregister slotnum=3

libxl: debug: libxl_device.c:991:device_backend_callback: calling device_backend_cleanup

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x1581bc0: deregister unregistered

libxl: debug: libxl_linux.c:229:libxl__hotplug_disk: Args and environment ready

libxl: debug: libxl_device.c:1088:device_hotplug: calling hotplug script: /etc/xen/scripts/block remove

libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block remove

libxl: debug: libxl_event.c:545:watchfd_callback: watch epath=/local/domain/0/backend/vbd/88/51712/state token=3/2: empty slot

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x1581cc0: deregister unregistered

libxl: debug: libxl_linux.c:246:libxl__get_hotplug_script_info: num_exec 1, not running hotplug scripts

libxl: debug: libxl_device.c:1075:device_hotplug: No hotplug script to execute

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x1581cc0: deregister unregistered

libxl: debug: libxl_linux.c:267:libxl__get_hotplug_script_info: backend_kind 6, no need to execute scripts

libxl: debug: libxl_device.c:1075:device_hotplug: No hotplug script to execute

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch w=0x1582400: deregister unregistered

libxl: debug: libxl.c:1738:devices_destroy_cb: forked pid 19076 for destroy of domain 88

libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x157ac00: complete, rc=-3

libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x157ac00: destroy

libxl: debug: libxl.c:1477:libxl_domain_destroy: ao 0x157f7f0: create: how=(nil) callback=(nil) poller=0x157b2a0

libxl: error: libxl.c:1610:libxl__destroy_domid: non-existant domain 88

libxl: error: libxl.c:1568:domain_destroy_callback: unable to destroy guest with domid 88

libxl: error: libxl.c:1495:domain_destroy_cb: destruction of domain 88 failed

libxl: debug: libxl_event.c:1874:libxl__ao_complete: ao 0x157f7f0: complete, rc=-21

libxl: debug: libxl.c:1486:libxl_domain_destroy: ao 0x157f7f0: inprogress: poller=0x157b2a0, flags=ic

libxl: debug: libxl_event.c:1843:libxl__ao__destroy: ao 0x157f7f0: destroy

xc: debug: hypercall buffer: total allocations:1185 total releases:1185

xc: debug: hypercall buffer: current allocations:0 maximum allocations:3

xc: debug: hypercall buffer: cache current size:3

xc: debug: hypercall buffer: cache hits:1170 misses:3 toobig:12

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

 


Rackspace

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