Re: [Qemu-devel] 3 new x86 instructions

[Torbjorn Granlund]

Richard Henderson <address@hidden> writes:

  On 2013-02-19 13:52, Torbjorn Granlund wrote:
  > Execute.  I believe correct behaviour is to print:
  >
  >      000000000000000d 000000000000000d 040000000000000b 000000000000000a
  >
  > The program under your special qemu instead prints:
  >
  >      000000000000000e 000000000000000d 040000000000000b 000000000000000a
  >
  > Perhaps I am being silly and the program is behaving correctly.
  
  Nope, you found a typo in the comparison.  Annoyingly, not in the i686
  version, which is what I'd tested by hand before.
  
  I've pushed an update to my x86-next branch, and updated the eflags3
  branch against which I posted patches for review this afternoon.
  
I cloned a fresh repo, and compiled it exactly like yesterday on the
same system (I used bash's history list):

  [srcpath]/configure && make -j8

Now my disk image fails to boot.

"No bootable device.  Retrying in 60 seconds."

My boot command is (and was):

qemu-system-x86_64 -m 512 -cpu Haswell,+adx \
   -net nic,macaddr=52:54:00:f2:81:c7,model=e1000 -net tap \
  -cdrom /u/FreeBSD/FreeBSD-9.1-RELEASE-amd64-dvd1.iso -boot c -hda disk.img

I went back to the old qemu-system-x86_64 and that still works, so I
don't think the disk.img file is corrupt.

I then tried something that you might consider more plain:

qemu-system-x86_64 -m 512 -cpu Haswell,+adx \
 -net nic,macaddr=52:54:00:f2:18:b7,model=e1000 -net tap \
 -cdrom /u/GNU/Debian/debian-6.0.6-amd64-netinst.iso -boot d --hda disk.img

It fails similarly.  (Here disk.img is pristine from a "qemu-img create"
command, but I am attemtping to boot from the iso img.)

-- 
Torbjörn