[Bug 973096] Re: Nvidia driver causes xorg crash
Can you please provide some valid links? Those don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973096] Re: Nvidia driver causes xorg crash
Actually, found amd64 on https://launchpad.net/ubuntu/precise/amd64 /nvidia-current/290.10-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011698] Re: Performance problems with Nvidia driver
I am also affected by this exact same issue 04:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce 7100 GS] (rev a1) This card is used to drive two LCD screens for standard gnome shell configuration in 12.04 when i try using the normal nvidia-current package or the one from the ppa (with version 302.17) my desktop freezes. Last few times this has locked the whole machine meaning i needed to pull the plug to get the system back up. I have purged the nvidia-current package and now have LCD mirroring on my screens (not very useful for me). This did not happen before i upgraded to 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011698 Title: Performance problems with Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1011698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806969] [NEW] xterm -into id not working correctly
Public bug reported: When re-parenting xterm into another window using '-into id' the term ignores all input. When using a different terminal such as urxvt -embed id it works as expected Attached scripts shows the problem when typing into the new window when using xterm and urxvt $ dpkg -l |grep xterm ii xterm 268-1ubuntu1 $ more /etc/debian_version squeeze/sid system is up to date ** Affects: xterm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806969 Title: xterm -into id not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/806969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806969] Re: xterm -into id not working correctly
** Attachment added: Script showing the problem https://bugs.launchpad.net/bugs/806969/+attachment/2195378/+files/gtk2_try.pl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806969 Title: xterm -into id not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/806969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589223] [NEW] kvm domain failing to start after kernel upgrade to 2.6.32-22
Public bug reported: Binary package hint: qemu-kvm KVM hosts were working OK prior to upgrade. Upgraded kernel to linux- image-2.6.32-22-generic and now hosts hang on boot up. Reproduced with reduced kvm command as code $ kvm -cdrom Disk_Images/ubuntu-10.04-beta1-server-amd64.iso -boot d pci_add_option_rom: failed to find romfile pxe-rtl8139.bin /code A console window is opened but is blank and remains that way. Rebooting machine onto previous kernel allows kvm host to start up as expected. Please also see http://ubuntuforums.org/showthread.php?p=9404334 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kvm 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Jun 3 16:03:39 2010 KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD 1000 3963 3905 99 139969 15980 1 15:57 pts/600:06:33 kvm -cdrom Disk_Images/ubuntu-10.04-beta1-server-amd64.iso -boot d MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 10/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: G31M-GS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- kvm domain failing to start after kernel upgrade to 2.6.32-22 https://bugs.launchpad.net/bugs/589223 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 589223] [NEW] kvm domain failing to start after kernel upgrade to 2.6.32-22
Public bug reported: Binary package hint: qemu-kvm KVM hosts were working OK prior to upgrade. Upgraded kernel to linux- image-2.6.32-22-generic and now hosts hang on boot up. Reproduced with reduced kvm command as code $ kvm -cdrom Disk_Images/ubuntu-10.04-beta1-server-amd64.iso -boot d pci_add_option_rom: failed to find romfile pxe-rtl8139.bin /code A console window is opened but is blank and remains that way. Rebooting machine onto previous kernel allows kvm host to start up as expected. Please also see http://ubuntuforums.org/showthread.php?p=9404334 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kvm 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Jun 3 16:03:39 2010 KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD 1000 3963 3905 99 139969 15980 1 15:57 pts/600:06:33 kvm -cdrom Disk_Images/ubuntu-10.04-beta1-server-amd64.iso -boot d MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 10/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: G31M-GS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- kvm domain failing to start after kernel upgrade to 2.6.32-22 https://bugs.launchpad.net/bugs/589223 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589223] Re: kvm domain failing to start after kernel upgrade to 2.6.32-22
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49610847/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49610848/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49610849/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49610850/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49610851/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49610852/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49610853/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49610854/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/49610855/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49610856/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49610857/UdevLog.txt -- kvm domain failing to start after kernel upgrade to 2.6.32-22 https://bugs.launchpad.net/bugs/589223 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490264] Re: kvm wont boot off a qcow2 overlay disk image
*** This bug is a duplicate of bug 470636 *** https://bugs.launchpad.net/bugs/470636 Thanks for pointing out the original case - i didn't find it when I searched (used different search terms). The work around in that bug (option 2) fixed it for me. Thanks -- kvm wont boot off a qcow2 overlay disk image https://bugs.launchpad.net/bugs/490264 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 490264] Re: kvm wont boot off a qcow2 overlay disk image
*** This bug is a duplicate of bug 470636 *** https://bugs.launchpad.net/bugs/470636 Thanks for pointing out the original case - i didn't find it when I searched (used different search terms). The work around in that bug (option 2) fixed it for me. Thanks -- kvm wont boot off a qcow2 overlay disk image https://bugs.launchpad.net/bugs/490264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490264] [NEW] kvm wont boot off a qcow2 overlay disk image
Public bug reported: Binary package hint: qemu-kvm kvm no longer booted domains based on overlay disk images: $ kvm-img create -f qcow2 /srv/vm_disks/dev20/disk0.qcow2 8192M Formatting '/srv/vm_disks/dev20/disk0.qcow2', fmt=qcow2 size=8589934592 encryption=off cluster_size=0 $ kvm-img create -f qcow2 -b /srv/vm_disks/dev20/disk0.qcow2 /srv/vm_disks/dev20/disk0_snapshot.ovl Formatting '/srv/vm_disks/dev20/disk0_snapshot.ovl', fmt=qcow2 size=8589934592 backing_file='/srv/vm_disks/dev20/disk0.qcow2' encryption=off cluster_size=0 $ virt-install --connect qemu:///system --name dev20 --ram 512 --arch x86_64 --vcpus 2 --check-cpu --file /srv/vm_disks/dev20/disk0_snapshot.ovl --nonsparse --network network:default --vnc --noautoconsole --hvm --accelerate --cdrom /home/dferguson/Disk_Images/debian-40r7-amd64-netinst.iso --os-type linux --os-variant debianEtch Starting install... internal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start dev20'; otherwise, please restart your installation. ERRORinternal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl Traceback (most recent call last): File /usr/bin/virt-install, line 780, in module main() File /usr/bin/virt-install, line 678, in main start_time, guest.start_install) File /usr/bin/virt-install, line 733, in do_install dom = install_func(conscb, progresscb, wait=(not wait)) File /usr/lib/python2.6/dist-packages/virtinst/Guest.py, line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File /usr/lib/python2.6/dist-packages/virtinst/Guest.py, line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File /usr/lib/python2.6/dist-packages/libvirt.py, line 1077, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl $ ls -la /srv/vm_disks/dev20/disk0_snapshot.ovl -rw-r--r-- 1 dferguson dferguson 262144 2009-11-30 09:28 /srv/vm_disks/dev20/disk0_snapshot.ovl $ file /srv/vm_disks/dev20/disk0_snapshot.ovl /srv/vm_disks/dev20/disk0_snapshot.ovl: Qemu Image, Format: Qcow , Version: 2 $ kvm-img info /srv/vm_disks/dev20/disk0_snapshot.ovl image: /srv/vm_disks/dev20/disk0_snapshot.ovl file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 131K cluster_size: 65536 backing file: /srv/vm_disks/dev20/disk0.qcow2 (actual path: /srv/vm_disks/dev20/disk0.qcow2) $ apt-cache policy qemu-kvm qemu-kvm: Installed: 0.11.0-0ubuntu6.3 Candidate: 0.11.0-0ubuntu6.3 Version table: *** 0.11.0-0ubuntu6.3 0 500 http://gb.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 0.11.0-0ubuntu6 0 500 http://gb.archive.ubuntu.com karmic/main Packages $ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 This was fine when running Intrepid - happened immediately on upgrading to Karmic. I see the same error on creating a new vm or trying to boot a vm that worked without issue prior to the upgrade. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- kvm wont boot off a qcow2 overlay disk image https://bugs.launchpad.net/bugs/490264 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 490264] [NEW] kvm wont boot off a qcow2 overlay disk image
Public bug reported: Binary package hint: qemu-kvm kvm no longer booted domains based on overlay disk images: $ kvm-img create -f qcow2 /srv/vm_disks/dev20/disk0.qcow2 8192M Formatting '/srv/vm_disks/dev20/disk0.qcow2', fmt=qcow2 size=8589934592 encryption=off cluster_size=0 $ kvm-img create -f qcow2 -b /srv/vm_disks/dev20/disk0.qcow2 /srv/vm_disks/dev20/disk0_snapshot.ovl Formatting '/srv/vm_disks/dev20/disk0_snapshot.ovl', fmt=qcow2 size=8589934592 backing_file='/srv/vm_disks/dev20/disk0.qcow2' encryption=off cluster_size=0 $ virt-install --connect qemu:///system --name dev20 --ram 512 --arch x86_64 --vcpus 2 --check-cpu --file /srv/vm_disks/dev20/disk0_snapshot.ovl --nonsparse --network network:default --vnc --noautoconsole --hvm --accelerate --cdrom /home/dferguson/Disk_Images/debian-40r7-amd64-netinst.iso --os-type linux --os-variant debianEtch Starting install... internal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start dev20'; otherwise, please restart your installation. ERRORinternal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl Traceback (most recent call last): File /usr/bin/virt-install, line 780, in module main() File /usr/bin/virt-install, line 678, in main start_time, guest.start_install) File /usr/bin/virt-install, line 733, in do_install dom = install_func(conscb, progresscb, wait=(not wait)) File /usr/lib/python2.6/dist-packages/virtinst/Guest.py, line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File /usr/lib/python2.6/dist-packages/virtinst/Guest.py, line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File /usr/lib/python2.6/dist-packages/libvirt.py, line 1077, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open disk image /srv/vm_disks/dev20/disk0_snapshot.ovl $ ls -la /srv/vm_disks/dev20/disk0_snapshot.ovl -rw-r--r-- 1 dferguson dferguson 262144 2009-11-30 09:28 /srv/vm_disks/dev20/disk0_snapshot.ovl $ file /srv/vm_disks/dev20/disk0_snapshot.ovl /srv/vm_disks/dev20/disk0_snapshot.ovl: Qemu Image, Format: Qcow , Version: 2 $ kvm-img info /srv/vm_disks/dev20/disk0_snapshot.ovl image: /srv/vm_disks/dev20/disk0_snapshot.ovl file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 131K cluster_size: 65536 backing file: /srv/vm_disks/dev20/disk0.qcow2 (actual path: /srv/vm_disks/dev20/disk0.qcow2) $ apt-cache policy qemu-kvm qemu-kvm: Installed: 0.11.0-0ubuntu6.3 Candidate: 0.11.0-0ubuntu6.3 Version table: *** 0.11.0-0ubuntu6.3 0 500 http://gb.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 0.11.0-0ubuntu6 0 500 http://gb.archive.ubuntu.com karmic/main Packages $ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 This was fine when running Intrepid - happened immediately on upgrading to Karmic. I see the same error on creating a new vm or trying to boot a vm that worked without issue prior to the upgrade. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- kvm wont boot off a qcow2 overlay disk image https://bugs.launchpad.net/bugs/490264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs