public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Bruce Cran <bruce@cran.org.uk>
To: "edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@ml01.01.org>
Subject: OVMF: cross-filesystem copy broken? ("The source and destination are the same")
Date: Wed, 16 Nov 2016 20:11:02 -0700	[thread overview]
Message-ID: <47cd17d8-f022-6ca5-2f52-06a8250f8d14@cran.org.uk> (raw)

I don't know if this is a known issue, but it appears that 
cross-filesystem copies no longer work. I'm running OVMF X64 built from 
git commit a0426207c133bdf40c42561f26c20c4b3114d8f9.  I've tried copying 
between filesystems in various ways - with the current directory being 
fs0, fs1, specifying the destination as the current directory, a empty 
directory or a filename. It always results in the same error:

FS0:\efi\ubuntu\> cp grubx64.efi fs1:\

cp: The source and destination are the same.


I built OVMF with: `./OvmfPkg/build.sh -a X64 -t GCC49 -b NOOPT -D 
DEBUG_ON_SERIAL_PORT=TRUE` and am running OVMF with:


qemu-system-x86_64 -name uefi -M q35 -m size=16G -cpu host -enable-kvm \
   -drive 
if=pflash,format=raw,file=workspace/edk2/Build/OvmfX64/NOOPT_GCC49/FV/OVMF.fd 
-serial pty \
   -nodefaults -s -rtc base=utc -monitor stdio --usbdevice tablet \
   -vga qxl  -sdl                                       \
   -device vfio-pci,host=01:00.0,id=iodrive,rombar=0 \
   -drive file=uefi.img,if=ide,media=disk,id=disk,format=raw \
   -drive file=uefi_tmp.img,if=ide,media=disk,id=disk1,format=raw


-- 
Bruce



             reply	other threads:[~2016-11-17  3:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  3:11 Bruce Cran [this message]
2016-11-17  9:35 ` OVMF: cross-filesystem copy broken? ("The source and destination are the same") Laszlo Ersek
2016-11-17 15:24   ` Bruce Cran
2016-11-17 16:06     ` Laszlo Ersek
2016-12-14 22:08       ` Palmer, Thomas
2016-12-15  4:36         ` Gao, Liming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47cd17d8-f022-6ca5-2f52-06a8250f8d14@cran.org.uk \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox