Ian Jackson wrote:
Andrew Lyon writes ("Re: [Xen-devel] HVM guest question (was Re: [PATCH] ioemu:
Cleanup the code of PCI passthrough.)"):
On Mon, Feb 23, 2009 at 2:53 PM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
These messages are not very surprising. Is it working ?
No, when try to start HVM on Xen unstable with pv_ops kernel I get this error:
Ah. This is rather odd. Normally I would hope that xend would report
an exit status. (I haven't tried pvops with qemu.)
Hm, I'm getting:
[2009-02-23 15:26:18 4380] WARNING (image:482) domain win7: device model
failure: pid 5409: died due to signal 7; see /var/log/xen/qemu-dm-win7.log
Hm, signal 7 - SIGBUS. I wonder if
Using stub domains doesn't work either.
I would suggest running qemu-dm under strace. This can be done easily
enough with a simple wrapper script, something like:
#!/bin/sh
set -e
exec strace -vvs500 -f -o /root/qemu-dm.strace \
/usr/lib/xen/bin/qemu-dm "$@"
and then give the name of the script as device_model in your config file.
I see:
...
5079 ioctl(10, EVIOCGKEYCODE, 0x7fffdfd52b70) = 0
5079 clock_gettime(CLOCK_MONOTONIC, {1324, 539747423}) = 0
5079 clock_gettime(CLOCK_MONOTONIC, {1324, 539837298}) = 0
5079 select(14, [3 6 10 11 13], [], [], {0, 10000}) = 1 (in [10], left {0,
9995})
5079 read(10, "\36\0\0\0"..., 4) = 4
5079 write(10, "\36\0\0\0"..., 4) = 4
5079 ioctl(10, EVIOCGKEYCODE, 0x7fffdfd52b70) = 0
5079 clock_gettime(CLOCK_MONOTONIC, {1324, 540495964}) = 0
5079 clock_gettime(CLOCK_MONOTONIC, {1324, 540591278}) = 0
5079 select(14, [3 6 10 11 13], [], [], {0, 10000}) = 1 (in [10], left {0,
9995})
5079 read(10, "\36\0\0\0"..., 4) = 4
5079 write(10, "\36\0\0\0"..., 4) = 4
5079 mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) =
0x7f1ad5f2b000
5079 ioctl(4, SNDCTL_DSP_STEREO, 0x7fffdfd52230) = 0
5079 --- SIGBUS (Bus error) @ 0 (0) ---
5157 +++ killed by SIGBUS +++
This mmap and ioctl is from /proc/xen/privcmd.
J
qemu-dm.strace.gz
Description: GNU Zip compressed data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home