Re: [Xen-users] how to boot something to get a vm started

[hw <hw@xxxxxxxxxxxxxxxxxxxxxxxx>]

Am 13.07.2015 um 17:48 schrieb Ian Campbell:
> On Mon, 2015-07-13 at 17:19 +0200, hw wrote:
> > Hi,
> >
> > how do I boot anything to get a VM started and installed?  I tried a
> > windoze 7 installer ISO and a Gentoo live-DVD ISO and nothing works.  No
> > matter what I try, I keep getting messages that no kernel can be found
> > and that the VM cannot be created.
> Without any logs or even a config file I'm just guessing, but it sounds
> like you are wanting to create an HVM guest but are actually creating a
> PV one.
>
> The main difference is the use of
>          builder = "hvm"
> in your cfg file. xl.cfg(5) has details and xlexample.hvm (normally
> installed to /etc/xen) an example.
Yes, I have that.  The config is:


# This configures an HVM rather than PV guest
builder = "hvm"

device_model_version="qemu-xen"
#device_model_override="/usr/bin/qemu-img-xen"

# Guest name
name = "ws-01"

# 128-bit UUID for the domain as a hexadecimal number.
# Use "uuidgen" to generate one if required.
# The default behavior is to generate a new UUID each time the guest is 
started.
#uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

# Enable Microsoft Hyper-V compatibile paravirtualisation /
# enlightenment interfaces. Turning this on can improve Windows guest
# performance and is therefore recommended
viridian = 1

# Initial memory allocation (MB)
memory = 4096

# Maximum memory (MB)
# If this is greater than `memory' then the slack will start ballooned
# (this assumes guest kernel support for ballooning)
#maxmem = 512

# Number of VCPUS
vcpus = 2

# Network devices
# A list of 'vifspec' entries as described in
# docs/misc/xl-network-configuration.markdown
vif = [ 'bridge=brloc' ]

# Disk Devices
# A list of `diskspec' entries as described in
# docs/misc/xl-disk-configuration.txt
disk = [ 'phy:/dev/sde1,hda,w', 
'file:/root/installers/de_windows_7_professional_with_sp1_x64_dvd_u_676919.iso,hdc:cdrom,r' 
]

boot="dc"

# Guest VGA console configuration, either SDL or VNC
sdl = 0
vnc = 1


And I'm only getting:


Parsing config from /etc/xen/ws-01.hvm
libxl: debug: libxl_create.c:1504:do_domain_create: ao 0x250e350: 
create: how=(nil) callback=(nil) poller=0x250e3b0
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk 
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk 
vdev=hda, using backend phy
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:907: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=0x250ec80: 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=9875
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=10311
libxl: detail: libxl_dom.c:196:numa_place_domain: NUMA placement 
candidate with 1 nodes, 12 cpus and 10311 KB free selected
libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: base group enabled
libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: freq group enabled
libxl: detail: libxl_dom.c:254:hvm_set_viridian_features: time_ref_count 
group enabled
xc: error: Could not open kernel image (2 = No such file or directory): 
Internal error
libxl: error: libxl_dom.c:818:libxl__build_hvm: hvm building failed
libxl: error: libxl_create.c:1121:domcreate_rebuild_done: cannot 
(re-)build domain: -3
libxl: error: libxl_dm.c:1595:kill_device_model: unable to find device 
model pid in /local/domain/35/image/device-model-pid
libxl: error: libxl.c:1608:libxl__destroy_domid: 
libxl__destroy_device_model failed for 35
libxl: info: libxl.c:1691:devices_destroy_cb: forked pid 5250 for 
destroy of domain 35
libxl: debug: libxl_create.c:1520:do_domain_create: ao 0x250e350: 
inprogress: poller=0x250e3b0, flags=i
libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x250e350: 
complete, rc=-3
libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x250e350: destroy
xc: debug: hypercall buffer: total allocations:197 total releases:197
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:182 misses:4 toobig:11


So I thought I'd try to make a PV guest with Gentoo ISO and found that 
nothing can be booted:

Parsing config from /etc/xen/test.pvlinux
libxl: debug: libxl_create.c:1504:do_domain_create: ao 0x2454c30: 
create: how=(nil) callback=(nil) poller=0x2455410
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk 
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:215:disk_try_backend: Disk vdev=xvda, 
backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk 
vdev=xvda, using backend qdisk
libxl: debug: libxl_create.c:907:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:329:libxl__bootloader_run: no 
bootloader configured, using user supplied kernel
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
w=0x2455ca0: 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=36, 
free_memkb=9875
libxl: debug: libxl_numa.c:483:libxl__get_numa_candidate: New best NUMA 
placement candidate found: nr_nodes=1, nr_cpus=12, nr_vcpus=36, 
free_memkb=10312
libxl: detail: libxl_dom.c:196:numa_place_domain: NUMA placement 
candidate with 1 nodes, 12 cpus and 10312 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/ram0 
init=/linuxrc aufs looptype=squashfs loop=/image.squashfs cdroot", 
features="(null)"
libxl: debug: libxl_dom.c:533:libxl__build_pv: pv kernel mapped 0 path 
/isolinux/gentoo
domainbuilder: detail: xc_dom_kernel_file: filename="/isolinux/gentoo"
xc: error: panic: xc_dom_core.c:208: failed to open file: No such file 
or directory: Internal error
domainbuilder: detail: xc_dom_malloc_filemap: failed (on file 
`/isolinux/gentoo')
libxl: error: libxl_dom.c:546:libxl__build_pv: xc_dom_kernel_file 
failed: No such file or directory
domainbuilder: detail: xc_dom_release: called
libxl: error: libxl_create.c:1121:domcreate_rebuild_done: cannot 
(re-)build domain: -3
libxl: info: libxl.c:1691:devices_destroy_cb: forked pid 5252 for 
destroy of domain 36
libxl: debug: libxl_create.c:1520:do_domain_create: ao 0x2454c30: 
inprogress: poller=0x2455410, flags=i
libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x2454c30: 
complete, rc=-3
libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x2454c30: destroy
xc: debug: hypercall buffer: total allocations:252 total releases:252
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:237 misses:4 toobig:11


'/isolinux/gentoo' is listed in the grub.cfg contained in the ISO, and 
it does exist.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users