On Mon, Feb 23, 2009 at 6:47 PM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> I've tried that :-
> name = "Ubuntu810HVM"
> builder = "hvm"
> memory = "2048"
> disk = ['phy:/dev/loop0,hdc:cdrom,r','phy:/dev/sdb7,hda,w']
> vif = [ 'type=ioemu,bridge=eth0' ]
> # device_model = "/usr/lib64/xen/bin/qemu-dm"
> device_model = "device_model_wrap.sh"
> kernel = "/usr/lib/xen/boot/hvmloader"
> on_reboot = "restart"
> on_crash = "restart"
> cat device_model_wrap.sh
> set -e
> exec strace -vvs500 -f -o ~boris/vm/qemu-dm.strace \
> /usr/lib64/xen/bin/qemu-dm "$@"
> Same behavior. File qemu-dm.strace has not been created at all.
> Content of log file under /var/log/xen is just the same.
> xm dmesg is much less informative. Just 2-3 HVM lines
Worked for me, I've attached the 1mb strace logfile.
Perhaps you don't have strace installed?
> --- On Mon, 2/23/09, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] HVM pvops failures
> To: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
> Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Monday, February 23, 2009, 11:21 AM
> 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
> Ah. This is rather odd. Normally I would hope that xend would report
> an exit status. (I haven't tried pvops with
> I would suggest running qemu-dm under strace. This can be done easily
> enough with a simple wrapper script, something like:
> 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.
> Xen-devel mailing list
Description: Binary data
Xen-devel mailing list