Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
[1308405713.767653] change /devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-2/target3:0:2/3:0:2:0/block/sdc (block) UDEV [1308405713.772146] change /devices/pci:00/:00:02.0/:07:00.3/:08:01.1/host3/rport-3:0-3/target3:0:3/3:0:3:0/block/sdd (block) UDEV [1308405713.778288] change /devices/pci:00/:00:02.0/:07:00.3/:08:01.0/host2/rport-2:0-3/target2:0:3/2:0:3:0/block/sdb (block) john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+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
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 04:04:46PM -, Martin Pitt wrote: Accepted multipath-tools into natty-proposed, the package will build now and be available in a few hours. [snip] ** Changed in: ubuntu Status: Confirmed = Invalid ** Changed in: Ubuntu Lucid Status: Confirmed = Invalid So this won't be SRU'd for lucid? Unfortunately, I don't have any affected machines running natty, and can't upgrade the affected lucid machine(s) to that release in order to provide feedback. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/644489/+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
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Fri, Jun 24, 2011 at 05:15:33PM -, Serge Hallyn wrote: the bug was also nominated for lucid. The proposed package just hasn't been accepted (yet) into lucid-proposed, but I've seen no indication that it was rejected. Cool. Does the LP bug get notified when it's accepted into -proposed, or should I check for it in -proposed periodically? john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/644489/+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
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote: Excellent, you're still interested. I've got a fix for you to try. Attached is a custom version of mpath_prio_netapp that should not generate any more change events for you. Please post for comparison that this new version returns the same data as the old one. [snip] Once you verify that the updated prio checker no longer generates change events, start up multipathd again and verify that this continues to be true. Thanks! Everything seems to be as anticipated: [j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get install multipath-tools=0.4.8-14ubuntu4 multipath-tools-boot=0.4.8-14ubuntu4 kpartx=0.4.8-14ubuntu4 [...] [j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo mpath_prio_netapp $i; done 4 1 4 1 [j...@pxe-237.roch.ny:pts/0 ~ sudo apt-get dist-upgrade [...] Preparing to replace kpartx 0.4.8-14ubuntu4 (using .../kpartx_0.4.8-14ubuntu5~lp644489_amd64.deb) ... [...] Preparing to replace multipath-tools 0.4.8-14ubuntu4 (using .../multipath-tools_0.4.8-14ubuntu5~lp644489_amd64.deb) ... [...] Preparing to replace multipath-tools-boot 0.4.8-14ubuntu4 (using .../multipath-tools-boot_0.4.8-14ubuntu5~lp644489_all.deb) ... [...] [j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/sd[abcd]; do sudo mpath_prio_netapp $i; done 4 1 4 1 [j...@pxe-237.roch.ny:pts/0 ~ psg multi root 30498 30498 0.0 0.0 85396 3500 ? SLl futex_ 13:24 /sbin/multipathd root 30498 30500 0.0 0.0 85396 3500 ? SLl futex_ 13:24 /sbin/multipathd root 30498 30514 0.0 0.0 85396 3500 ? SLl dm_wai 13:24 /sbin/multipathd root 30498 30515 0.0 0.0 85396 3500 ? SLl hrtime 13:24 /sbin/multipathd root 30498 30516 0.0 0.0 85396 3500 ? SLl skb_re 13:24 /sbin/multipathd root 30498 30517 0.0 0.0 85396 3500 ? SLl poll_s 13:24 /sbin/multipathd root 30498 30518 0.0 0.0 85396 3500 ? SLl futex_ 13:24 /sbin/multipathd [j...@pxe-237.roch.ny:pts/0 ~ sudo udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent [no events generated] john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+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
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Sat, Jun 18, 2011 at 09:00:59PM -, Peter Petrakis wrote: Excellent, you're still interested. I've got a fix for you to try. Attached is a custom version of mpath_prio_netapp Would you provide a patch to multipath-tools instead, please? I'd be more comfortable building a patched binary myself. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489/+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
Re: [Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
On Wed, Apr 13, 2011 at 03:59:58PM -, Serge Hallyn wrote: Does fixing the rule to use '-q' fix this bug for you? Doesn't seem to. Changing the one instance of -Q in /lib/udev/rules.d/95-kpartx.rules to -q doesn't change the behavior described in this bug. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing -- 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 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
Wasn't sure which /dev paths you were interested in specifically, so here's ~everything that might be relevant. We don't run the stock syslog configuration, so I filtered out multipathd verbose output from our syslogs and attached it; let me know if you were looking for something more than multipathd's verbose syslogs. [j...@pxe-237.roch.ny:pts/0 ~ for i in /dev/disk/by-id/* /dev/sd*; do echo -n $i ; sudo /sbin/mpath_prio_netapp $i; done /dev/disk/by-id/dm-name-rootvol 4 /dev/disk/by-id/dm-name-rootvol-part1 4 /dev/disk/by-id/dm-name-rootvol-part10 4 /dev/disk/by-id/dm-name-rootvol-part11 4 /dev/disk/by-id/dm-name-rootvol-part12 4 /dev/disk/by-id/dm-name-rootvol-part13 4 /dev/disk/by-id/dm-name-rootvol-part14 4 /dev/disk/by-id/dm-name-rootvol-part15 4 /dev/disk/by-id/dm-name-rootvol-part2 4 /dev/disk/by-id/dm-name-rootvol-part5 4 /dev/disk/by-id/dm-name-rootvol-part6 4 /dev/disk/by-id/dm-name-rootvol-part7 4 /dev/disk/by-id/dm-name-rootvol-part8 4 /dev/disk/by-id/dm-name-rootvol-part9 4 /dev/disk/by-id/dm-uuid-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part1-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part10-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part11-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part12-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part13-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part14-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part15-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part2-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part5-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part6-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part7-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part8-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/dm-uuid-part9-mpath-360a98000486e5339576f5336524d5273 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/scsi-360a98000486e5339576f5336524d5273-part9 4 /dev/disk/by-id/scsi-rootvol 4 /dev/disk/by-id/scsi-rootvol-part1 4 /dev/disk/by-id/scsi-rootvol-part10 4 /dev/disk/by-id/scsi-rootvol-part11 4 /dev/disk/by-id/scsi-rootvol-part12 4 /dev/disk/by-id/scsi-rootvol-part13 4 /dev/disk/by-id/scsi-rootvol-part14 4 /dev/disk/by-id/scsi-rootvol-part15 4 /dev/disk/by-id/scsi-rootvol-part2 4 /dev/disk/by-id/scsi-rootvol-part5 4 /dev/disk/by-id/scsi-rootvol-part6 4 /dev/disk/by-id/scsi-rootvol-part7 4 /dev/disk/by-id/scsi-rootvol-part8 4 /dev/disk/by-id/scsi-rootvol-part9 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part1 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part10 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part11 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part12 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part13 1 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part14 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part15 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part2 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part5 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part6 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part7 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part8 4 /dev/disk/by-id/wwn-0x60a98000486e5339576f5336524d5273-part9 4 /dev/sda 4 /dev/sda1 4 /dev/sda10 4 /dev/sda11 4 /dev/sda12 4 /dev/sda13 4 /dev/sda14 4 /dev/sda15 4 /dev/sda2 4 /dev/sda5 4 /dev/sda6 4 /dev/sda7 4 /dev/sda8 4 /dev/sda9 4 /dev/sdb 1 /dev/sdb1 1 /dev/sdb10 1 /dev/sdb11 1 /dev/sdb12 1 /dev/sdb13 1 /dev/sdb14 1 /dev/sdb15 1 /dev/sdb2 1 /dev/sdb5 1 /dev/sdb6 1 /dev/sdb7 1 /dev/sdb8 1 /dev/sdb9 1 /dev/sdc 4 /dev/sdc1 4 /dev/sdc10 4 /dev/sdc11 4 /dev/sdc12 4 /dev/sdc13 4 /dev/sdc14 4 /dev/sdc15 4 /dev/sdc2 4 /dev/sdc5 4 /dev/sdc6 4 /dev/sdc7 4 /dev/sdc8 4 /dev/sdc9 4 /dev/sdd 1 /dev/sdd1 1 /dev/sdd10 1 /dev/sdd11 1 /dev/sdd12 1 /dev/sdd13 1 /dev/sdd14 1 /dev/sdd15 1 /dev/sdd2 1 /dev/sdd5 1 /dev/sdd6 1 /dev/sdd7 1 /dev/sdd8 1 /dev/sdd9 1 **
[Bug 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
I should also note that the errant behavior has changed a little since we first observed it; events used to be generated constantly, but now there are large bursts every ~20s. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing -- 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 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
What additional information do you need? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/644489 Title: constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing -- 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Fri, Mar 18, 2011 at 05:13:55PM -, Lars Hansson wrote: The problem with the upstart solution is that it doesn't work since Upstart will kill the virsh instances that you spawn in shutdown_guests. That's only the case if you don't follow the instructions to patch sendsigs to avoid that bug: #44: John Morrissey wrote on 2010-09-17: Finally, this modified upstart job requires the fix for https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/639940. Otherwise, the libvirt-bin pre-stop script isn't guaranteed to finish successfully, since sendsigs races the child processes executed during the course of the job script. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown -- 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 579596] Re: VNC console doesn't accept keyboard input during PXE boot
I imagine this is still a problem, since the only update (to the qemu- kvm or syslinux packages in lucid) since I reported this bug was to fix an iovec memory leak in qemu-kvm. I'm not sure if the problem lies in qemu-kvm or in syslinux. What it boils down to is that newer versions of qemu-kvm don't work with syslinux 3.86, but I'm not sure what the underlying problem is. Like I said, I looked through the upstream syslinux changelogs and didn't notice any obvious changes that would have fixed this. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Thu, Nov 04, 2010 at 11:43:10AM -, Valentijn Sessink wrote: The proposals in this report (mine, John Morrissey's) all have a pre- stop shutdown of virtual machines in their Upstart conf-file. When you update libvirt-bin, dpkg will stop libvirt-bin before upgrading. As a result — if you have implemented the pre-stop shutdown — your virtual machines will all stop. Sorry, that's incorrect. The libvirt-bin upstart job I wrote will only shut down VMs if the physical machine is entering runlevels 0 or 6 (i.e., shutdown or reboot): -- pre-stop script if [ -z $RUNLEVEL ]; then exit 0 fi if [ $RUNLEVEL -ne 0 ] [ $RUNLEVEL -ne 6 ]; then exit 0 fi -- john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Sat, Oct 02, 2010 at 02:54:47AM -, Nathan Crawford wrote: FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the libvirt packaging. I think it already is? (dpkg --status libvirt-bin says it is... but I've been changing things all over the place so I might have confused it) Yes, my fault. debhelper probably adds it as a conffile automatically. Also, are these changes based on Lucid packages? The Lucid machine I'm using for testing has a kernel panic on shutdown with the packages from my PPA installed. Yes, I'm running these changes on a number of lucid machines. Maybe the changed behavior triggers something in the kernel that's causing a panic? I can't really say without seeing the full panic output. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Fri, Oct 01, 2010 at 03:47:07AM -, Nathan Crawford wrote: @John Morrissey - Nice work on getting this working! I hope you don't mind, I've taken the liberty of packaging all your changes and putting them in a PPA for easier testing. Thanks, and packaging the changes is no problem at all. FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the libvirt packaging. Also, it might make more sense to package omit-kvm-vm-pids as part of libvirt instead of a separate package; makes it harder to forget to install it. One question on omit-kvm-vm-pids from #51, what does the '##*/' mean toward the end of line 26? It's a shell construct that removes text at the beginning of a parameter. In this case, the net effect is to remove the leading pathname, so all that's left is the filename ('##' is longest match, and the pattern is '*/'). Since it's a shell builtin, it's faster than calling basename(1), although speed is arguably important here. :-) Looking at it again, that for loop should probably have a guard so it gracefully handles the case where no QEMU VMs are running: for pidfile in /var/run/libvirt/qemu/*.pid; do if [ $pidfile = '/var/run/libvirt/qemu/*.pid' ]; then break fi if ! cp -f $pidfile /lib/init/rw/sendsigs.omit.d/libvirt-bin-${pidfile##*/}; then status=1 fi done john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
On Wed, Sep 22, 2010 at 09:47:47AM -, Valentijn Sessink wrote: - if the shutdown script searches for the word running (like mine does, - but John Morrissey's script is affected, too), it must set LANG=C at the - top, otherwise virsh will run in the local language. Good catch. I've updated libvirt-bin.conf; let's see if LP accepts attachments via e-mail. john -- John Morrissey _o/\ __o j...@horde.net_- \_ / \ \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ ** Attachment added: libvirt-bin.conf https://bugs.launchpad.net/bugs/350936/+attachment/1622533/+files/libvirt-bin.conf ** Attachment added: omit-kvm-vm-pids https://bugs.launchpad.net/bugs/350936/+attachment/1622534/+files/omit-kvm-vm-pids -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
For example, running 'multipath -v0 /dev/sda' while watching 'udevadm monitor -e' shows one event generated for each path, each time the multipath command is run. Each even would generate another multipath(8) invocation. Looks like the multipath(8) action in 95-multipath.rules is causing an infinite event loop. ** Package changed: udev (Ubuntu) = multipath-tools (Ubuntu) -- constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing https://bugs.launchpad.net/bugs/644489 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools 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 644489] Re: constantly changes /dev/disk/by-id/{scsi, wwn}-* LUN symlinks with multipathing
Looks like this call to multipath(8) in the udev rules was added quite a while ago. I'm not sure where to go from here; our hardy machines don't exhibit this behavior, and I'm not sure what's generating the events or how to break the loop short of commenting out the udev rule action. multipath-tools (0.4.8-11) unstable; urgency=low [...] * [4f8a5d1] Call multipath via udev on block device add/change events This helps slow devices when either /etc/init.d/multipath-tools-boot or the initramfs script are being run although the devices are not ready yet. (Closes: #489850) - many thanks to Janusz Dziemidowicz for his suggestions and testing [...] -- Guido Guenther a...@sigxcpu.org Wed, 30 Jul 2008 17:59:03 -0400 -- constantly changes /dev/disk/by-id/{scsi,wwn}-* LUN symlinks with multipathing https://bugs.launchpad.net/bugs/644489 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools 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 644481] Re: 95-kpartx.rules uses invalid -Q argument to modprobe(8)
0.4.8-14ubuntu4. Sorry, I forgot to mention that. -- 95-kpartx.rules uses invalid -Q argument to modprobe(8) https://bugs.launchpad.net/bugs/644481 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools 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 350936] Re: Should shut down domains on system shutdown
The attached file updates libvirt-bin's upstart job to gracefully shut down VMs when the system shuts down. You can alter the shutdown timeout (SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use (URIS, default: qemu:///system) in /etc/default/libvirt-bin. You'll also need the omit-kvm-vm-pids init script (attachment forthcoming), which copies the KVM pidfiles to /lib/init/rw/sendsigs.omit.d, preventing /etc/init.d/sendsigs from killing KVM VM processes before the updated libvirt-bin upstart job shuts them down. Finally, this modified upstart job requires the fix for https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/639940. Otherwise, the libvirt-bin pre-stop script isn't guaranteed to finish successfully, since sendsigs races the child processes executed during the course of the job script. With all of these changes, VMs shut down gracefully with the physical host. I would have implemented suspend-on-shutdown (a la the rc script from libvirt 0.8.2), but lucid has an older libvirt that doesn't support 'virsh managedsave'. Shutting down domains gets us *a lot* of the way there, anyway. In fact, I run some largeish KVM hosts, and saving 30-60GB of memory images to disk before shutdown strikes me as less useful than shutting the domains down. sudo service stop libvirt-bin sudo cp libvirt-bin.conf /etc/init/ sudo kill -HUP 1 sudo service start libvirt-bin sudo cp omit-kvm-vm-pids /etc/init.d/ sudo update-rc.d omit-kvm-vm-pids defaults sudo cp -f sendsigs /etc/init.d/ # get fixed sendsigs from LP#639940 ** Attachment added: Stop libvirt VMs gracefully on system shutdown https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599109/+files/libvirt-bin.conf -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 350936] Re: Should shut down domains on system shutdown
** Attachment added: omit-kvm-vm-pids https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599117/+files/omit-kvm-vm-pids -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 350936] Re: Should shut down domains on system shutdown
@francesco, #46 The packaging is cleaner and easier with the rc script running before sendsigs (which is also an rc script). That way, the initscripts package/sendsigs doesn't need to carry around special behavior for libvirt-bin and any other packages that don't need this type of fix. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 350936] Re: Should shut down domains on system shutdown
Er, s/don't need/need/ -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 579596] Re: VNC console doesn't accept keyboard input during PXE boot
Upgrading to a new version of pxelinux fixes this. We had been running these: # lenny PXELINUX 3.71 Debian-2008-09-06 Copyright (C) 1994-2008 H. Peter Anvin # Ubuntu lucid PXELINUX 3.63 Debian-2008-07-15 3.86, from Debian squeeze/sid seems to have fixed this. PXELINUX 3.86 debian-20100418 Copyright (C) 1994-2010 H. Peter Anvin et al I looked over the syslinux Debian and upstream changelogs, but nothing jumps out at me. Our other hosts run KVM 85 or qemu-kvm 0.11.1+dfsg-1. They had been fine with pxelinux 3.63 or 3.71 (we PXE boot nearly all our new VMs for OS installation). FWIW, they also seem to be fine with 3.86. -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 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 579596] Re: VNC console doesn't accept keyboard input during PXE boot
** Bug watch added: Debian Bug tracker #582434 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582434 ** Also affects: qemu-kvm (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582434 Importance: Unknown Status: Unknown -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 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 579596] [NEW] VNC console doesn't accept keyboard input during PXE boot
Public bug reported: Binary package hint: qemu-kvm On lucid, I'm PXE booting a VM. Keyboard input on the VNC console works fine until PXELinux loads, so I can answer N to: Boot from (N)etwork or (Q)uit? N just fine, but once PXELinux loads, the VNC console ignores all keyboard input at the boot: prompt. No matter what keystrokes I hit, nothing happens on the VNC console. Input on PXELinux's *serial* console works fine. I can boot a target and keyboard input on the VNC console works fine when the target boots. What I type on the PXELinux serial console appears in the PXELinux VNC console. Interestingly, if I request a nonexistent boot target on the serial console, the VNC console starts accepting keyboard input. For example: r...@pxe-244:~# virsh console foo Connected to domain foo Escape character is ^] PXELINUX 3.63 Debian-2008-07-15 Copyright (C) 1994-2008 H. Peter Anvin boot: a Could not find kernel image: a boot: The VNC console now accepts keyboard input. I have kvm-pxe installed (obviously, since the VM *does* successfully load PXELinux). I'm not sure how to troubleshoot this further, or even if this is a bug in qemu-kvm proper; this is a strange failure mode. The libvirt domain XML for the VM I'm booting is below. It was created by a local tool, but using virt-manager(1) to create and PXE boot a VM exhibits the same behavior. domain type='kvm' namefoo/name uuidc80f27f4-cf2d-2125-9dd5-ca35855bdf42/uuid memory2097152/memory currentMemory2097152/currentMemory vcpu1/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='network'/ /os features acpi/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' source file='/var/lib/libvirt/images/foo.raw'/ target dev='vda' bus='virtio'/ /disk interface type='bridge' mac address='02:00:00:3d:7c:a5'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target port='0'/ /console input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'/ video model type='cirrus' vram='9216' heads='1'/ /video /devices /domain ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- VNC console doesn't accept keyboard input during PXE boot https://bugs.launchpad.net/bugs/579596 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 261274] [NEW] clustat(8) truncates columnar output when stdout is not a TTY
Public bug reported: Binary package hint: redhat-cluster-suite I originally discovered this bug in Ubuntu 8.04 LTS. I've also submitted this as: https://bugzilla.redhat.com/show_bug.cgi?id=460060 Description of problem: clustat(8) offers no way of obtaining untruncated columns when its stdout is not a TTY. As a result, it is impossible to obtain untruncated service names when calling clustat(8) from a script or any situation where its output is being parsed programmatically. Version-Release number of selected component (if applicable): Latest available in RHEL5. The cluster3 master branch at: http://sources.redhat.com/cluster/wiki/ also exhibits this behavior. How reproducible: Always. From rgmanager/src/utils/clustat.c: 34 int dimx = 80, dimy = 24, stdout_is_tty = 0; [...] 1103 if (isatty(STDOUT_FILENO)) { 1104 stdout_is_tty = 1; 1105 setupterm((char *) 0, STDOUT_FILENO, (int *) 0); 1106 dimx = tigetnum(cols); 1107 dimy = tigetnum(lines); 1108 } dimx is initialized to 80 columns. No code other than the above modifies dimx. Therefore, when the environment variable COLUMNS is set, its value is never honored when stdout is not going to a TTY. This causes the Service Name column to be truncated as though the output was being emitted on an 80-column terminal: Service Name Owner (Last) State --- - -- - service:cl01-svc01.roch.ny.exa (cl01-host01) disabled service:cl01-svc02.roch.ny.exa (cl01-host02) disabled service:cl01-svc03.roch.ny.exa cl01-host03started service:cl01-svc04.roch.ny.exa cl01-host04started Ideally, columnar data would *never* be truncated when output is not going to a TTY, so programmatic callers do not have to worry about setting COLUMNS. ** Affects: redhat-cluster-suite (Ubuntu) Importance: Undecided Status: New -- clustat(8) truncates columnar output when stdout is not a TTY https://bugs.launchpad.net/bugs/261274 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to redhat-cluster-suite 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