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

Re: [Xen-users] Xen 4.11 Hypervisor does not start HVM



Ok, I will check.


Thanks for the attention! After cleaning my hvm file so that it lokks like



name='vm'
type='hvm'
vcpus='4'
memory='4096'
disk=['file:/media/STORAGE01/ISO/vm-linux-kde-2019.2-amd64.iso,hdb,cdrom,ro' , '/dev/vm01/vm,raw,hda,rw']
boot='dc'
_on_poweroff_='destroy'
_on_reboot_='restart'
#bios='seabios'
#bootloader='pygrub'
serial='pty'
#kernel='/boot/vmlinuz-4.19.0-5-amd64'
#ramdisk='/boot/initrd.img-4.19.0-5-amd64'
device_model_version='qemu-xen'
#device_model_override='/usr/lib/xen-4.11/bin/qemu-system-x86_64'
vif=['ip=XXX:XXX:XXX:XXX','mac=XX:XX:XX:XX:XX:XX','bridge=xenbr0']
vnc='1'
vnclisten='192.168.0.11'
vncdisplay='0'

The results were:


libxl: debug: libxl_create.c:1671:do_domain_create: Domain 0:ao 0x55e3a0852c30: create: how=(nil) callback=(nil) poller=0x55e3a0852cc0
libxl: debug: libxl_device.c:397:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=qdisk
libxl: debug: libxl_device.c:397:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:432:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy
libxl: debug: libxl_create.c:1007:initiate_domain_create: Domain 12:running bootloader
libxl: debug: libxl_bootloader.c:328:libxl__bootloader_run: Domain 12:not a PV/PVH domain, skipping bootloader
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a08538f0: deregister unregistered
domainbuilder: detail: xc_dom_allocate: cmdline="", features=""
domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen-4.11/boot/hvmloader"
domainbuilder: detail: xc_dom_malloc_filemap    : 174 kB
libxl: debug: libxl_dom.c:973:libxl__load_hvm_firmware_module: Loading BIOS: /usr/share/seabios/bios-256k.bin
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.11, 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 multiboot-binary loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying HVM-generic loader ...
domainbuilder: detail: loader probe OK
xc: detail: ELF: phdr: paddr=0x100000 memsz=0x35284
xc: detail: ELF: memory: 0x100000 -> 0x135284
domainbuilder: detail: xc_dom_mem_init: mem 4088 MB, pages 0xff800 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0xff800 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: range: start=0x0 end=0xf0000000
domainbuilder: detail: range: start=0x100000000 end=0x10f800000
domainbuilder: detail: xc_dom_malloc            : 8688 kB
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail:   4KB PAGES: 0x0000000000000200
xc: detail:   2MB PAGES: 0x00000000000003fb
xc: detail:   1GB PAGES: 0x0000000000000002
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x100+0x36 at 0x7feff353c000
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x100000 -> 0x136000  (pfn 0x100 + 0x36 pages)
xc: detail: ELF: phdr 0 at 0x7feff3506000 -> 0x7feff3531800
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x136+0x40 at 0x7feff34fc000
domainbuilder: detail: xc_dom_alloc_segment:   System Firmware module : 0x136000 -> 0x176000  (pfn 0x136 + 0x40 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x176+0x1 at 0x7feff443e000
domainbuilder: detail: xc_dom_alloc_segment:   HVM start info : 0x176000 -> 0x177000  (pfn 0x176 + 0x1 pages)
domainbuilder: detail: alloc_pgtables_hvm: doing nothing
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x177000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x0
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64
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 <= matches
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: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 8693 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 174 kB
domainbuilder: detail:       domU mmap          : 476 kB
domainbuilder: detail: vcpu_hvm: called
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x10f800
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x10f801
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:397:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=qdisk
libxl: debug: libxl_linux.c:226:libxl__get_hotplug_script_info: Domain 12:backend_kind 3, no need to execute scripts
libxl: debug: libxl_device.c:1203:device_hotplug: Domain 12:No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a0855da0: deregister unregistered
libxl: debug: libxl_device.c:397:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=phy
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x55e3a08585a0 wpath=/local/domain/0/backend/vbd/12/768/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1708:do_domain_create: Domain 0:ao 0x55e3a0852c30: inprogress: poller=0x55e3a0852cc0, flags=i
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x55e3a08585a0 wpath=/local/domain/0/backend/vbd/12/768/state token=3/0: event epath=/local/domain/0/backend/vbd/12/768/state
libxl: debug: libxl_event.c:878:devstate_callback: backend /local/domain/0/backend/vbd/12/768/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x55e3a08585a0 wpath=/local/domain/0/backend/vbd/12/768/state token=3/0: event epath=/local/domain/0/backend/vbd/12/768/state
libxl: debug: libxl_event.c:874:devstate_callback: backend /local/domain/0/backend/vbd/12/768/state wanted state 2 ok
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x55e3a08585a0 wpath=/local/domain/0/backend/vbd/12/768/state token=3/0: deregister slotnum=3
libxl: debug: libxl_device.c:1117:device_backend_callback: Domain 12:calling device_backend_cleanup
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a08585a0: deregister unregistered
libxl: debug: libxl_linux.c:185:libxl__hotplug_disk: Domain 12:Args and environment ready
libxl: debug: libxl_device.c:1218:device_hotplug: Domain 12:calling hotplug script: /etc/xen/scripts/block add
libxl: debug: libxl_device.c:1219:device_hotplug: Domain 12:extra args:
libxl: debug: libxl_device.c:1227:device_hotplug: Domain 12:env:
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: script: /etc/xen/scripts/block
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_PATH: backend/vbd/12/768
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_BASE_PATH: backend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block add
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a08586a0: deregister unregistered
libxl: debug: libxl_linux.c:203:libxl__get_hotplug_script_info: Domain 12:num_exec 1, not running hotplug scripts
libxl: debug: libxl_device.c:1203:device_hotplug: Domain 12:No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a08586a0: deregister unregistered
libxl: debug: libxl_disk.c:918:libxl__device_disk_find_local_path: Directly accessing local RAW disk /media/STORAGE01/ISO/vm-linux-kde-2019.2-amd64.iso
libxl: debug: libxl_disk.c:918:libxl__device_disk_find_local_path: Directly accessing local RAW disk /dev/vm01/vm
libxl: debug: libxl_dm.c:1656:libxl__build_device_model_args_new: Domain 12:dm_restrict disabled, starting QEMU as root
libxl: debug: libxl_dm.c:2331:libxl__spawn_local_dm: Domain 12:Spawning device-model /usr/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  /usr/bin/qemu-system-i386
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -xen-domid
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  12
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -chardev
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-12,server09,nowait
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -no-shutdown
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -mon
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -chardev
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-12,server09,nowait
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -mon
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  chardev=libxenstat-cmd,mode=control
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -nodefaults
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -no-user-config
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -name
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  vm
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -vnc
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  192.168.0.11:0,to=99
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -display
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  none
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -serial
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  pty
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -device
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  cirrus-vga,vgamem_mb=8
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -boot
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  order=dc
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -smp
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  4,maxcpus=4
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -device
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  rtl8139,id=nic0,netdev=net0,mac=00:16:3e:36:9b:70
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -netdev
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  type=tap,id=net0,ifname=vif12.0-emu,script=no,downscript=no
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -device
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  rtl8139,id=nic1,netdev=net1,mac=00:16:3e:03:f4:fc
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -netdev
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  type=tap,id=net1,ifname=vif12.1-emu,script=no,downscript=no
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -device
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  rtl8139,id=nic2,netdev=net2,mac=00:16:3e:10:91:5f
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -netdev
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  type=tap,id=net2,ifname=vif12.2-emu,script=no,downscript=no
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -machine
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  xenfv
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -m
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  4088
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -drive
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  if=ide,index=1,readonly=on,media=cdrom,id=ide-832,file=/media/STORAGE01/ISO/vm-linux-kde-2019.2-amd64.iso,format=raw
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  -drive
libxl: debug: libxl_dm.c:2333:libxl__spawn_local_dm: Domain 12:  file=/dev/vm01/vm,if=ide,index=0,media=disk,format=raw,cache=writeback
libxl: debug: libxl_dm.c:2335:libxl__spawn_local_dm: Domain 12:Spawning device-model /usr/bin/qemu-system-i386 with additional environment:
libxl: debug: libxl_dm.c:2337:libxl__spawn_local_dm: Domain 12:  XEN_QEMU_CONSOLE_LIMIT=1048576
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x55e3a0853be8 wpath=/local/domain/0/device-model/12/state token=3/1: register slotnum=3
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x55e3a0853be8 wpath=/local/domain/0/device-model/12/state token=3/1: event epath=/local/domain/0/device-model/12/state
libxl: debug: libxl_exec.c:398:spawn_watch_event: domain 12 device model: spawn watch p=(null)
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x55e3a0853be8 wpath=/local/domain/0/device-model/12/state token=3/1: deregister slotnum=3
libxl: error: libxl_dm.c:2427:device_model_spawn_outcome: Domain 12:domain 12 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1563:domcreate_devmodel_started: Domain 12:device model did not start: -3
libxl: error: libxl_dm.c:2541:kill_device_model: Device Model already exited
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x55e3a085be10 wpath=/local/domain/0/backend/vbd/12/768/state token=3/2: register slotnum=3
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x55e3a085be10 wpath=/local/domain/0/backend/vbd/12/768/state token=3/2: event epath=/local/domain/0/backend/vbd/12/768/state
libxl: debug: libxl_event.c:874:devstate_callback: backend /local/domain/0/backend/vbd/12/768/state wanted state 6 ok
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x55e3a085be10 wpath=/local/domain/0/backend/vbd/12/768/state token=3/2: deregister slotnum=3
libxl: debug: libxl_device.c:1117:device_backend_callback: Domain 12:calling device_backend_cleanup
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a085be10: deregister unregistered
libxl: debug: libxl_linux.c:185:libxl__hotplug_disk: Domain 12:Args and environment ready
libxl: debug: libxl_device.c:1218:device_hotplug: Domain 12:calling hotplug script: /etc/xen/scripts/block remove
libxl: debug: libxl_device.c:1219:device_hotplug: Domain 12:extra args:
libxl: debug: libxl_device.c:1227:device_hotplug: Domain 12:env:
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: script: /etc/xen/scripts/block
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_PATH: backend/vbd/12/768
libxl: debug: libxl_device.c:1234:device_hotplug: Domain 12: XENBUS_BASE_PATH: backend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block remove
libxl: debug: libxl_event.c:542:watchfd_callback: watch epath=/local/domain/0/backend/vbd/12/768/state token=3/2: empty slot
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a085bf10: deregister unregistered
libxl: debug: libxl_linux.c:203:libxl__get_hotplug_script_info: Domain 12:num_exec 1, not running hotplug scripts
libxl: debug: libxl_device.c:1203:device_hotplug: Domain 12:No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a085bf10: deregister unregistered
libxl: debug: libxl_linux.c:226:libxl__get_hotplug_script_info: Domain 12:backend_kind 3, no need to execute scripts
libxl: debug: libxl_device.c:1203:device_hotplug: Domain 12:No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a0854df0: deregister unregistered
libxl: debug: libxl_linux.c:226:libxl__get_hotplug_script_info: Domain 12:backend_kind 6, no need to execute scripts
libxl: debug: libxl_device.c:1203:device_hotplug: Domain 12:No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x55e3a0858e70: deregister unregistered
libxl: debug: libxl_domain.c:1172:devices_destroy_cb: Domain 12:Forked pid 19124 for destroy of domain
libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x55e3a0852c30: complete, rc=-3
libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x55e3a0852c30: destroy
libxl: debug: libxl_domain.c:902:libxl_domain_destroy: Domain 12:ao 0x55e3a085a550: create: how=(nil) callback=(nil) poller=0x55e3a0852cc0
libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 12:Non-existant domain
libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 12:Unable to destroy guest
libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 12:Destruction of domain failed
libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x55e3a085a550: complete, rc=-21
libxl: debug: libxl_domain.c:911:libxl_domain_destroy: Domain 12:ao 0x55e3a085a550: inprogress: poller=0x55e3a0852cc0, flags=ic
libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x55e3a085a550: destroy
xencall:buffer: debug: total allocations:690 total releases:690
xencall:buffer: debug: current allocations:0 maximum allocations:3
xencall:buffer: debug: cache current size:3
xencall:buffer: debug: cache hits:672 misses:3 toobig:15
xencall:buffer: debug: total allocations:0 total releases:0
xencall:buffer: debug: current allocations:0 maximum allocations:0
xencall:buffer: debug: cache current size:0
xencall:buffer: debug: cache hits:0 misses:0 toobig:0
root@server09:/home/server09/Documentos#









after running dmesg,  some things called my attention:

dmesg file in here: https://pastebin.com/Fd0wuAFe


    [    0.000000] Hypervisor detected: Xen PV

and that led me to try an pv configurations that had the same results.

    [    1.061597] VPMU disabled by hypervisor.

    [    1.882758] efi: EFI_MEMMAP is not enabled.

     1.889655] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.889759] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.889837] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.889902] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.889961] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890023] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890081] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890141] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890202] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890279] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890357] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890442] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890537] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890619] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890707] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
    [    1.890788] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)





    [   63.698079] parport_pc parport_pc.956: Unable to set coherent dma mask: disabling DMA
    [   63.698251] parport_pc parport_pc.888: Unable to set coherent dma mask: disabling DMA
    [   63.698419] parport_pc parport_pc.632: Unable to set coherent dma mask: disabling DMA
    [   63.945433] tpm_crb MSFT0101:00: can't request region for resource [mem 0xdc28e000-0xdc28efff]





    [   66.049928] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
    [   69.117024] ccp 0000:08:00.2: sev command 0x4 timed out, disabling PSP
    [   69.118484] ccp 0000:08:00.2: SEV: failed to get status. Error: 0x0
    [   69.203512] r8169 0000:06:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw
    [   69.203741] Generic PHY r8169-600:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
    [   69.335118] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
    [   69.388777] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
    [   69.393369] xenbr0: port 1(enp6s0) entered blocking state
    [   69.393371] xenbr0: port 1(enp6s0) entered disabled state
    [   69.393465] device enp6s0 entered promiscuous mode
    [   69.398664] IPv6: ADDRCONF(NETDEV_UP): xenbr0: link is not ready
    [   71.443399] r8169 0000:06:00.0 enp6s0: Link is Up - 100Mbps/Full - flow control rx/tx
    [   71.443407] xenbr0: port 1(enp6s0) entered blocking state
    [   71.443408] xenbr0: port 1(enp6s0) entered forwarding state
    [   71.443470] IPv6: ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready
    [   78.268239] tun: Universal TUN/TAP device driver, 1.6
    [   78.395395] virbr0: port 1(virbr0-nic) entered blocking state
    [   78.395396] virbr0: port 1(virbr0-nic) entered disabled state
    [   78.395437] device virbr0-nic entered promiscuous mode
    [   78.745620] virbr0: port 1(virbr0-nic) entered blocking state
    [   78.745621] virbr0: port 1(virbr0-nic) entered listening state
    [   78.817034] virbr0: port 1(virbr0-nic) entered disabled state


