tags 570245 + pending
thanks
Christophe Benz wrote:
Hi,
Your package corrects the bug (0.12.3).
Thank you for testing Christophe.
(And still does not work with 0.11.1+dfsg-1, with the same conditions).
I'm preparing 0.12.3 for real, since we now have
all the necessary dependencies in
reassign 572625 virt-manager
retitle 572625 virt-manager apparently changes ownership of disk images
thanks
Giovanni Toraldo wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: important
I cannot start a newly created VM using a vmdk image, probably by a
permission problem.
Toni Mueller wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: normal
Hello,
networking does not come up on my machine. I changed the script
[]
# only add the interface to default-route bridge if we
# have such interface (with default route) and if that
# interface is actually
Package: ftp.debian.org
Severity: normal
The kvm package is transitional now in squeeze+,
since upstream changed name from kvm to qemu-kvm.
So we created a dummy package to simplify upgrade
path but placed it to oldlibs so it will be visible
by utilities such as deborphan and similar. Following
2 Vassili: full bugreport can be seen online at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572943
We (Debian) just updated qemu-kvm from 0.11 to 0.12.3.
Can you comment please? Thank you.
Christian Ohm wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-2
Severity: important
Hello,
The
severity 570245 important
thanks
I'm lowering severity of this from grave back to important
since the issue were quite infrequent and only reproduceable
on a few systems.
Thanks.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
malc wrote:
On Mon, 8 Mar 2010, Michael Tokarev wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572943
If the OP uses SDL, then it's most likely fixed by
ff5414990645653bf43bf64adfc1ca77ffb9edcb i've no idea whether kvm
0.12.3 includes this though, if not i'm interested in seeing
tags 572930 + pending
tags 572924 + pending
thanks
Frank Lin PIAT wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: normal
Hi,
Recent kernels (including Lenny, IIRC), publish DMI information in
/sys/class/dmi/.
In /usr/share/bug/qemu-kvm, you could uses something like that (I
Bjørn Mork wrote:
Looking at the list of available modes in the guest showed that there
was no 1440x900 anymore, which probably explains why Windows chose
another one close by. There were also a number of other expected modes
missing.
Think I got it.
The modes were once added to
tags 572991 + pending
thanks
Bjørn Mork wrote:
Michael Tokarev m...@tls.msk.ru writes:
[]
I too noticed that the list of video modes available is quite a bit
shorter than it used to be, but at that time I were dealing with
another bug and didn't pay enough attention to that fact, and it
were
tags 573280 + pending
thanks
Bastian Blank wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-3
Severity: grave
qemu-kvm fails to install:
| Unpacking qemu-kvm (from .../qemu-kvm_0.12.3+dfsg-3_amd64.deb) ...
| No packages found matching kvm.
| dpkg: error processing
Gary Dale wrote:
Package: qemu-kvm
Followup-For: Bug #572784
Networking starts only on the first time that I start an XP virtual
machine after a reboot of the actual machine. If I subsequently restart
the virtual machine, or the XP instance within it, the network only
comes up enough for
tags 573439 + upstream patch pending
thanks
Kouichi ONO wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-3
Severity: normal
Hello,
On version 0.12.3, -drive serial=XXX option does not work.
Below patch fixes it. 'serial' is pointer, not array.
--- qemu-kvm-0.12.3+dfsg/vl.c 2010-02-26
of the
patches, and resend the whole lot to qemu-de...@nongnu.org.
You can add my
Tested-By: Michael Tokarev m...@tls.msk.ru
if you wish.
But if you prefer me to handle all this, just indicate
that, and I'll happily do what I can.
Thank you very much!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist
01.05.2010 10:05, Martin Stut wrote:
Interesting. Here, kvm nevers stops. But this is,
perhaps, due to a more recent host kernel: mine is
2.6.33.3, which received qutie a few kvm updates.
I'm using kernel 2.6.32-3-bigmem #1 SMP, the one that is currently
shipped with Debian testing
01.05.2010 10:05, Martin Stut wrote:
The system run attempt
kvm -m 1024 -hda /backup/qemu/francke4/francke4.img -cdrom
/backup/qemu/francke4/winnt4.iso -cpu host -boot order=cd -net
nic,model=rtl8139,vlan=0,macaddr=00:11:22:33:44:66 -net user,vlan=0
-localtime -name francke4 -monitor stdio
06.05.2010 23:25, Martin Stut wrote:
Am 05.05.2010 10:56, schrieb Michael Tokarev:
Now one more try please:
kvm ... -cpu qemu64,level=1
this should cure the 0x3E issue during install time.
-cpu qemu64,level=1
I tried that, but KVM just produces the error message
Unable to find x86 CPU
severity 579751 minor
thanks
30.04.2010 19:28, Harald Dunkel wrote:
On 04/30/10 15:14, Michael Tokarev wrote:
Please show the kvm command line in use.
/usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 4096 -smp
2,sockets=2,cores=1,threads=1 -name solaris10u6-x86-template -uuid
9575f7a9-c101-460a
Package: x11-common
Version: 1:7.3+20
Severity: minor
Tags: patch
In x11-common.postinst the /etc/X11/Xwrapper.config gets created using
tmpfile ($NEW_XWRAPPER_CONFIG). By default, tmpfile creates temp file
with mode 0600. With that mode the new file is installed to the right
place.
There's no
Toni Mueller wrote:
Hi Michael,
Hello!
On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev m...@tls.msk.ru wrote:
Toni, please verify if this bug is present in the current
version of qemu-kvm in unstable (0.12.3+dfsg-4). If you
don't like using unstable, try out qemu-kvm from my page
tags 574988 + moreinfo
thanks
Adam Majer wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
I've been using KVM for quite some time now to run Windows XP, 2000,
Vista, and Win 7. Though all the generations of KVM, video speed was
acceptable. After installing qemu-kvm, video
Michal Suchanek wrote:
Package: qemu
Version: 0.12.3+dfsg-2
Severity: important
I could not find any documentation of support for the kqemu
acceleration. As kvm is not available on all machines and kqemu
supposedly makes the emulation faster as well as workarounds bugs in the
software
Brian Kroth wrote:
Guido Günther a...@sigxcpu.org 2010-03-28 14:53:
[]
Could you try to add execute this by hand and find the offending
option?
-- Guido
Yeah, I did that. It's as the other bug I linked said. Basically,
libvirt changed the way it arranges the command lines from the XML
Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
severity 570245 grave
Bug #570245 [qemu-kvm] qemu-kvm: kvm exits with unhandled vm exit: 0x11
Severity set to 'grave' from 'important'
Stefen, can you please, this and next time you merely
increases severity,
Christophe, can you please try 0.12 qemu-kvm
packages from my site, http://www.corpit.ru/debian/tls/kvm/
and see if these fixes your problem?
This bug is difficult to reproduce, upstream says
it's fixed long ago, and it also seems to affect
only Intel machines, but I only have AMD CPUs here.
The
Stefan Fritsch wrote:
On Mon, 1 Mar 2010, Michael Tokarev wrote:
Stefen, can you please, this and next time you merely
increases severity, give at least some hint about your
justification?
I thought from the original report it was obvious that this makes kvm
unusable, therefore this bug
severity 578154 wishlist
thanks
17.04.2010 16:15, Michal Suchanek hramr...@centrum.cz пишет:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
$ kvm -m 512 -hda vmcli -net nic -net
tap,ifname=tap0,script=no,downscript=no -usb -usbdevice tablet -vnc :0
warning: could not configure
Package: lxsession
Version: 0.4.4-1
Severity: wishlist
lxsession uses a config file (and there's a config file editor,
lxsession-edit package). But unfortunately, the local config
file (~/.config/lxsession/LXDE/config) is not being used, but
only the global one (/etc/xdg/lxsession/LXDE/conifg)
retitle 578160 missing useable documentation
thanks
17.04.2010 18:03, Michael Tokarev wrote:
Package: lxsession
Version: 0.4.4-1
Severity: wishlist
lxsession uses a config file (and there's a config file editor,
lxsession-edit package). But unfortunately, the local config
file (~/.config
Package: initscripts
Version: 2.87dsf-10
Severity: minor
That message gets printed during boot each numerous times,
at least as many as there are interfaces configured in
/etc/network/interfaces. This clutters up the boot logs
etc with useless information.
I found quite a few references on the
Package: initscripts
Version: 2.87dsf-10
Severity: normal
It appears that NFS mounts are not working at bootup anymore.
Not sure since what time.
Here's a typical boot log with ASYNCMOUNTNFS is not set:
Setting up networking
Configuring network interfaces...if-up.d/mountnfs[br0]: waiting
found 539952 0.1.7-1
thanks
The bug #539952 is only partially fixed in 0.1.7-1.
Before, only Alt+0 worked. In 0.1.7-1, Alt+2..Alt+0
works (9 keys), but not Alt+1. Running just cat in
the lxterminal and hitting Alt+2 - this produces
^[2, Alt+3 - ^[3 and so on, but for Alt+1 there's
nothing
18.04.2010 17:48, Michael Tokarev wrote:
The bug #539952 is only partially fixed in 0.1.7-1.
Before, only Alt+0 worked. In 0.1.7-1, Alt+2..Alt+0
works (9 keys), but not Alt+1. Running just cat in
the lxterminal and hitting Alt+2 - this produces
^[2, Alt+3 - ^[3 and so on, but for Alt+1 there's
Package: compiz
Version: 0.8.4-3
Severity: normal
0.8.4-1 (debian version) dropped compiz-manager script and implemented
everything in compiz binary. I mean the patch taken from ubuntu,
debian/patches/060_move_checks_to_compiz.patch .
Now, there are 2 problems with this approach:
1. It is
normally as all other keys, thus allowing one to
assign a command to that key sequence.
Signed-Off-By: Michael Tokarev m...@tls.msk.ru
--- compiz-0.8.4/src/event.c.orig 2010-04-19 17:25:36.677931239 +
+++ compiz-0.8.4/src/event.c2010-04-19 17:27:06.004697317 +
@@ -376,9 +376,9
20.04.2010 22:13, Marc Siegwald wrote:
[]
I have the same problem : BUG: unable to handle kernel paging request at
..
The same as what? Paging request at what?
Same problem as Message #30...
Which message #30? Where that message is?
My kernel is Linux 2.6.32-4-amd64 (see
20.04.2010 23:00, Marc Siegwald wrote:
Le 20/04/2010 20:20, Michael Tokarev a écrit :
Same problem as Message #30...
Which message #30? Where that message is?
My kernel is Linux 2.6.32-4-amd64 (see Message #35)
Which message #35?
I'm using http://bugs.debian.org/cgi-bin/bugreport.cgi?bug
21.04.2010 20:23, Sébastien wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
Tags: squeeze
I'm trying to install Frugalware in a kvm virtual machine, with the following
command : $ kvm -hda vm/frugalwarelibellule.img -cdrom
images/frugalware-1.2-i686-net.iso -boot d -m 512
21.04.2010 21:13, Gary Dale wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
Every time my Windows XP/Pro virtual machine starts or retarts, it takes
out my screen saver and screen power manager. I have to manually restart
them. This has been happening since I first installed
21.04.2010 21:43, Gary Dale wrote:
Michael Tokarev wrote:
21.04.2010 21:13, Gary Dale wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
Every time my Windows XP/Pro virtual machine starts or retarts, it takes
out my screen saver and screen power manager. I have to manually
21.04.2010 23:03, Sébastien wrote:
Le 21/04/2010 19:24, Michael Tokarev a écrit :
Actually their bootloader is eating 100% cpu during all time,
probably in a loop waiting for keyboard events. And it is
graphical too, and graphics mode gets turned on right after
Loading stage 2 message. So I've
tags 565550 + moreinfo
thanks
13.03.2010 14:39, Georg Gast wrote:
Michael Tokarev schrieb:
Georg Gast wrote at Sat, 16 Jan 2010 22:37:10 +0100:
Package: hal
Version: 0.5.14-1
Severity: normal
After installing hal on a kfreebsd port of Debian on a kvm platform
(Debian/Squeeze Linux 2.6.32
severity 575720 normal
thanks
Downgrading severity to normal since the problem is
easy to work around (at least in some cases) and because
the probelm does not affect the core functionality.
Yes the cirrus vga is slow, and it's a quite difficult
to find issue in the upstream kvm. Hopefully
severity 504049 wishlist
thanks
I'm downgrading severity of this bug to wishlist.
Reason is that it's quite rare to use virtual fat
to start with (actually it isn't even documented
in qemu-kvm anymore), and especially with -snapshot.
Also, upstream isn't willing to work on this corner
case and
tags 578396 + moreinfo
thanks
19.04.2010 19:20, Gary Dale wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: normal
This is weird. I found it necessary to reinstall Debian/Squeeze. This
shouldn't have affected my Windows XP/Pro VM since it was in my home
directory. However, after
tags 565573 + pending
tags 565573 - patch
thanks
17.01.2010 07:53, Leo 'costela' Antunes wrote:
Package: qemu-kvm
Version: 0.11.1-2
Severity: minor
Hi,
The current manpage for qemu doesn't mention the -incoming switch,
used for live migrations.
Upstream seems to not have included it in their
25.04.2010 17:17, Gary Dale wrote:
[]
I've tried converting my original .qcow file to a new .qcow file and
also to a raw file (which took a long time but seems faster than qcow,
but is also larger - it seems to occupy the full space I initially
created the virtual partition with). Unfortunately
tags 579341 + pending
thanks
27.04.2010 10:25, Artyom Pervukhin wrote:
Subject: qemu-kvm: kvm process memory leak
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: important
Tags: upstream
*** Please type your report below this line ***
After several days of running, kvm process started with
27.04.2010 07:54, Gary Dale wrote:
Further to below, I figured I'd try a re-install using virt-manager -
something I couldn''t get working earlier. I noticed when I installed
virt-manager, it installed a whole raft of software related to the qemu
(not qemu-kvm) package.
It also seems to be
27.04.2010 12:08, Alexandre Fayolle wrote:
Package: qemu
Version: 0.12.3+dfsg-4
Severity: normal
Hi,
I've created a 30GB disk image with qemu-img using qcow2 format, and I was able
to
install windows XP on that image using an ISO image (via libvirt). However when
booting again
the image I
28.04.2010 11:00, Konstantin Stepanyuk wrote:
This issue has been fixed in upstream with a patch here:
http://lists.gnu.org/archive/html/qemu-devel/2010-04/msg00377.html
http://git.debian.org/?p=collab-maint/qemu-kvm.git;a=commit;h=8737e37ee07e1ac66db44a4d0908356ebd6b48b3
I applied that
Harald Dunkel wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
If I use rtl8139 network device emulation, then this
device doesn't show up in the Solaris 10 guest.
Using e1000 instead there is no such problem.
There was no such problem for qemu-kvm 0.11.0+dfsg-1.
Seems that this
30.04.2010 19:32, Martin Stut wrote:
[]
kvm -m 1024 -hda /backup/qemu/francke4/francke4.img -cdrom
/backup/qemu/francke4/winnt4.iso -net
nic,vlan=0,macaddr=00:11:22:33:44:66 -net user,vlan=0 -localtime -name
francke4 -monitor stdio
results in: STOP 0x001E (0xC005, 0x8001449C,
01.05.2010 02:45, Bruno Miguel wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: important
I've installed qemu-kvm under Debian Squeeze and I'm unable to run any virtual
machine. Everytime I try to run an ISO file, this is what happens: http://m
01.05.2010 02:45, Bruno Miguel wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: important
I've installed qemu-kvm under Debian Squeeze and I'm unable to run any virtual
machine. Everytime I try to run an ISO file, this is what happens: http://m
01.05.2010 03:04, Bruno Miguel wrote:
[]
I've tried Ubuntu 9.10 and Ubuntu 10.04 isos and got the exact same
problems. Fedora 13 KDE beta also doesn't work.
Wonderful... Not!
How do I redirect the output to a text file? 'kvm -hda ubuntu.img
-cdrom ubuntu-10.04-desktop-i386.iso -m 512M
01.05.2010 03:23, Bruno Miguel wrote:
[]
Here is what I could grab with screen:
[2.463626] [c012b5b7] bad_area_nosemaphore+0x17/0x20
[2.463923] [c058dc76] do_page_fault+0x2f6/0x3a0
[2.464221] [c058d980] ? do_page_fault+0x0/0x3a0
Not there yet. it's basically the same as you
severity 579810 normal
thanks
01.05.2010 03:48, Bruno Miguel wrote:
On Sat, May 1, 2010 at 12:26 AM, Michael Tokarevm...@tls.msk.ru wrote:
01.05.2010 03:23, Bruno Miguel wrote:
[]
[]
This is the output screen let's me select:
And it's still the same.
[]
Here is a video to prove that I
01.05.2010 04:08, Bruno Miguel wrote:
[]
Sorry, I totally forgot to tell the hosts kernel. Here it is: Linux
2.6.32-3-686 #1 SMP i686 GNU/Linux
That's ok, and the kernel is fine too.
The md5 is the same.
Excellent.
I too have no idea how to use kvm with a serial console. I'll try to
find
tags 569990 + moreinfo
thanks
08.04.2010 21:04, Marc Siegwald wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Hi
I have the same problem : BUG: unable to handle kernel paging request at
..
The same as what? Paging request at what?
I'll close this bugreport unless you provide much
10.04.2010 00:09, C.J. Adams-Collier wrote:
Package: wnpp
Severity: wishlist
Owner: C.J. Adams-Collierc...@colliertech.org
Owner: C.J. Adams-Collierc...@colliertech.org
* Package name: xen-unmodified-drivers
Version : 3.4.3
Upstream Author : Xen
Toni Mueller wrote at Wed, 03 Feb 2010 18:17:51 +0100:
Package: qemu-kvm
Version: 0.11.0+dfsg-1~bpo50+1
Severity: important
Hello,
my virtual machine(s) become unresponsive every few days and need to be
killed then. While being unresponsive, the machine consumes 100% CPU,
fortunately
Toni Mueller wrote at Tue, 16 Feb 2010 16:58:13 +0100:
Hi,
[]
on a different machine, running Testing/i386, the VM boots nicely to
the login prompt using -i686 variant of the 2.6.32 kernel, but there is
no network. On the host system, I can see tap0, and on tap0, I can
see the DHCP requests
Toni Mueller wrote at Tue, 16 Feb 2010 11:46:04 +0100:
Hi,
On Mon, 15.02.2010 at 18:36:19 +0100, Toni Mueller supp...@oeko.net wrote:
I'm running into a severe problem, where I'm unsure about the origin.
Please feel free to re-assign as appropriate.
three of them running Etch, Lenny, and
tags 504049 + confirmed upstream
thanks
Josh Triplett wrote at Thu, 30 Oct 2008 13:03:28 -0700:
Package: kvm
Version: 72+dfsg-2
Severity: normal
The KVM virtual FAT drive does not work with -snapshot. For instance:
$ kvm -fda fat:/tmp/foo -cdrom rescue.iso -boot d -snapshot
qemu: could
Georg Gast wrote at Sat, 16 Jan 2010 22:37:10 +0100:
Package: hal
Version: 0.5.14-1
Severity: normal
After installing hal on a kfreebsd port of Debian on a kvm platform
(Debian/Squeeze Linux 2.6.32) it spams tty1 (Ctrl Alt 1) and syslog with the
shown message in the title of this
tags 570244 + help
thanks
Goran Janes wrote at Wed, 17 Feb 2010 16:10:47 +0100:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: normal
I'm trying to run Debian Stable on qemu but it won't start. This is the
command:
sudo kvm -hda server.img -cdrom
severity 572784 wishlist
thanks
Toni Mueller wrote:
Hi,
On Sat, 06.03.2010 at 19:02:33 +0300, Michael Tokarev m...@tls.msk.ru wrote:
fragile (I for one will hate packages which substitute my
eth0 with a bridge and change firewall rules behind my back).
agreed. This would easily become
Gary Dale wrote:
Michael Tokarev wrote:
Gary Dale wrote:
Package: qemu-kvm
Followup-For: Bug #572784
Networking starts only on the first time that I start an XP virtual
machine after a reboot of the actual machine. If I subsequently restart
the virtual machine, or the XP instance within
Gary Dale wrote:
OK, I think I've got it now. I found
http://blog.cynapses.org/2007/07/12/qemu-kvm-internal-network-setup/
which provided some additional settings for the -net options.
Using a made-up mac address and -net tap,ifname=tap0,script=no gave me
an IP address from my local network
tags 561879 + wontfix
thanks
Josh Triplett wrote:
Package: qemu-kvm
Version: 0.11.0+dfsg-1
Severity: wishlist
Currently, kvm defaults to emulated hardware, not virtio. To make the
use of virtio more automatic, I'd propose that KVM's virtio devices
should have the ability to handle
severity 574063 wishlist
retitle 574063 should not fall back to qemu unless requested
thanks
Russell Coker wrote:
What I would prefer is to have it default to not operating unless KVM is
available and have a command-line option to use QEMU.
This is how it will be done in to-be-released
Russell Coker wrote:
Package: kvm
Version: 72+dfsg-5~lenny5
Severity: normal
When the path specified by -mem-path isn't writable the error message
mkstemp: Permission denied is displayed on stderr - which means that it
can't be seen until after the kvm session is ended when using the
Russell Coker wrote:
On Tue, 16 Mar 2010, Michael Tokarev m...@tls.msk.ru wrote:
When the path specified by -mem-path isn't writable the error message
mkstemp: Permission denied is displayed on stderr - which means that it
can't be seen until after the kvm session is ended when using
Toni Mueller wrote:
Hi Michael,
On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev m...@tls.msk.ru wrote:
From what you provided above it sounds like some sort of i/o
problem, but without much more details (exact kvm command line,
kinds of disk devices you use, and some sorts of traces
Toni Mueller wrote:
[]
kvm -localtime -no-acpi -m 512 \
-net nic,model=rtl8139,macaddr=52:54:00:12:34:56,vlan=0 \
-daemonize \
-net tap,vlan=0 /mounts/vmachines/kvm/d-sid/sid1.img
--- cut
Ugh, can you retry without -no-acpi? -no-acpi is basically
tags 574051 + pending upstream confirmed
thanks
Stuart Pook wrote:
Package: kvm
Version: 1:0.12.3+dfsg-4
Severity: normal
After an upgrade none of my virtual machines will start any more. They all
give the error
isa irq 4 already assigned. This appears to be because you can no longer
Santiago Vila wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Note that current version is 0.12.3+dfsg-4. JFYI.
I see that qemu-kvm uses these fields:
Package: qemu-kvm
Replaces: kvm
Conflicts: kvm
The Conflicts: kvm is not really necessary. It forces kvm to be
removed before
reassign 574063 qemu-kvm
reassign 574051 qemu-kvm
reassign 574073 qemu-kvm
reassign 574069 qemu-kvm
thanks
Reassigning (some) bugs against kvm package to qemu-kvm.
The version in Lenny is frozen and is too old and buggy
to be useful. In squeeze+ the package is qemu-kvm, not
kvm. And all the
Michal Suchanek hramr...@centrum.cz wrote:
Package: kvm
Version: 72+dfsg-5~lenny4
Severity: normal
[1]+ Segmentation fault kvm -m 512 -net
tap,ifname=tap0,script=no,downscript=no -net nic -vnc :1 /srv/kvm/img2
-cdrom /srv/kvm/binary.iso -boot d -M isapc
Michal, please be aware
Russell Coker wrote:
On Tue, 16 Mar 2010, Michael Tokarev m...@tls.msk.ru wrote:
Or kvm could use syslog or some other mechanism for logging such things.
Where the error message will not be noticed either. With current
form it at least has a chance to be noticed after the guest exits
I've been biten by this issue too.
When a PC in basement, which were running for several
years has been rebooted (power lost, clean shutdown
off UPS) and later it turned out it had bad CMOS battery.
Actually it had bad battery for quite some time and
I knew it, but it is such a large issue to get
I've similar prob here too.
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1280b1, caps: 0xa04713/0x204000
I: Bus=0011 Vendor=0002 Product=0007 Version=12b1
N: Name=SynPS/2 Synaptics TouchPad
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input7
U: Uniq=
H:
Michael Tokarev пишет:
I've similar prob here too.
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1280b1, caps: 0xa04713/0x204000
I: Bus=0011 Vendor=0002 Product=0007 Version=12b1
N: Name=SynPS/2 Synaptics TouchPad
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input
[commit 52e039f3b0a5749f706b97491087b9632d30512f in hal git tree,
http://cgit.freedesktop.org/hal/commit/?id=52e039f3b0a5749f706b97491087b9632d30512f]
That commit in hal (released as 0.5.14) - apparently -
causes some breakage.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562052
is one
Dmitry Torokhov wrote:
[]
B: KEY=6420 7000f 0 0 0 0
B: ABS=1103
[]
- if (test_bit (ABS_PRESSURE, bitmask_abs)) {
[]
What's wrong? ;)
Not sure, seems to be working here... Keying on ABS_PRESSURE is
It apparently works on some laptops here and fails on others.
definitely
Dmitry Torokhov wrote:
On Thu, Dec 24, 2009 at 11:32:27PM +0300, Michael Tokarev wrote:
Dmitry Torokhov wrote:
[]
B: KEY=6420 7000f 0 0 0 0
B: ABS=1103
[]
- if (test_bit (ABS_PRESSURE, bitmask_abs)) {
[]
What's wrong? ;)
Not sure, seems to be working here... Keying
Michael Tokarev wrote:
Dmitry Torokhov wrote:
On Thu, Dec 24, 2009 at 11:32:27PM +0300, Michael Tokarev wrote:
B: KEY=6420 7000f 0 0 0 0
B: ABS=1103
[]
Not really :( We print in groups of longs so it is either 32 or 64 bits
worth of data per number.
Ok, I stand corrected. I verified
Package: initscripts
Version: 2.86.ds1-61
Severity: normal
Tags: patch
Current initscripts checks kernel command line in /lib/init/vars.sh
to set some variables which are used later in various /etc/init.d/*
scripts. In particular, it has the following test:
if [ -r /proc/cmdline ] grep -q '
tags 604604 + moreinfo
thanks
23.11.2010 01:20, Jakub Wilk wrote:
Package: qemu-kvm
Version: 0.13.0+dfsg-2
Severity: grave
Justification: renders package unusable
After 0.12.5+dfsg-5 - 0.13.0+dfsg-2 upgrade kvm doesn't start anymore.
I get an error immediately:
$ kvm
kvm: vm entry
tags 604604 - moreinfo
tags 604604 + confirmed upstream patch
reassign 604604 linux-image-2.6.32-5-i686 2.6.32-27
severity 604604 normal
thanks
23.11.2010 01:20, Jakub Wilk wrote:
Package: qemu-kvm
Version: 0.13.0+dfsg-2
Severity: grave
Justification: renders package unusable
After
tags 604604 - upstream patch
thanks
Hello again.
After a bit more testing it turns out this problem is
somehow specific to debian 2.6.32-5-686-27 kernel,
it does not occur on upstream (kernel.org) kernel
even when not applying the mentioned patch (which
went into upstream -stable just a few days
severity 604844 wishlist
retitle 604844 request saner default behavour when run as root and $DISPLAY is
not accessible
tags 604844 + confirmed
thanks
24.11.2010 22:10, Hugo Mills wrote:
Package: qemu-kvm
Version: 0.12.5+dfsg-4
Severity: important
When starting a VM with SDL video
24.11.2010 23:15, Hugo Mills wrote:
[]
When starting a VM with SDL video output, I end up with a black
screen containing a (blinking) text-mode cursor in the top left
corner. The kvm process dies immediately. It is impossible to
console-switch to a text VT (Ctrl-Alt-F1), or indeed do
25.11.2010 01:26, Jakub Wilk wrote:
Package: qemu-kvm
Version: 0.13.0+dfsg-2
Severity: normal
kvm with a virtual FAT disk crashes when trying to boot a FreeBSD
kernel[0]. Backtrace:
#0 0xf7786425 in __kernel_vsyscall ()
#1 0xf7166751 in raise (sig=6) at
25.11.2010 12:10, Konstantin Alekseev wrote:
Package: qemu-kvm
Version: 0.12.5+dfsg-4
Severity: important
Tags: squeeze
While rebooting windows 2003 server guest, error occured:
kvm: unhandled exit
kvm_run returned -22
This seems to be the same as #604604.
The problem is
28.11.2010 05:25, Ben Hutchings wrote:
Please can you test whether this is fixed in 2.6.32-28? We backported a
KVM feature (VCPU_EVENTS) which meant we needed an additional fix beyond
the one which Michael Tokarev identified, and that was done in -28.
Yes, with 2.6.32-28 686 kernel I can't
While #389996 is relevant here as well (as in, default
/etc/network/run should be moved to /lib/init/rw/),
the problem in this #306224 is different, and it is
much more apparent now when insserv is running all
the scripts.
The problem here is that /etc/init.d/ifupdown does
not depend on anything
30.11.2010 14:58, Константин Алексеев wrote:
Package: qemu-kvm
Version: 0.12.5+dfsg-4
Severity: important
Tags: squeeze
While rebooting windows 2003 server guest, error occured:
kvm: unhandled exit
30.11.2010 15:06, Michael Tokarev wrote:
[]
Please see http://bugs.debian.org/599507 - this is the same
issue as this #604900 -- #604900 has been merged with 599507.
This is incorrect -- #604604 has been merged with #599507,
not this #604900.
The fix is available in -testing (kernel 2.6.32-28
101 - 200 of 2533 matches
Mail list logo
