All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muelli <ubuntu-bugs@auftrags-killer.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 543478] Re: qemus pmemsave doesn't accept "/" in filename
Date: Wed, 07 Jul 2010 01:29:36 -0000	[thread overview]
Message-ID: <20100707012936.28141.98656.launchpad@palladium.canonical.com> (raw)
In-Reply-To: 20100321151438.9877.81956.malonedeb@palladium.canonical.com

** Branch linked: lp:~ubuntu-bugs-auftrags-killer/qemu/proper-error-
characters

-- 
qemus pmemsave doesn't accept "/" in filename
https://bugs.launchpad.net/bugs/543478
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid
Status in “qemu-kvm” package in Ubuntu: Incomplete

Bug description:
Binary package hint: qemu-kvm

Please see my conversation with qemu:

(qemu) pmemsave 
unexpected end of expression
(qemu) help pmemsave 
pmemsave addr size file -- save to disk physical memory dump starting at 'addr' of size 'size'
(qemu) pmemsave 0 512M /tmp/qemu.mem
pmemsave: extraneous characters at the end of line
(qemu) pmemsave 0 512 /tmp/qemu.mem
invalid char in expression
(qemu) pmemsave 0 512 /tmp/qemu
invalid char in expression
(qemu) pmemsave 0 512 qemu.mem
(qemu) pmemsave 0 512M qemu.mem
pmemsave: extraneous characters at the end of line



Let me comment on each one of those:
(qemu) pmemsave 
unexpected end of expression

I expected some sort of hint as to where to get more information. Maybe just a "Type ``help pmemsave'' to get syntax information" would be sufficient.


(qemu) help pmemsave 
pmemsave addr size file -- save to disk physical memory dump starting at 'addr' of size 'size'

Nice. But an example would be nice. My proposal: "I.e.: pmemsave 0 1G /tmp/qemu.mem"


(qemu) pmemsave 0 512M /tmp/qemu.mem
pmemsave: extraneous characters at the end of line

eh. Would be nice if it told me *which* character was "extraneous" and what "extraneous" means. My proposal: "Couldn't parse character at position 23, please see help pmemsave for an example".


(qemu) pmemsave 0 512 /tmp/qemu.mem
invalid char in expression

Hm. Interesting. Again, would be nice if it printed me the offending character. My proposal: "Could not parse character at position 23, please see help pmemsave for an example".


(qemu) pmemsave 0 512 /tmp/qemu
invalid char in expression

Now I got rid of almost everything but it still doesn't work.


(qemu) pmemsave 0 512 qemu.mem

aha! No slashes?! Seriously?

(qemu) pmemsave 0 512M qemu.mem
pmemsave: extraneous characters at the end of line

And no "M" or "G" modifiers? If I want to dump 2GB then I'd have to calculate the number in bytes and paste that long string. I expected qemu to be able to parse the K, M, G suffixes.

Also, I'm wondering why it doesn't offer to dump all memory.

ProblemType: Bug
Architecture: amd64
CurrentDmesg:
 [150870.676062] kvm_intel: Unknown symbol kvm_vcpu_on_spin
 [150947.222923] cron[24260]: segfault at 0 ip (null) sp 00007fffe865eed8 error 14 in cron[400000+9000]
 [150947.224187] cron[24261]: segfault at 0 ip (null) sp 00007fffe865eed8 error 14 in cron[400000+9000]
Date: Sun Mar 21 15:03:13 2010
DistroRelease: Ubuntu 9.10
KvmCmdLine:
 UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
 muelli   23807 23806 13 239738 228464 0 14:54 pts/8    00:01:22 /usr/bin/kvm -S -M pc -m 512 -smp 1 -name vanilla_ubuntu -monitor stdio -boot c -drive file=/home/muelli/qemu/ubuntu8.10/ubuntu.img,if=ide,index=0,boot=on -drive file=,if=ide,media=cdrom,index=2 -net nic,model=rtl8139,macaddr=f0:00:BA:12:34:56 -net user,hostfwd=tcp::2223-:22,smb=/tmp/share -serial pty -snapshot
MachineType: LENOVO 766636G
Package: kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=/dev/mapper/cryptroot source=UUID=9c3d5596-27c6-4fd5-bfcd-fa8eef6f1230 ro vdso32=0 quiet splash  crashkernel=384M-2G:64M,2G-:128M
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
SourcePackage: qemu-kvm
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 03/12/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETC0WW (2.20 )
dmi.board.name: 766636G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NETC0WW(2.20):bd03/12/2009:svnLENOVO:pn766636G:pvrThinkPadX61:rvnLENOVO:rn766636G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 766636G
dmi.product.version: ThinkPad X61
dmi.sys.vendor: LENOVO

  parent reply	other threads:[~2010-07-07  1:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100321151438.9877.81956.malonedeb@palladium.canonical.com>
2010-06-23 21:35 ` [Qemu-devel] [Bug 543478] Re: qemus pmemsave doesn't accept "/" in filename Serge Hallyn
2010-06-23 21:51 ` Anthony Liguori
2010-06-24  1:10   ` Serge E. Hallyn
2010-06-24  1:09 ` Serge Hallyn
2010-06-24  8:19 ` Muelli
2010-06-24 14:48 ` Serge Hallyn
2010-07-06 15:39 ` Muelli
2010-07-06 16:31 ` Brian Murray
2010-07-07  1:29 ` Muelli [this message]
2010-12-10  4:17 ` Launchpad Bug Tracker
2011-02-12 16:54 ` [Qemu-devel] [Bug 543478] The education it�s prestigious ! Roberto Scotti

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-all 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=20100707012936.28141.98656.launchpad@palladium.canonical.com \
    --to=ubuntu-bugs@auftrags-killer.org \
    --cc=543478@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.