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:
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 valent...@sessink.nl:
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual
Clap! :)
2010/9/29 Andy a...@xillean.com:
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
2010/9/17 Martin Pitt martin.p...@ubuntu.com:
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
2010/9/17 John Morrissey j...@horde.net:
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
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
2010/6/24 Soren Hansen so...@ubuntu.com:
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.
2010/5/20 PryGuy p...@inbox.ru:
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
2010/5/5 Soren Hansen so...@ubuntu.com:
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
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 21 /var/log/shut-guests.log
This
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 21 /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
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
** 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.
--
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
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
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
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
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
I used virt-manager:
domain type='kvm' id='5'
namestorage/name
uuid0175b337-5faf-42ba-d6a7-bb60ec8da4ad/uuid
memory1572864/memory
currentMemory1572864/currentMemory
vcpu1/vcpu
os
type arch='x86_64' machine='pc-0.12'hvm/type
boot dev='hd'/
/os
features
acpi/
apic/
19 matches
Mail list logo
