[Xen-users] Trouble starting HVM domU with Linux 3.0.0 and Xen 4.1.1

[Sergiusz Bazanski <bazanski@xxxxxxxxx>]

Hey,

I've recently tried installing Xen 4.1.1 on my server, which is
running ArchLinux. However, for some reason, when I start a domU with
HVM enabled, I get an immediate crash. Here is my setup:

===================
celestia ~ # uname -a
Linux celestia.q3k.org 3.0.0-rc6-q3k-xen #1 SMP Mon Jul 11 03:52:41
CDT 2011 x86_64 Intel(R) Xeon(R) CPU E5520 @ 2.27GHz GenuineIntel
GNU/Linux
===================

This kernel is based off the 3.0.0 sources, with the VGA patch applied.

===================
celestia ~ # zcat /proc/config.gz | grep XEN
CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_DEBUG is not set
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
# CONFIG_XEN_WDT is not set
CONFIG_XEN_FBDEV_FRONTEND=m
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=m
CONFIG_XEN_GRANT_DEV_ALLOC=m
CONFIG_XEN_PLATFORM_PCI=m
CONFIG_SWIOTLB_XEN=y
===================

Here is the domU I am trying to run:

===================
celestia vmconfs # cat ws2008.cfg
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
memory = '1024'
name = "testing"
vcpus=4
viridian = 1
pae=0
acpi=1
apic=1
disk = [
 Â'file:/home/xen/vms/xenwin2008/hdd.img,hda,w',
 Â'file:/home/xen/vms/xenwin2008/cd.iso,hdc:cdrom,r'
]
boot="dc"
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
device_model = "/usr/lib/xen/bin/qemu-dm"
sdl=0
vnc=1
vncconsole=10
vnclisten="96.127.164.138"
===================

And here are the logs

===================
celestia vmconfs # cat /var/log/xen/qemu-dm-testing.log
domid: 287
Using file /home/xen/vms/xenwin2008/hdd.img in read-write mode
Using file /home/xen/vms/xenwin2008/cd.iso in read-only mode
Watching /local/domain/0/device-model/287/logdirty/cmd
Watching /local/domain/0/device-model/287/command
Watching /local/domain/287/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 6aca0939-d93e-e02e-beb1-81c89c159398
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/287/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/6aca0939-d93e-e02e-beb1-81c89c159398/vncpasswd.
medium change watch on `hdc' (index: 1): /home/xen/vms/xenwin2008/cd.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/287/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/287/log-throttling'
medium change watch on `/local/domain/287/log-throttling' - unknown
device, ignored
char device redirected to /dev/pts/3
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
===================
celestia vmconfs # xm log | tail -n 200
[....]
[2011-07-11 06:25:26 824] DEBUG (DevController:139) Waiting for devices pci.
[2011-07-11 06:25:26 824] DEBUG (DevController:139) Waiting for devices vusb.
[2011-07-11 06:25:26 824] DEBUG (DevController:139) Waiting for devices vtpm.
[2011-07-11 06:25:26 824] INFO (XendDomain:1225) Domain testing (287) unpaused.
[2011-07-11 06:25:26 824] INFO (XendDomainInfo:2078) Domain has
shutdown: name=testing id=287 reason=reboot.
[2011-07-11 06:25:26 824] ERROR (XendDomainInfo:2195) VM testing
restarting too fast (Elapsed time: 0.258410 seconds). Refusing to
restart to avoid loops.
[2011-07-11 06:25:26 824] DEBUG (XendDomainInfo:3071)
XendDomainInfo.destroy: domid=287
[2011-07-11 06:25:26 824] DEBUG (XendDomainInfo:2401) Destroying device model
[....]
===================

And, possibly, most importantly:

===================
celestia vmconfs # xm dmesg
[...]
(XEN) io.c:194:d287 MMIO emulation failed @ 0018:9ffff: 00 b0 1a 80 c4 82
===================

The images specified in the config are accessible, and the ISO image
is bootable.

Could anyone give me any hints on what I might be doing wrong?

Sergiusz BazaÅski
sergiusz@xxxxxxx
http://www.q3k.org/

PS. I've sent this email from another email address a few minutes ago
- it probably got blocked. If it has not, ignore this one.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users