[Bug 494141] Re: CUPS starts after SAMBA; printers are not available
Just to be clear, what is exactly the cups bug (other than not being an upstart job yet)? I don't know if upstart already have stanzas like "start before/after" (because it's clear that samba is not really dependent on cups, but if present cups should be started before samba), but it seems more easy to me for samba to say something like "start after cups" than cups keeping an updated list of services it should start before. -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 494141] Re: CUPS starts after SAMBA; printers are not available
Or maybe is a problem in cups not promptly giving a dynamic list of printers available runtime? Sorry, but there were no explanation and I was curious about this. :) -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 350936] Re: Should shut down domains on system shutdown
I'm not sure it can be done hacking upstart job. When libvirt was a sysvinit script in ubuntu 9.10, I used this [1] script adding it in "stop" function. In Lucid, if I add the same script to /etc/init /libvirt-bin.conf with the stanza: pre-stop exec shut-guests.sh 2>&1 > /var/log/shut-guests.log This works if I manually invoke a stop of libvirt-bin in a running system with: $ sudo stop libvirt-bin but **doesn't** work when issuing a reboot or halt. It seems there's an aggressive killing of all kvm processes **before** the pre-stop stanza is execute, and libvirt doesn't find any running guests when the shut- guests.sh is executed. it's not clear to me why and If this is an exptected behavior. For sure, kvm processes are detached from libvirt process branch. [1] http://www.linux-kvm.com/content/stop-script-running-vms-using-virsh -- 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
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 2>&1 >> /var/log/shut-guests.log
/sbin/initctl emit guests-shutted
just after "do_stop() {" in /etc/init.d/sendsings
*and* changing the line:
stop on (runlevel [!2345])
on file /etc/init/libvirt-bin.conf to:
stop on guests-shutted
Ugly but works, until libvirt/kvm/distributions crews will care more
about data integrity in vm guests during shutdown (sigh).
--
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
2010/5/5 Soren Hansen : > > It's important to remember that libvirt intentionally does not kill VM's > on termination. This enables us to upgrade libvirt without interruping > running VM's, so we want to only conditionally shut down VM's. Correct. > What I've > done on one of my Hardy boxes is to check $0 to see if the init script > was invoked as K??libvirt-bin. If so, I assume we're being shut down and > then I go and shut down the virtual machines. If invoked any other way, > it just stops libvirt, not the VM's. To achieve something similar with > upstart jobs, there's an environment variable that tells us why libvirt- > bin is being stopped. This will reveal whether it's being shut down as a > result of shutdown being called or whatnot. > But the problem is that the PIDs of the vm are not part of the libvirt-bin upstart job. Try to look my *ugly* workaround[1] : /etc/init.d/sendsings is just parallelizing killing any process not in upstart pool of tracked ones. So, when upstart shutdown libvirt-bin, almost for sure libvirt-bin won't find any active guests because they have been killed before by /etc/init.d/sendsing (killing those vm processes seems very quick). While this is good for libvirt-bin independence from kvm guests processes, this make fine grain control of guests shutdown harder, and one may wonder if it's not kvm itelsef that should send ACPI shutdown signal to guests, and not libvirt. I have another suspect: upstart may failing here. Doesn't libvirt-bin forks here to create kvm guests? Shouldn't "expect daemon" upstart stanza track daemons that fork more than once? If so, shouldn't libvirt- bin upstart job track these guests processes too? I have to ask in upstart mailing list. [1] https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/comments/8 -- 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 494141] Re: CUPS starts after SAMBA; printers are not available
2010/5/20 PryGuy : > I'm all sorry, this was a mistake. I'm really surprised an ordinary user > can change it. Sorry again. > (OT) Hehehe, actually Launchpad works better than others BTS because gives more freedom to users. If you did a mistake, don't worry but be more careful next time :) -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
2010/6/24 ossjunkie : > why does libvirt-bin still stop before the libvirt-shutdown-guests job has > finished the script? Because kvm guests processes aren't tracked by the upstart job and they are killed immediately by /etc/init.d/sendsings. This approach have pros (independence of libvirt from guests) and cons (this problem) so there's no easy fix. In my previous post [1] there's an ugly but safe workaround. If you want a definitive solution try to bug libvirt devs by pointing this exact problem (/etc/init.d/sendsings killing guests before libvirt-bin upstart job finishes). [1] https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/comments/8 -- 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
2010/6/24 Soren Hansen : >> why does libvirt-bin still stop before the libvirt-shutdown-guests job >> has finished the script? > > Good question. Upstart shouldn't be killing it, but something else > might. I can't imagine what, though. > I'm not sure Upstart isn't supposed to kill them. Let's suppose upstart is able to track all pids forked for livbvirt-bin job start (and it doesn't do so, even if the "expect daemon" stanza is used: this may be an upstart bug): there would be a pid for libvirt-bin and many pids for kvm guests. Suppose you want to kill the libvirt-bin job: how can you tell upstart to kill just libvirt-bin and not kvm guests? I don't think upstart jobs are so flexible. -- 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
I have seen the commit that implements this functionality and it's, as usual, a sysvinit script. Unfortunately, I think this is a use case where upstart can't do anything yet and the only solution (without moving back to a sysvinit script) is doing an ugly workaround in /etc/init.d/sendsigs. I've tried to subscribe Scott James Remnant (maintainer of upstart: thanks!): this is not a bug in upstart (maybe a feature lack) but I hope he have something to share with us about this problem. 2010/8/6 Sergey Svishchev <350...@bugs.launchpad.net>: > This is implemented in libvirt 0.8.2: > > https://bugzilla.redhat.com/show_bug.cgi?id=444273 > > ** Bug watch added: Red Hat Bugzilla #444273 > https://bugzilla.redhat.com/show_bug.cgi?id=444273 > > -- 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 494141] Re: CUPS starts after SAMBA; printers are not available (convert cups to upstart)
2010/9/17 Martin Pitt : > cups (1.4.4-5) unstable; urgency=low > > [ Martin Pitt ] > * ubuntu-upstart.dpatch: Drop the dependency "on starting smbd", it causes > samba to hang on package upgrades or manual restarts. There doesn't seem > to be a good way to express this dependency right now. (LP: #639768) Is Scott (maintainer of upstart) aware of this? -- CUPS starts after SAMBA; printers are not available (convert cups to upstart) https://bugs.launchpad.net/bugs/494141 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
2010/9/17 John Morrissey : > 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. > While I am beginning to hate upstart because of its deficiencies (#494141, #406397), I don't think adding a sysvinit script to fix an upstart job is the best workaround. Just handle pid omits in sendsigs as a special case for libvirt, as done for other problems. -- 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
Clap! :) 2010/9/29 Andy : > It is a dismal situation when at this point there is still no official simple > way from Canonical to > gracefully shutdown KVM VMs if the host has to go down for any reason such as > a UPS issued shutdown command. > -- 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
Don't think so. It's part of the independence of libvirt from the the actual virtualization technology (KVM, ...) to permit updates without shutdown of guests. 2010/11/4 Valentijn Sessink : > Hmm. If libvirt shuts down the virtual machines it monitors, then these > virtual machines will also be shut down when updating libvirt. > -- 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
[Bug 350936] Re: Should shut down domains on system shutdown
Is this fixed in ubuntu 10.04.3? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
I'm using libvirt-bin 0.7.5-5ubuntu25 and the bug is still there. Is the fix lost somewhere? My /var/log/libvirt/qemu/storage.log have these lines: usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied ... -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
Just to confirm something is still not working for me: $ sudo apt-cache showpkg libvirt-bin Package: libvirt-bin Versions: 0.7.5-5ubuntu25 Adding the generic (and unsafe) line: /dev/bus/usb/*/[0-9]* rw, to /etc/apparmor.d/abstractions/libvirt-qemu and reloading profiles works for me so it seems the mechanism to dynamically add host devices to the apparmor profile has been bounced as well or not working anymore. -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
I used virt-manager: storage 0175b337-5faf-42ba-d6a7-bb60ec8da4ad 1572864 1572864 1 hvm destroy restart restart /usr/bin/kvm libvirt-0175b337-5faf-42ba-d6a7-bb60ec8da4ad libvirt-0175b337-5faf-42ba-d6a7-bb60ec8da4ad -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
Yes, that worked! :) -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 494141] Re: CUPS starts after SAMBA; printers are not available
** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 494141] Re: CUPS starts after SAMBA; printers are not available
2 problems here: - cups is still an old sysvinit script; - samba is an upstart job but doesn't have any dependencies on cups. Moreover I think it's the samba upstart job that should assert "start after cups", and not cups to worry about starting before samba. So for sure this actually a deficiency in the samba upstart job. Not clear to me if it can be solved before cups becomes an upstart job too. If you want a temporary workaround, put a: sleep 10 just after "pre start script" in /etc/init/smbd.conf. Actually, I needed to put the same waiting time in /etc/init/nmbd.conf otherwise the master domain browser was nonfunctional, so it seems there are some dependencies nmbd <-> smbd (don't know the correct verse) unsatisfied. -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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
