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
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.16
Public bug reported:
I have configured host filesystem access via virt-manager.
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
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 handl
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:
ubun
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
** 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-s
** 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
** 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.
--
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 char
FWIW: I can't reproduce anymore. It was not the memory leak though.
--
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-bu
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
** 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
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 j
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/565
** 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
** A
' 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 wor
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 su
** 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 adde
007fffe865eed8 error
14 in cron[40+9000]
[150947.224187] cron[24261]: segfault at 0 ip (null) sp 7fffe865eed8 error
14 in cron[400000+9000]
Date: Sun Mar 21 15:03:13 2010
DistroRelease: Ubuntu 9.10
KvmCmdLine:
UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD
muelli
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 yo
** 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
** A
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
** 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
** A
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,
25 matches
Mail list logo