According to another line of thought, there may de some installations issues because I've tried to run some commands with other weird results:




    root@server09:/home/vm01# sudo /etc/init.d/xencommons start    
    sudo: /etc/init.d/xencommons: comando não encontrado
   
    sudo: /etc/init.d/xencommons: comando não encontrado
    root@server09:/home/vm01# sudo /etc/init.d/xendomains start    
    [ ok ] Starting xendomains (via systemctl): xendomains.service.
   
    root@server09:/home/vm01# sudo /etc/init.d/xen-watchdog start    
    sudo: /etc/init.d/xen-watchdog: comando não encontrado
   
    root@server09:/home/vm01# sudo /etc/init.d/xendriverdomain start
    sudo: /etc/init.d/xendriverdomain: comando não encontrado


Those commands were considered because I've noticed that the first time I've tried to start an VM an different issued apperared:

    libxl error libxl_xshelp.c:201:libxl__xs_read_mandatory: xenstore read failed: `/libxl/1/type': No such file or directory



 




Em sex, 13 de set de 2019 às 06:57, Kun Cheng <chengkunck@xxxxxxxxx> escreveu:


Joao Henrique da Silva < 000jhs@xxxxxxxxx> 于2019年9月11日周三 下午10:24写道:
No, it's not. Thanks for the attention.

I've tried to comment the following lines:

#bootloader='pygrub'
#device_model_override='/usr/lib/xen-4.11/bin/qemu-system-x86_64'
 
Just to reduce the noise. 
Maybe you can also comment 'kernel' and 'ramdisk' lines as they are for direct kernel boot, which may conflict with the kernel in your iso file. 

And the configuration file still led me to the same error. I cannot confirm the pv issue you asked but your affirmations both seem right. I think it has something to do with the NetworkManager (vif21.0-emu) part.

One dumb question: you do have xenbr0 configured correctly (seems that you are using libvirt to manage the bridge), and you have no problems creating a pv domain with that bridge, right?

Then, can you try: xl -vvv create -c YOU_HVM_CONFIG_FILE
And check anything suspicious?
 

Em qua, 11 de set de 2019 às 06:19, Kun Cheng < chengkunck@xxxxxxxxx> escreveu:
Hello

Joao Henrique da Silva < 000jhs@xxxxxxxxx> 于2019年9月11日周三 上午11:55写道:
i'm having this problem to start any xen HMV on my debian server:


    root@server /h/l/Documentos# xl create vm.cfg
    Parsing config from vm.cfg
    libxl: error: libxl_dm.c:2427:device_model_spawn_outcome: Domain 20:domain 20 device model: spawn failed (rc=-3)
    libxl: error: libxl_create.c:1563:domcreate_devmodel_started: Domain 20:device model did not start: -3
    libxl: error: libxl_dm.c:2541:kill_device_model: Device Model already exited
    libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 20:Non-existant domain
    libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 20:Unable to destroy guest
    libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 20:Destruction of domain failed


In the logs appear:



    01/09/2019 21:15 server09 /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/20/768
    01/09/2019 21:15 server09 /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/21/768
    01/09/2019 21:15 server09 /etc/xen/scripts/block: Writing backend/vbd/21/768/physical-device fe:9 to xenstore.
    01/09/2019 21:15 server09 /etc/xen/scripts/block: Writing backend/vbd/21/768/physical-device-path /dev/dm-9 to xenstore.
    01/09/2019 21:15 server09 /etc/xen/scripts/block: Writing backend/vbd/21/768/hotplug-status connected to xenstore.
    01/09/2019 21:15 systemd-udevd Using default interface naming scheme 'v240'.
    01/09/2019 21:15 NetworkManager <info>  [1567383358.5189] manager: (vif21.0-emu): new Tun device (/org/freedesktop/NetworkManager/Devices/50)
    01/09/2019 21:15 systemd-udevd link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    01/09/2019 21:15 systemd-udevd Could not generate persistent MAC address for vif21.0-emu: No such file or directory
    01/09/2019 21:15 server09 /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/21/768

My system is a:

    root@server:/home/server09# uname -a
    Linux server 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux



    root@server:/home/server09# apt policy qemu
    qemu:
      Instalado: 1:3.1+dfsg-8~deb10u1
      Candidato: 1:3.1+dfsg-8~deb10u1
      Tabela de versão:
     *** 1:3.1+dfsg-8~deb10u1 500
            500 http://deb.debian.org/debian stable/main amd64 Packages
            100 /var/lib/dpkg/status
         1:2.8+dfsg-6+deb9u8 500
            500 http://security.debian.org stretch/updates/main amd64 Packages
            500 http://deb.debian.org/debian-security oldstable/updates/main amd64 Packages
            500 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
         1:2.8+dfsg-6+deb9u5 500
            500 http://ftp.br.debian.org/debian stretch/main amd64 Packages
            500 http://deb.debian.org/debian oldstable/main amd64 Packages
            500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
   
   
   
    root@server:/home/server09# apt policy libxenmisc4.11 xen-hypervisor-4.11-amd64 xen-utils-4.11
    libxenmisc4.11:
      Instalado: 4.11.1+92-g6c33308a8d-2
      Candidato: 4.11.1+92-g6c33308a8d-2
      Tabela de versão:
     *** 4.11.1+92-g6c33308a8d-2 500
            500 http://deb.debian.org/debian stable/main amd64 Packages
            100 /var/lib/dpkg/status
    xen-hypervisor-4.11-amd64:
      Instalado: 4.11.1+92-g6c33308a8d-2
      Candidato: 4.11.1+92-g6c33308a8d-2
      Tabela de versão:
     *** 4.11.1+92-g6c33308a8d-2 500
            500 http://deb.debian.org/debian stable/main amd64 Packages
            100 /var/lib/dpkg/status
    xen-utils-4.11:
      Instalado: 4.11.1+92-g6c33308a8d-2
      Candidato: 4.11.1+92-g6c33308a8d-2
      Tabela de versão:
     *** 4.11.1+92-g6c33308a8d-2 500
            500 http://deb.debian.org/debian stable/main amd64 Packages
            100 /var/lib/dpkg/status

My Xen configuration file points to:



    name='vm'
    type='hvm'
    vcpus='4'
    memory='4096'
    disk=['file:/media/STORAGE01/ISO/vm-linux-kde-2019.2-amd64.iso,hdb,cdrom,ro' , '/dev/vm01/vm,raw,hda,rw']
    boot='dc'
    _on_poweroff_='destroy'
    _on_reboot_='restart'
    bios='seabios'
    bootloader='pygrub'

I remember pygrub is for pv domains only. Can you confirm hvm domus can use that as bootloader? 

    serial='pty'
    kernel='/boot/vmlinuz-4.19.0-5-amd64'
    ramdisk='/boot/initrd.img-4.19.0-5-amd64'
    device_model_version='qemu-xen'
    device_model_override='/usr/lib/xen-4.11/bin/qemu-system-x86_64'

'device_model_override' requires xen to be built with qemu-system support. Can you confirm your installed packages have that support?
 
    vif=['ip=XXX.XXX.XXX.XXX','mac=XX:XX:XX:XX:XX:XX','bridge=xenbr0']
    vnc='1'
    vnclisten='XXX.XXX.XXX.XXX'
    vncdisplay='0'


I've found several threads suggesting a diversity of approaches, none of them worked.






Update: It also appers to be releated with these logs too:



    11/09/2019 00:40 server lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/physical-device fe:9 to xenstore.
    11/09/2019 00:40 server lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/physical-device-path /dev/dm-9 to xenstore.
    11/09/2019 00:40 server lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/hotplug-status connected to xenstore.
    11/09/2019 00:40 server lucifer /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/24/768
   
   
    11/09/2019 00:40 lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/physical-device fe:9 to xenstore.
    11/09/2019 00:40 lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/physical-device-path /dev/dm-9 to xenstore.
    11/09/2019 00:40 lucifer /etc/xen/scripts/block: Writing backend/vbd/24/768/hotplug-status connected to xenstore.
    11/09/2019 00:40 lucifer /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/24/768

And this very suspicious:


    10/09/2019 22:45 xen en_evtchn: Event-channel device installed
    10/09/2019 22:45 xenbr0 port 1(enp6s0) entered blocking state
    10/09/2019 22:45 xenbr0 port 1(enp6s0) entered disabled state
    10/09/2019 22:45 IPv6 ADDRCONF(NETDEV_UP): xenbr0: link is not ready
    10/09/2019 22:45 xenbr0 port 1(enp6s0) entered blocking state
    10/09/2019 22:45 xenbr0 port 1(enp6s0) entered forwarding state
    10/09/2019 22:45 IPv6 ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready



That led me to check


    root@server:/#  systemctl status -l libvirtd
    ● libvirtd.service - Virtualization daemon
       Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
       Active: active (running) since Tue 2019-09-10 22:45:18 -03; 2h 3min ago
         Docs: man:libvirtd(8)
                https://libvirt.org
     Main PID: 1335 (libvirtd)
        Tasks: 18 (limit: 32768)
       Memory: 10.7M
       CGroup: /system.slice/libvirtd.service
               └─1335 /usr/sbin/libvirtd
   
    set 11 00:12:34 server libvirtd[1335]: Failed to open file '/sys/class/net/vif12.2-emu/operstate': Arquivo
    set 11 00:12:34 server libvirtd[1335]: unable to read: /sys/class/net/vif12.2-emu/operstate: Arquivo ou di
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    set 11 00:13:56 server libvirtd[1335]: ethtool ioctl error: Dispositivo inexistente
    lines 1-21/21 (END)


And hat makes me think that there is something wrong with the NIC device or its module; the bridge seems ok:



    root@server:/# brctl show
    bridge name bridge id STP enabled interfaces
    xenbr0 8000.e0d55ef46d39 no enp6s0

any ideas?





_______________________________________________
Xen-users mailing list
Regards,
Kun

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users

 


Rackspace

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