From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: qemu oddness with isolinux vesamenu.c32 Date: Fri, 18 Jul 2008 09:53:06 -0700 Message-ID: <4880CA72.2050809@zytor.com> References: <48800A9D.1080403@zytor.com> <4880C3F3.6010202@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pjones@redhat.com, kvm@vger.kernel.org, Anthony Liguori To: Matt_Domsch@Dell.com Return-path: Received: from terminus.zytor.com ([198.137.202.10]:38544 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752049AbYGRQxt (ORCPT ); Fri, 18 Jul 2008 12:53:49 -0400 In-Reply-To: <4880C3F3.6010202@zytor.com> Sender: kvm-owner@vger.kernel.org List-ID: Just noticed this post was missing the initial information: hpa: your test ISO shows: vesamenu.c32: attempted DOS system call INT 2C 42C4 D00004F0 when run under latest F9 virt-manager started KVM machine hpa, but does _not_ fail as such when run manually with sudo qemu-kvm -M pc -m 512 -hda /var/lib/libvirt/images/hpa.img -cdrom /var/tmp/boot-fc9-3.70-pre26.iso hpa, which means one of these args is probably causing it /usr/bin/qemu-kvm -S -M pc -m 512 -smp 1 -name foo -monitor pty -boot c -drive file=/var/lib/libvirt/images/foo.img,if=ide,index=0,boot=on -drive file=,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:13:75:3a,vlan=0 -net tap,fd=13,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us For what it's worth, it's the "boot=on" part that is causing extboot to be invoked, which is what is causing the failure. I have to admit I don't really understand why extboot hooks INT 13h at all (why emulate a disk on a system where disks are virtual anyway?), but more seriously, it has the problem that: a) it uses vectors in OS reserved space; b) it doesn't clean up after itself after giving up and before invoking the old INT 19h vector. -hpa