[Bug 1282816] [NEW] help output for delete volume indicates creating?
Public bug reported: $ euca-delete-volume -h Creates a volume in a specified availability zone. euca-delete-volume [-a, --access-key access_key ][-s, --secret-key ... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: euca2ools 2.1.3-1ubuntu1 Uname: Linux 3.13.0-ar-d8ec26d x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Feb 20 15:36:05 2014 InstallationDate: Installed on 2009-12-21 (1522 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: euca2ools UpgradeStatus: Upgraded to saucy on 2013-11-04 (108 days ago) ** Affects: euca2ools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/1282816 Title: help output for delete volume indicates creating? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/1282816/+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 663633] Re: package likewise-open (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/uuid', which is also in package uuid 0:1.6.2-1ubuntu1
No update in nearly three years. This bug is still present in the current LTS builds. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to likewise-open in Ubuntu. https://bugs.launchpad.net/bugs/663633 Title: package likewise-open (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/uuid', which is also in package uuid 0:1.6.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/663633/+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 1092342] Re: package likewise-open 6.1.0.406-0ubuntu5 failed to install/upgrade: trying to overwrite '/usr/bin/uuid', which is also in package uuid 1.6.2-1.1build3
*** This bug is a duplicate of bug 663633 *** https://bugs.launchpad.net/bugs/663633 ** This bug has been marked a duplicate of bug 663633 package likewise-open (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/uuid', which is also in package uuid 0:1.6.2-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to likewise-open in Ubuntu. https://bugs.launchpad.net/bugs/1092342 Title: package likewise-open 6.1.0.406-0ubuntu5 failed to install/upgrade: trying to overwrite '/usr/bin/uuid', which is also in package uuid 1.6.2-1.1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/1092342/+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 504368] Re: sdl window intermittently scales instead of resizing
Window manager varies. In the original report it was openbox (as I believe I stated, in comment #7). Current window manager is xfwm4. For the screenshot provided, I intentionally moved the window with Alt+left_click as I knew this would trigger the issue (also indicated in comment #7). However, as stated before, the issue happens seemingly randomly on its own without moving the window or interacting with it in any way. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/504368 Title: sdl window intermittently scales instead of resizing To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/504368/+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 504368] Re: sdl window intermittently scales instead of resizing
As requested here's a screenshot of the scaled window. The expected behavior is that the window be resized to the dimensions of the guest. Pressing Ctrl+Alt+u within this window corrects the issue and the window is in fact resized to the guest dimensions. ** Attachment added: Screenshot - 06112013 - 03:30:06 PM.png https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/504368/+attachment/3701167/+files/Screenshot%20-%2006112013%20-%2003%3A30%3A06%20PM.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/504368 Title: sdl window intermittently scales instead of resizing To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/504368/+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 1074460] Re: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration
Followed the steps provided and the current upstream source does not suffer from this issue. Last commit in current upstream source: commit 6801038bc52d61f81ac8a25fbe392f1bad982887. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1074460 Title: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1074460/+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 1074460] Re: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration
You don't need a license to reproduce this. You only need to attempt to boot from installation media. I'll happily try upstream qemu, can't say that I've done it before. Any pointers? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1074460 Title: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1074460/+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 1074460] Re: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration
I did some further digging on this and it appears that it only happens when the virtual machine definition includes a floppy device, either via -drive or -fda. Removal of the floppy device results in being able to successfully boot and install Windows XP. However, this does seem to prevent one from providing the virtio drivers for storage during installation as the additional storage drivers are provided via floppy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1074460 Title: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1074460/+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 1074460] [NEW] kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration
Public bug reported: Attempting to build a Windows XP virt using KVM results in a black screen after the familiar Setup is inspecting your computer's hardware configuration. No matter how long I wait there is no apparent progress of any kind and the VM CPU is pegged. Very similar to: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=684288. However, that report indicates the problem was fixed upstream in a version prior to what is provided with 12.10. So, perhaps the problem has reappeared. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: kvm 1:84+dfsg-0ubuntu16+1.2.0+noroms+0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 2 11:43:17 2012 InstallationDate: Installed on 2009-12-21 (1046 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD MachineType: LENOVO 2436CTO MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=/dev/mapper/ssd-root ro vga=792 splash nox2apic crashkernel=384M-2G:64M,2G-:128M quiet splash SourcePackage: qemu-kvm UpgradeStatus: Upgraded to quantal on 2012-10-12 (21 days ago) dmi.bios.date: 05/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET29WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO 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:bvrG5ET29WW(1.07):bd05/25/2012:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1074460 Title: kvm: windows xp installation hangs after Setup is inspecting your computer's hardware configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1074460/+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 246613] Re: ocfs2 startup link prior to open-iscsi
I have no idea why you claim the 3 listed items are not provided, they in fact have been. 1. install ofcs2-tools (apt-get install ofcs2-tools) 2. it should work, including after reboots 3. reread first post, it doesn't work after reboots due to startup order -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in ubuntu. https://bugs.launchpad.net/bugs/246613 Title: ocfs2 startup link prior to open-iscsi -- 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 246613] Re: ocfs2 startup link prior to open-iscsi
** Changed in: ocfs2-tools (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in ubuntu. https://bugs.launchpad.net/bugs/246613 Title: ocfs2 startup link prior to open-iscsi -- 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 329067] Re: Cannot change password on ldap client unless libpam-cracklib also installed
That's not really a viable solution as it introduces other issues. Once libpam-cracklib is installed and activated, creation of accounts that should not require a password prompt (disable login for example) all of a sudden does prompt for a password. -- Cannot change password on ldap client unless libpam-cracklib also installed https://bugs.launchpad.net/bugs/329067 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap 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 656173] Re: libvirt no longer probes chained backing stores
The automated run of libvirt-migrate-qemu-disks is great if your virtual machines are permanently defined within libvirt. However, if you simply inject and run a VM as needed, with something like the following: virsh create vm.xml Which is what I've been doing. The VM definitions will not hang around after the VM finishes executing. As such, this bug is very likely to silently hit you. I believe the upgrade needs a more prominent notice of this change. -- libvirt no longer probes chained backing stores https://bugs.launchpad.net/bugs/656173 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 470636] Re: AppArmor security driver does not support backingstore
You are indeed correct that specifying the format of the disk image file corrected the issue. However, this is also a fairly large regression over previous functionality. Configurations that worked flawlessly under lucid will now break under maverick. Additionally, the reason for the breakage will not be clear. There aren't any error messages reported, at least none that I could find, that would guide the user to what the problem actually is. -- AppArmor security driver does not support backingstore https://bugs.launchpad.net/bugs/470636 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 656173] Re: libvirt no longer probes chained backing stores
Jamie, I understand that the vm.xml does not contain enough information for the version of libvirt in maverick. I understand that with maverick's version one now has to supply a disk format. However, this was not the case with libvirt under lucid. Furthermore, not providing the disk format does not result in any meaningful error message that would guide the user to the actual cause of the problem. My point is that the very same vm.xml worked perfectly under the version of libvirt in lucid. Hence this is a regression, what did work no longer works. -- libvirt no longer probes chained backing stores https://bugs.launchpad.net/bugs/656173 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 656173] Re: libvirt no longer probes chained backing stores
Sure applications change with versions. However, they normally also provide useful error messages when something that was previously valid no longer is. This is *not* the case here. There is *no* error message. I'm not saying that users shouldn't provide valid XML when defining a VM. However, I am saying that if the XML being provided was previously valid and no longer is, that some clear indication about the change in validity should be given. There is no indication being given by the application. Yes, I believe the current behavior should change. No, I'm not disagreeing that this is a necessary security fix, nor am I saying that in the end this is somehow an undesired fix. What I am disputing is how the change is currently being handled. I do see that an effort has been made to migrate older configurations, and it does appear likely that this effort will catch the majority of cases. However, it won't catch all cases and the current handling leaves all remaining users wondering what the hell is going on with no guidance. I still see two points of contention. The first, and largest point of contention, is that due to the behavior change, previously valid XML configurations will now fail to operate as expected and will do so without any indication of why they are failing to operate. A change such as this should generate a log entry or something that would at least guide a user to documentation about the change and possible resolution. Perhaps an entry could be kicked out to the /var/log/libvirt/qemu/ per machine log file. Something along the lines of: WARNING: no drive image file format specified, defaulting to raw mode. Please specify drive image format. For more information please see: Second, I don't believe a blurb in the release notes alone is sufficient for this change. Why? Because, as indicated in the first point, there is no output from the application to indicate that the expected behavior has changed. Additionally, you've indicated that the existing behavior in lucid will be changing. As I understand it, this will be a simple security update. A change in behavior like this is definitely not something one would expect from a security update, not without a rather in your face notice about it. -- libvirt no longer probes chained backing stores https://bugs.launchpad.net/bugs/656173 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 656531] [NEW] libvirt unable to start VM with SDL display
Public bug reported: Since upgrading to 10.10, attempting to start any VM (new or pre- existing) that utilizes an SDL display fails. Initially, I thought it might be something with qemu/kvm. However, starting a VM with an SDL display manually with a command like the following, works fine: kvm -m 512 -cdrom dsl.iso -boot d I then thought it might be something with my pre-existing VMs definitions. So, I created a completely new VM using virt-manager. As long as the VM is using a VNC display it starts fine. However, once the VNC display is removed and replaced with an SDL display it fails to start. Log entries such as the following are created: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin XAUTHORITY=/home/jcollins/.Xauthority DISPLAY=:0.0 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name testing -uuid 37452670-32a9-4f86-8095-bc50c4111483 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/testing.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/opt/vms/testing.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:5e:ef:e6,bus=pci.0,addr=0x3 -net tap,fd=45,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -sdl -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/4 No protocol specified No protocol specified Could not initialize SDL - exiting ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libvirt-bin 0.8.3-1ubuntu14 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Oct 7 14:43:14 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- libvirt unable to start VM with SDL display https://bugs.launchpad.net/bugs/656531 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 656531] Re: libvirt unable to start VM with SDL display
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/656531/+attachment/1677836/+files/Dependencies.txt -- libvirt unable to start VM with SDL display https://bugs.launchpad.net/bugs/656531 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 615077] Re: [Maverick] SDL local window broken in last update
I reported #656531, which was marked as a duplicate of this. Indeed it is covered by this. However, I believe this is a much larger issue than this report makes it out to be. Importance on all components except qemu-kvm is still listed as undecided, and the problem isn't even with qemu-kvm. This problem is with virtinst and libvirt and is much higher than medium. This is a full on regression, configurations that worked under lucid will not work under maverick. This strikes me as a very severe or critical issue. -- [Maverick] SDL local window broken in last update https://bugs.launchpad.net/bugs/615077 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 470636] Re: AppArmor security driver does not support backingstore
This is still an issue in Maverick. -- AppArmor security driver does not support backingstore https://bugs.launchpad.net/bugs/470636 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 329067] Re: Cannot change password on ldap client unless libpam-cracklib also installed
What's more, with libpam-cracklib installed, creation of accounts that should have no password (password disabled accounts) still prompt for a password. The prompting for a password on password disabled account creation should probably be filed as a separate bug report, but I wanted to note it here for anyone affected by this bug. -- Cannot change password on ldap client unless libpam-cracklib also installed https://bugs.launchpad.net/bugs/329067 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap 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 613549] Re: does not support cloning vm storage on lvm backend
Restarting the libvirt daemon in addition to the above seems to have cleared things up. I can now clone LVM backed VMs. -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 613549] Re: does not support cloning vm storage on lvm backend
Rebooted the server and now I'm no longer getting the Could not determine original disk information: Disk '/dev/group/volume' does not exist. error. However it fails to actually perform the cloning with the following: Traceback (most recent call last): File /usr/share/virt-manager/virtManager/clone.py, line 756, in _async_clone CloneManager.start_duplicate(self.clone_design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 634, in start_duplicate _do_duplicate(design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 659, in _do_duplicate dst_dev.setup(meter) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 1076, in setup self._do_create_storage(progresscb) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 938, in _do_create_storage self._set_vol_object(self.vol_install.install(meter=progresscb), File /usr/lib/pymodules/python2.6/virtinst/Storage.py, line 1161, in install raise RuntimeError(Libvirt version does not support RuntimeError: Libvirt version does not support storage cloning. The only output in dmesg during this operation is this: [81563.970215] type=1503 audit(1281024773.950:22): operation=capable pid=1526 parent=1 profile=/usr/sbin/libvirtd name=fsetid -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 613549] Re: does not support cloning vm storage on lvm backend
Made the requested apparmor change, checked the dmesg output before attempting to clone the VM, found the following new entry: [90351.748748] type=1505 audit(1281033561.731:23): operation=profile_replace pid=7783 name=/usr/sbin/libvirtd Looks good so far. First attempt to clone the VM and set the new drive to the desired LVM device name resulted in an warning dialog: Cloning will overwrite the existing file Using an existing image will overwrite the path during the clone process. Are you sure you want to use this path? Answered yes and continued on. Cloning errors with the following: Traceback (most recent call last): File /usr/share/virt-manager/virtManager/clone.py, line 756, in _async_clone CloneManager.start_duplicate(self.clone_design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 634, in start_duplicate _do_duplicate(design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 659, in _do_duplicate dst_dev.setup(meter) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 1076, in setup self._do_create_storage(progresscb) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 968, in _do_create_storage self._clone_local(progresscb, size_bytes) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 1015, in _clone_local fd = os.open(self.path, os.O_WRONLY | os.O_CREAT) OSError: [Errno 2] No such file or directory: '/dev/vms/ldap' However, on the VM host: # ls -l /dev/vms/ldap lrwxrwxrwx 1 root root 18 2010-08-05 12:46 /dev/vms/ldap - ../mapper/vms-ldap # ls -l /dev/mapper/vms-ldap brw-rw 1 root disk 251, 16 2010-08-05 12:46 /dev/mapper/vms-ldap As you can see the device does in fact exist and this is backed up by the output of lvs: # lvs | grep ldap ldapvms -wi-a- 10.00g Now, removing the logical volume and starting fresh results in the following: Traceback (most recent call last): File /usr/share/virt-manager/virtManager/clone.py, line 756, in _async_clone CloneManager.start_duplicate(self.clone_design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 634, in start_duplicate _do_duplicate(design, meter) File /usr/lib/pymodules/python2.6/virtinst/CloneManager.py, line 659, in _do_duplicate dst_dev.setup(meter) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 1076, in setup self._do_create_storage(progresscb) File /usr/lib/pymodules/python2.6/virtinst/VirtualDisk.py, line 938, in _do_create_storage self._set_vol_object(self.vol_install.install(meter=progresscb), File /usr/lib/pymodules/python2.6/virtinst/Storage.py, line 1161, in install raise RuntimeError(Libvirt version does not support RuntimeError: Libvirt version does not support storage cloning. After which point virt-manager is fairly unresponsive, all statistics for the VMs are hung, and has to be forcibly exited. -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 613549] Re: does not support cloning vm storage on lvm backend
No, nothing. Here is the full kern.log since the reload: Aug 5 12:39:21 kvm-host kernel: [90351.748748] type=1505 audit(1281033561.731:23): operation=profile_replace pid=7783 name=/usr/sbin/libvirtd Aug 5 12:46:07 kvm-host kernel: [90757.988390] lo: Disabled Privacy Extensions Aug 5 13:34:13 kvm-host kernel: [93643.638255] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled Aug 5 13:34:13 kvm-host kernel: [93643.640841] SGI XFS Quota Management subsystem Aug 5 13:34:13 kvm-host kernel: [93643.647929] JFS: nTxBlock = 8192, nTxLock = 65536 Aug 5 13:34:13 kvm-host kernel: [93643.672639] NTFS driver 2.1.29 [Flags: R/O MODULE]. Aug 5 13:34:13 kvm-host kernel: [93643.701273] QNX4 filesystem 0.2.3 registered. Aug 5 13:34:13 kvm-host kernel: [93643.742493] Btrfs loaded Aug 5 13:34:14 kvm-host kernel: [93644.999234] EXT3-fs: INFO: recovery required on readonly filesystem. Aug 5 13:34:14 kvm-host kernel: [93644.999242] EXT3-fs: write access will be enabled during recovery. Aug 5 13:34:15 kvm-host kernel: [93645.020791] kjournald starting. Commit interval 5 seconds Aug 5 13:34:15 kvm-host kernel: [93645.020804] EXT3-fs: recovery complete. Aug 5 13:34:15 kvm-host kernel: [93645.021491] EXT3-fs: mounted filesystem with ordered data mode. Aug 5 13:34:51 kvm-host kernel: [93681.930679] kjournald starting. Commit interval 5 seconds Aug 5 13:34:51 kvm-host kernel: [93681.930700] EXT3-fs: mounted filesystem with ordered data mode. -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 613549] [NEW] does not support cloning vm storage on lvm backend
Public bug reported: It would appear that libvirt does not support cloning a VM that is using an LVM backend. Selecting Clone presents the user with a dialog prompting for a new name and options for networking and the storage details. However, below the LVM based storage entry is a statement: Could not determine original disk information: Disk '/dev/group/volume' does not exist. Where /dev/group/volume is the full path to the LVM volume being used by the VM. The referenced device does indeed exist, as it is successfully being used by the VM being cloned. Searching on this seems to indicate that there were patches provided back in July of '09: http://www.mail-archive.com/libvir-l...@redhat.com/msg14557.html It would appear that most of the patches were accepted: http://www.mail-archive.com/libvir-l...@redhat.com/msg14709.html Looks like the version in Lucid (0.7.5) was released several months after those patches were committed (based on the above referenced messages and the upstream release archive). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu27 ProcVersionSignature: Ubuntu 2.6.32-23.37-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-server x86_64 Architecture: amd64 Date: Wed Aug 4 11:12:09 2010 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 613549] Re: does not support cloning vm storage on lvm backend
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/53054416/Dependencies.txt -- does not support cloning vm storage on lvm backend https://bugs.launchpad.net/bugs/613549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 610103] [NEW] package suggests editing an installed non-conffile for normal operation
Public bug reported: Binary package hint: migrationtools The package's README file indicates that one should edit migrate_common.ph and change at least two lines: $DEFAULT_MAIL_DOMAIN $DEFAULT_BASE However, migrate_common.ph is installed at /usr/share/perl5/migrate_common.ph and is not (AFAICT) a conffile. As such, any changes made to file will be lost on subsequent installations and upgrades. As these two lines are intended to be edited/configured on a per- installation basis, perhaps they should be moved out to a configuration file that resides somewhere under /etc. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: migrationtools 47-8ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Mon Jul 26 08:48:51 2010 InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 (20100427) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: migrationtools ** Affects: migrationtools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- package suggests editing an installed non-conffile for normal operation https://bugs.launchpad.net/bugs/610103 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to migrationtools 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 610103] Re: package suggests editing an installed non-conffile for normal operation
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/52533789/Dependencies.txt -- package suggests editing an installed non-conffile for normal operation https://bugs.launchpad.net/bugs/610103 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to migrationtools 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 610103] Re: package suggests editing an installed non-conffile for normal operation
Some further investigation shows that there is a symlink created in the /etc/migrationtools directory: $ ls -l /etc/migrationtools/migrate_common.ph lrwxrwxrwx 1 root root 43 2010-07-26 06:53 /etc/migrationtools/migrate_common.ph - /usr/share/migrationtools/migrate_common.ph However, the symlink is to a non-existent file: $ ls -l /usr/share/migrationtools/migrate_common.ph ls: cannot access /usr/share/migrationtools/migrate_common.ph: No such file or directory because the file is actually installed at /usr/share/perl5/migrate_common.ph -- package suggests editing an installed non-conffile for normal operation https://bugs.launchpad.net/bugs/610103 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to migrationtools 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 329067] Re: Cannot change password on ldap client unless libpam-cracklib also installed
This bug is indeed still present in Lucid. With an account only present in LDAP and the default common-password configuration, I get the following when trying to change the password for the user stored in LDAP: $ sudo passwd testing passwd: Authentication information cannot be recovered passwd: password unchanged Removing only the use_authtok parameter, I get the following: $ sudo passwd testing New password: Re-enter new password: LDAP password information changed for testing passwd: password updated successfully -- Cannot change password on ldap client unless libpam-cracklib also installed https://bugs.launchpad.net/bugs/329067 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap 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 520386] Re: libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to create domain with virt-manager using network bridge
I too would like to see this fixed for Lucid. It's rather tedious to create a domain then have to hand edit the configuration. -- libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to create domain with virt-manager using network bridge https://bugs.launchpad.net/bugs/520386 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 345485] Re: libvirt does not remove interfaces on stop
If it created the interface on it's startup, it should remove the interface on it's shutdown. Simple as that. -- libvirt does not remove interfaces on stop https://bugs.launchpad.net/bugs/345485 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 345485] Re: libvirt does not remove interfaces on stop
True, I'd forgotten that libvirt could be stopped and the VMs remain running. -- libvirt does not remove interfaces on stop https://bugs.launchpad.net/bugs/345485 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 372001] Re: default network autostart symlink recreated
I don't want them undefined or removed, only not set to auto start. -- default network autostart symlink recreated https://bugs.launchpad.net/bugs/372001 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 345485] Re: libvirt does not remove interfaces on stop
Still present in up to date Lucid beta $ ifconfig -a | grep vir virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30 $ sudo service libvirt-bin stop libvirt-bin stop/waiting $ ifconfig -a | grep vir virbr0Link encap:Ethernet HWaddr 5a:85:91:8b:65:30 ** Changed in: libvirt (Ubuntu) Status: Incomplete = Confirmed -- libvirt does not remove interfaces on stop https://bugs.launchpad.net/bugs/345485 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 504368] Re: sdl window intermittently scales instead of resizing
Just had it happen again. Simply started the VM, didn't touch the SDL window for it at all, guest wound up scaled. Here's the xwininfo output for the SDL window: xwininfo: Window id: 0x6e3 QEMU (winxp-work) Absolute upper-left X: 640 Absolute upper-left Y: 367 Relative upper-left X: 1 Relative upper-left Y: 20 Width: 720 Height: 480 Depth: 24 Visual Class: DirectColor Border width: 0 Class: InputOutput Colormap: 0x6ec (not installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +640+367 -560+367 -560-353 +640-353 -geometry 720x480+639+347 -- sdl window intermittently scales instead of resizing https://bugs.launchpad.net/bugs/504368 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 504368] Re: sdl window intermittently scales instead of resizing
@Dustin, I've experienced the problem with a rebuild of the lucid package for karmic. The package is in my PPA, https://launchpad.net/~jcollins/+archive/jaminppa. @Anthony, I can assure you that I've seen the scaling without resizing the client window in any way. Simply starting the VM and leaving it untouched periodically results in a scaled display. -- sdl window intermittently scales instead of resizing https://bugs.launchpad.net/bugs/504368 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 504368] Re: sdl window intermittently scales instead of resizing
I frequently relocate my VM displays. My host system's window manager is openbox. Normally, for moving any window about my screen, I utilize the ALT+left-click feature to drag the window about. This has the added benefit of ensuring I don't accidentally resize the window. Most of my guests are Windows based at the moment. When the display scales it tends to remain the size of the booting splash screen. I just tried some different methods of starting the VMs and dragging the displays about. If I'm performing an ALT+left-click drag when the display wants to resize it seems to switch to scaling instead. So, this may be part of it, but I am very certain I've seen the same result when simply starting the VM and not touching the display in any way. -- sdl window intermittently scales instead of resizing https://bugs.launchpad.net/bugs/504368 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 513544] [NEW] libvirt 0.7.5 crashed on first virt-manager connection
Public bug reported: The release version of libvirt-0.7.5 suffers from a bug that causes it to segfault on the first connection attempt from each virt-manager launch. The upstream bug report for this is: https://bugzilla.redhat.com/show_bug.cgi?id=556815 There is a patch referenced in the report that fixes the issue. I've attached it to this report. From what I can tell the version planned for Lucid does not include this change. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- libvirt 0.7.5 crashed on first virt-manager connection https://bugs.launchpad.net/bugs/513544 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 513544] Re: libvirt 0.7.5 crashed on first virt-manager connection
** Patch added: patch to avoid freeing uninitialized pointer http://launchpadlibrarian.net/38472167/9018-dont-free-an-uninitalized-pointer.patch -- libvirt 0.7.5 crashed on first virt-manager connection https://bugs.launchpad.net/bugs/513544 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 504368] Re: sdl window intermittently scales instead of resizing
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/37560230/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/37560231/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37560232/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/37560233/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/37560234/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/37560235/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/37560236/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/37560237/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/37560238/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/37560239/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/37560240/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37560241/XsessionErrors.txt -- sdl window intermittently scales instead of resizing https://bugs.launchpad.net/bugs/504368 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 504368] [NEW] sdl window intermittently scales instead of resizing
Public bug reported: Binary package hint: qemu-kvm Normally, the SDL output window for a VM resizes to match the VM's resolution. However, intermittently the output is instead scaled within the window. I can't seem to find any pattern to when the output is scaled versus when the window is resized. I would prefer that the window be resized as needed to display the VM in a 1:1 manner. ProblemType: Bug Architecture: amd64 Date: Thu Jan 7 10:30:10 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 27618 1 38 241752 804668 1 10:05 ?00:09:39 /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -m 768 -smp 1 -name win2k3 -uuid da414aa0-f18a-7a02-3d1b-1dbf13137bc9 -monitor unix:/var/run/libvirt/qemu/win2k3.monitor,server,nowait -localtime -boot c -drive file=/media/qpc-devel/testing/win2k3/testing.ovl,if=ide,index=0,boot=on -drive file=/media/qpc-devel/testing/win2k3/../../isos/en_win_srv_2003_r2_standard_cd1.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:d6:f5:60,vlan=0,model=ne2k_pci,name=ne2k_pci.0 -net tap,fd=18,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vga cirrus root 28306 1 54 177732 545520 1 10:28 ?00:00:49 /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -m 512 -smp 1 -name win2k -uuid 153d6125-acb5-70bc-c7d2-bcbf87c5be86 -monitor unix:/var/run/libvirt/qemu/win2k.monitor,server,nowait -localtime -boot c -drive file=/media/qpc-devel/testing/win2k/testing.ovl,if=ide,index=0,boot=on -drive file=/media/qpc-devel/testing/win2k/../../isos/windows_2000.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=68:29:6b:13:50:c6,vlan=0,model=ne2k_pci,name=ne2k_pci.0 -net tap,fd=19,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vga cirrus NonfreeKernelModules: nvidia Package: kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=30218f9a-6f90-4eab-9ba5-f54897e842cb ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: qemu-kvm Uname: Linux 2.6.31-16-generic x86_64 dmi.bios.date: 02/20/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB2WW (2.12 ) 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:bvr7LETB2WW(2.12):bd02/20/2008:svnLENOVO:pn:pvrThinkPadT61p:rvnLENOVO:rn:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.version: ThinkPad T61p dmi.sys.vendor: LENOVO ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- sdl window intermittently scales instead of resizing https://bugs.launchpad.net/bugs/504368 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 372001] Re: default network autostart symlink recreated
Steps to reproduce: Create additional network definitions. I have the following (all set to start on boot): - public_1, 192.168.51.0/24, 192.168.51.128, 192.168.51.254, w/NAT - private_1, 192.168.61.0/24, 192.168.61.128, 192.168.61.254, isolated - private_2, 192.168.62.0/24, 192.168.62.128, 192.168.62.254, isolated Disable the default network definition (uncheck Autostart and Apply). Verify that the symlink for starting the default network definition is no longer present: ls -l /etc/libvirt/qemu/networks/autostart/ Install, or reinstall, the libvirt-bin package or any update to the package. The symlink for the default network autostart is restored. -- default network autostart symlink recreated https://bugs.launchpad.net/bugs/372001 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 203020] Re: virsh attach-disk doesn't work
** Attachment added: device file used to eject the drive http://launchpadlibrarian.net/31546265/no-cdrom.xml -- virsh attach-disk doesn't work https://bugs.launchpad.net/bugs/203020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 203020] Re: virsh attach-disk doesn't work
I found using a device xml file works in Jaunty with 0.7.0-0ubuntu0~ppa2, haven't tried older version, but it may work with them as well. I could not get the attach or detach -disk options to work. However using the device xml seems to work. I've attached the xml file I use to attach my system's physical CD-ROM to the VM. Detaching is (oddly enough) accomplished by attaching an empty device. I'll upload the no-cdrom.xml after this. virsh attach-device winxp ~/cdrom.xml ** Attachment added: cdrom definition for physical drive http://launchpadlibrarian.net/31546244/cdrom.xml -- virsh attach-disk doesn't work https://bugs.launchpad.net/bugs/203020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 50385] Re: samba can't be launched by a normal user (qemu related)
I can confirm that this is still a problem with jaunty. -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 371687] Re: smb option doesn't appear to work
*** This bug is a duplicate of bug 50385 *** https://bugs.launchpad.net/bugs/50385 ** This bug has been marked a duplicate of bug 50385 samba can't be launched by a normal user (qemu related) -- smb option doesn't appear to work https://bugs.launchpad.net/bugs/371687 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu (via bug 50385). -- 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
