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

pvshim for 32-bit PV guests - what am I doing wrong?


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Mon, 10 May 2021 12:54:34 +0000
  • Delivery-date: Mon, 10 May 2021 12:55:29 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

Hi,

Let's say I have a 32-bit PV guest being booted with pvgrub2 like
so:

name   = "tracker0"
memory = 1024
vcpus  = 2
cpus   = "all,^0,^1"
vif    = [ "mac=00:16:5e:00:01:f5, ip=192.168.80.250, vifname=v-tracker0" ]
type   = "pv"
kernel = "/opt/grub/lib/grub-i386-xen.bin"
disk   = [ "phy:/dev/xenvg/domu_tracker0_xvda,xvda,w" ]

So if I want to run it under pvshim, I should change the config to this, right?

name   = "tracker0"
memory = 1024
vcpus  = 2
cpus   = "all,^0,^1"
vif    = [ "mac=00:16:5e:00:01:f5, ip=192.168.80.250, vifname=v-tracker0" ]
type   = "pvh"
pvshim = 1
kernel = "/opt/grub/lib/grub-i386-xen.bin"
disk   = [ "phy:/dev/xenvg/domu_tracker0_xvda,xvda,w" ]

But when I try to create that guest, I just get this:

$ sudo xl -v create -c /etc/xen/tracker0.conf
Parsing config from /etc/xen/tracker0.conf
domainbuilder: detail: xc_dom_allocate: cmdline="pv-shim console=xen,pv", 
features=""
domainbuilder: detail: xc_dom_kernel_file: 
filename="/usr/lib/xen-4.12/boot/xen-shim"
domainbuilder: detail: xc_dom_malloc_filemap    : 1549 kB
domainbuilder: detail: xc_dom_module_file: 
filename="/opt/grub/lib/grub-i386-xen.bin"
domainbuilder: detail: xc_dom_malloc_filemap    : 1401 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.12, 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=0x200000 memsz=0x183460
xc: detail: ELF: memory: 0x200000 -> 0x383460
domainbuilder: detail: xc_dom_mem_init: mem 1024 MB, pages 0x40000 pages, 4k 
each
domainbuilder: detail: xc_dom_mem_init: 0x40000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: range: start=0x0 end=0x40000400
domainbuilder: detail: xc_dom_malloc            : 2048 kB
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail:   4KB PAGES: 0x0000000000000000
xc: detail:   2MB PAGES: 0x0000000000000000
xc: detail:   1GB PAGES: 0x0000000000000001
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x200+0x184 at 0x7f375d2f3000
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x200000 -> 
0x384000  (pfn 0x200 + 0x184 pages)
xc: detail: ELF: phdr 0 at 0x7f375d16f000 -> 0x7f375d2f2460
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x384+0x15f at 0x7f375d194000
domainbuilder: detail: xc_dom_alloc_segment:   module0      : 0x384000 -> 
0x4e3000  (pfn 0x384 + 0x15f pages)
domainbuilder: detail: xc_dom_load_acpi: 64 bytes at address fc008000
domainbuilder: detail: xc_dom_load_acpi: 4096 bytes at address fc000000
domainbuilder: detail: xc_dom_load_acpi: 28672 bytes at address fc001000
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x4e3+0x1 
at 0x7f375e605000
domainbuilder: detail: xc_dom_alloc_segment:   HVM start info : 0x4e3000 -> 
0x4e4000 (pfn 0x4e3 + 0x1 pages)
domainbuilder: detail: alloc_pgtables_hvm: doing nothing
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x4e4000
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             : 2068 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 2950 kB
domainbuilder: detail:       domU mmap          : 2960 kB
domainbuilder: detail: Adding module 0 guest_addr 384000 len 1437696
domainbuilder: detail: vcpu_hvm: called
domainbuilder: detail: xc_dom_set_gnttab_entry: d5 gnt[0] -> d0 0xfefff
domainbuilder: detail: xc_dom_set_gnttab_entry: d5 gnt[1] -> d0 0xfeffc
domainbuilder: detail: xc_dom_release: called
$ 

What am I doing wrong?

This is Xen 4.12.4.

Thanks,
Andy



 


Rackspace

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