[Bug 1511803] [NEW] /etc/default/docker is read by systemd and contains invalid export statement
Public bug reported: in the journal Okt 30 20:19:26 forlerbox systemd[1]: docker.service: Ignoring invalid environment assignment 'export http_proxy=http://foo:b...@proxy.acme.corp:8080': /etc/default/docker I guess that file should be fixed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: docker.io (not installed) ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 30 18:18:56 2015 SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1511803 Title: /etc/default/docker is read by systemd and contains invalid export statement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1511803/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1493067] [NEW] ssh-copy-id does not work with fish on the other machine
Public bug reported: ssh-copy-id 10.200.17.160 /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys foo@10.200.17.160's password: fish: Expected a command name, got token of type “Run job in background”. Did you mean “COMMAND; and COMMAND”? See the help section for the “and” builtin command by typing “help and”. Standard input: mkdir -p .ssh && cat >> .ssh/authorized_keys || exit 1 ; ^ I expected to be able to copy my key. An approach I see is for ssh-copy-id to run bash -c ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openssh-client 1:6.7p1-5ubuntu1.3 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 7 15:56:44 2015 RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.7p1-5ubuntu1.3 SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1493067 Title: ssh-copy-id does not work with fish on the other machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1493067/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1445386] [NEW] virtual machine cannot access p9 filesystem
Public bug reported: I have configured host filesystem access via virt-manager. filesystem type='mount' accessmode='squash' source dir='/tmp/share1'/ target dir='/hostshare1'/ alias name='fs0'/ address type='pci' domain='0x' bus='0x00' slot='0x09' function='0x0'/ /filesystem filesystem type='mount' accessmode='mapped' source dir='/tmp/share2'/ target dir='hostshare2'/ alias name='fs1'/ address type='pci' domain='0x' bus='0x00' slot='0x0a' function='0x0'/ /filesystem now, in the guest, I can mount /hostshare1 -t 9p -o trans=virtio,version9p2000.L,access=any,posixacl /mnt/ but I cannot list the directory. I get a permission denied error. cat /etc/apparmor.d/libvirt/libvirt-039f126b- da58-4dba-9317-4c7586c34a61.files # DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT. /var/log/libvirt/**/ubuntutrusty-server.log w, /var/lib/libvirt/**/ubuntutrusty-server.monitor rw, /var/run/libvirt/**/ubuntutrusty-server.pid rwk, /run/libvirt/**/ubuntutrusty-server.pid rwk, /var/run/libvirt/**/*.tunnelmigrate.dest.ubuntutrusty-server rw, /run/libvirt/**/*.tunnelmigrate.dest.ubuntutrusty-server rw, /var/lib/libvirt/images/ubuntutrusty-server.qcow2 rw, /tmp/share1/** rwl, /tmp/share1/ r, /tmp/share2/** rwl, /tmp/share2/ r, /dev/vhost-net rw, /dev/net/tun rw, but I needed to sudo aa-complain libvirt/libvirt-039f126b-da58-4dba-9317-4c7586c34a61 in order to be able to list the directory. I cannot read or write files, though. I expected it to work fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libvirt-bin 1.2.12-0ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 17 10:15:24 2015 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1445386 Title: virtual machine cannot access p9 filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1445386/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777318] Re: ubuntu-vm-builder crashed with VMBuilderUserError in main()
Well. I'm still surprised how this can seriously not be considered a crash. Yes it's an error message. Maybe even a good and meaningful one. But it's a crash nonetheless. I'd use logging.exception to print the stack trace along with an error message instead of letting the Python exception handler handle it and make Apport show up. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/777318 Title: ubuntu-vm-builder crashed with VMBuilderUserError in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/777318/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777318] Re: ubuntu-vm-builder crashed with VMBuilderUserError in main()
But it makes apport pop up to report a crash. ** Changed in: vm-builder (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/777318 Title: ubuntu-vm-builder crashed with VMBuilderUserError in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/777318/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777318] Re: ubuntu-vm-builder crashed with VMBuilderUserError in main()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/777318 Title: ubuntu-vm-builder crashed with VMBuilderUserError in main() -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777331] Re: ubuntu-vm-builder crashed with VMBuilderUserError in preflight_check()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/777331 Title: ubuntu-vm-builder crashed with VMBuilderUserError in preflight_check() -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777318] Re: ubuntu-vm-builder crashed with VMBuilderUserError in main()
Calling the program with the wrong arguments shouldn't make it crash. Hence it's a bug. ** Changed in: vm-builder (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/777318 Title: ubuntu-vm-builder crashed with VMBuilderUserError in main() -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] Re: qemus pmemsave doesn't accept / in filename
Here's a patch against qemu from git that prints the offending characters, helping the user to understand what's going on. I can't deal with qemu-devel myself, it's way too noisy. But Ubuntu might want to take that patch or push it upstream. ** Patch added: Patch which prints the errorneous characters http://launchpadlibrarian.net/51467852/0001-Monitor-Print-the-errorneous-character-if-we-detecte.patch -- qemus pmemsave doesn't accept / in filename https://bugs.launchpad.net/bugs/543478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] Re: qemus pmemsave doesn't accept / in filename
** 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 Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] Re: qemus pmemsave doesn't accept / in filename
Eh. Well. I'm a bit surprised that you won't allow forward slashes if you try to parse a path. It's actually a quite common character in the Linux world. Even other Unixes use it for separating components of a path. And since people use it so much, it should be as easy as possible to actually give a path to qemu. The excuse that it is used to create special expressions (which, btw?!) doesn't hold. I'm pretty confident that people use the '/' character to separate components of a path rather than doing special expressions. Especially when a path the a file is expected! So if there are still special expressions needed in a path, it'd be better to select a different character. Even if you don't agree on that, I really believe the user deserves some explanation along with the error message that is printed as I've pointed out in comment #0. ** Changed in: qemu-kvm (Ubuntu) Status: Invalid = New -- qemus pmemsave doesn't accept / in filename https://bugs.launchpad.net/bugs/543478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 590232] Re: qemu-system-x86_64 crashed with SIGSEGV
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49743556/BootDmesg.txt ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/49743557/CoreDump.gz ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49743558/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49743559/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/49743560/Disassembly.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49743561/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49743562/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49743563/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/49743564/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49743565/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/49743566/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49743567/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/49743568/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/49743569/Registers.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/49743570/RelatedPackageVersions.txt ** Attachment added: SegvAnalysis.txt http://launchpadlibrarian.net/49743571/SegvAnalysis.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/49743572/ThreadStacktrace.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49743573/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49743574/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/49743575/XsessionErrors.txt ** Visibility changed to: Public -- qemu-system-x86_64 crashed with SIGSEGV https://bugs.launchpad.net/bugs/590232 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 565659] Re: qemu-img baseimage creation doesn't warn for image being smaller
It's qcow2 and increasing size is not what the problem is. The problem is, if the forked image is smaller than the base image. In that case, qemu-img should not create the image in first place. -- qemu-img baseimage creation doesn't warn for image being smaller https://bugs.launchpad.net/bugs/565659 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 565659] Re: qemu-img baseimage creation doesn't warn for image being smaller
You're right. the descriptive text is wrong. In fact, I was typing the bug report up very quickly. I did not want to change the size of the base image. Basically I just wanted to checkpoint my machine. So in fact, I couldn't bother less about the size and I thought qemu-img made me. But now I've just realised that you don't need to provide a size argument which I thought was mandatory. Although I think it is very a corner case to reduce the image size and qemu should raise a warning if anybody attempts to decrease the image size, this could probably be closed as NOTABUG or so. -- qemu-img baseimage creation doesn't warn for image being smaller https://bugs.launchpad.net/bugs/565659 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 565659] [NEW] qemu-img baseimage creation doesn't warn for image being smaller
Public bug reported: Binary package hint: qemu-kvm $ qemu-img create -b ../base-dont-touch.img new.img 10G should really raise a warning if ../base-dont-touch.img is smaller than 10GB because QEmu apparently does not handle that fact. At least my guest OS didn't boot at all. Creating an Image of the same resulted in a successful boot though. In fact, If QEmu doesn't handle a differnent size, even a bigger one, I don't see why qemu-img create -b ... should take a size argument at all. But then again, I don't know whether QEmu handles images backed by a smaller base image. In any case: The command line tool is very misleading. Right now it reads: $ qemu-img qemu-img version 0.11.0, Copyright (c) 2004-2008 Fabrice Bellard usage: qemu-img command [command options] QEMU disk image utility Command syntax: check [-f fmt] filename create [-F fmt] [-b base_image] [-f fmt] [-o options] filename [size] commit [-f fmt] filename convert [-c] [-f fmt] [-O output_fmt] [-o options] [-B output_base_image] filename [filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a snapshot | -c snapshot | -d snapshot] filename Command parameters: 'filename' is a disk image filename 'base_image' is the read-only disk image which is used as base for a copy on write image; the copy on write image only stores the modified data 'output_base_image' forces the output image to be created as a copy on write image of the specified base image; 'output_base_image' should have the same content as the input's base image, however the path, image format, etc may differ 'fmt' is the disk image format. It is guessed automatically in most cases 'size' is the disk image size in kilobytes. Optional suffixes 'M' (megabyte, 1024 * 1024) and 'G' (gigabyte, 1024 * 1024 * 1024) are supported any 'k' or 'K' is ignored 'output_filename' is the destination disk image filename 'output_fmt' is the destination format 'options' is a comma separated list of format specific options in a name=value format. Use -o ? for an overview of the options supported by the used format '-c' indicates that target image must be compressed (qcow format only) '-h' with or without a command shows this help and lists the supported formats Parameters to snapshot subcommand: 'snapshot' is the name of the snapshot to create, apply or delete '-a' applies a snapshot (revert disk to saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all snapshots in the given image Supported formats: cow qcow vmdk cloop dmg bochs vpc vvfat qcow2 parallels nbd host_cdrom host_floppy host_device raw tftp ftps ftp https http and it doesn't mention the size problem at all. Even creation work without a single warning. ProblemType: Bug Architecture: amd64 Date: Sat Apr 17 18:17:28 2010 DistroRelease: Ubuntu 9.10 KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD muelli 26589 26588 13 175490 505084 0 17:41 pts/15 00:04:50 kvm -m 512 -monitor stdio -S -hda elster.img -smb /tmp/ -snapshot MachineType: LENOVO 766636G Package: kvm 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu6 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-21.31-generic 2.6.32.11+drm33.2 SourcePackage: qemu-kvm Uname: Linux 2.6.32-21-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 ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- qemu-img baseimage creation doesn't warn for image being smaller https://bugs.launchpad.net/bugs/565659 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 565659] Re: qemu-img baseimage creation doesn't warn for image being smaller
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/44622926/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/44622927/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/44622928/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/44622929/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/44622930/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/44622931/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/44622932/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/44622933/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/44622934/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/44622935/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/44622936/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/44622937/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/44622938/XsessionErrors.txt -- qemu-img baseimage creation doesn't warn for image being smaller https://bugs.launchpad.net/bugs/565659 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] Re: qemus pmemsave doesn't accept / in filename
1. Yes 2. kvm /tmp/someimage.img -monitor stdio ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = New -- qemus pmemsave doesn't accept / in filename https://bugs.launchpad.net/bugs/543478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] [NEW] qemus pmemsave doesn't accept / in filename
Public bug reported: 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 7fffe865eed8 error 14 in cron[40+9000] [150947.224187] cron[24261]: segfault at 0 ip (null) sp 7fffe865eed8 error 14 in cron[40+9000] Date: Sun Mar 21 15:03:13 2010 DistroRelease: Ubuntu 9.10 KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD muelli 23807 23806 13 239738 228464 0 14:54 pts/800: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 ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- qemus pmemsave doesn't accept / in filename https://bugs.launchpad.net/bugs/543478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 543478] Re: qemus pmemsave doesn't accept / in filename
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/41520545/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41520546/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/41520547/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/41520548/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/41520549/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/41520550/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/41520551/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/41520552/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/41520553/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/41520554/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/41520555/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/41520556/XsessionErrors.txt -- qemus pmemsave doesn't accept / in filename https://bugs.launchpad.net/bugs/543478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 474968] Re: kvm smb server hogs cpu guest freeze
No it does not hog the CPU if I'm not triggering it the way I described. I run the machine with 512 megs. ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = New -- kvm smb server hogs cpu guest freeze https://bugs.launchpad.net/bugs/474968 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 474969] [NEW] Documentation error: hostfwd syntax wrong
Public bug reported: Binary package hint: qemu-kvm The manpage is wrong. Currently it reads To redirect telnet connections from host port to telnet port on the guest, use the following: # on the host qemu -net user,hostfwd=tcp:::23 [...] telnet localhost but the correct syntax is -net user,hostfwd=tcp::2223-:22 Also, the documentation should mention that you *need* a -net nic for a -net user. That took me hours to figure out. ProblemType: Bug Architecture: amd64 Date: Thu Nov 5 01:26:04 2009 DistroRelease: Ubuntu 9.10 KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD 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 quiet splash crashkernel=384M-2G:64M,2G-:128M SourcePackage: qemu-kvm Uname: Linux 2.6.32-999-generic x86_64 dmi.bios.date: 07/01/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETB6WW (2.16 ) 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:bvr7NETB6WW(2.16):bd07/01/2008:svnLENOVO:pn766636G:pvrThinkPadX61s:rvnLENOVO:rn766636G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 766636G dmi.product.version: ThinkPad X61s dmi.sys.vendor: LENOVO ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Documentation error: hostfwd syntax wrong https://bugs.launchpad.net/bugs/474969 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 474969] Re: Documentation error: hostfwd syntax wrong
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/35126259/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/35126260/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35126261/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/35126263/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/35126264/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/35126265/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/35126266/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/35126267/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/35126268/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/35126269/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/35126270/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/35126271/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/35126272/XsessionErrors.txt -- Documentation error: hostfwd syntax wrong https://bugs.launchpad.net/bugs/474969 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 474968] [NEW] kvm smb server hogs cpu guest freeze
Public bug reported: Binary package hint: qemu-kvm kvm hogs the CPU reproducibly. I installed an Ubuntu using KVM. I run the machine with -net nic,model=rtl8139,macaddr=f0:00:BA:12:34:56 -net user,hostfwd=tcp::2223-:22,smb=/tmp/share, sshed into the machine and typed telnet 10.0.2.4 139 to try whether the SMB server works. KVM then hogs the CPU. ProblemType: Bug Architecture: amd64 Date: Thu Nov 5 01:23:09 2009 DistroRelease: Ubuntu 9.10 KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD 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 quiet splash crashkernel=384M-2G:64M,2G-:128M SourcePackage: qemu-kvm Uname: Linux 2.6.32-999-generic x86_64 dmi.bios.date: 07/01/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETB6WW (2.16 ) 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:bvr7NETB6WW(2.16):bd07/01/2008:svnLENOVO:pn766636G:pvrThinkPadX61s:rvnLENOVO:rn766636G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 766636G dmi.product.version: ThinkPad X61s dmi.sys.vendor: LENOVO ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- kvm smb server hogs cpu guest freeze https://bugs.launchpad.net/bugs/474968 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 474968] Re: kvm smb server hogs cpu guest freeze
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/35126223/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/35126228/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35126229/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/35126230/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/35126231/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/35126232/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/35126233/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/35126234/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/35126235/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/35126236/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/35126237/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/35126238/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/35126239/XsessionErrors.txt -- kvm smb server hogs cpu guest freeze https://bugs.launchpad.net/bugs/474968 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
