All,
While testing and configuring this VM host and the VM's, I let a host
update go through (on purpose) without shutting down the VM's and it had
_no_effect_ on the running VM's. The Console's went down but the VM's
remained operational and after the install I could restart the gui VMM
and see
All,
While testing and configuring this VM host and the VM's, I let a host
update go through (on purpose) without shutting down the VM's and it had
_no_effect_ on the running VM's. The Console's went down but the VM's
remained operational and after the install I could restart the gui VMM
and see
Serge and Leo,
We are using hardware RAID, no multipath.
We did not preserve any of host or VM syslog or bootlog entries from
that time. The messages.log shows a kernel restart at 12:31:16 on VM01.
We also have the postgres logs and they show a restart 2011-04-05
12:31:23 ...
database
See vm01 and vm02 virsh dumpxml - note that the configuration has been
changed due to performance testing and reconfig of the pinned cpu's to
reduce cross-chip task conflicts
** Attachment added: vm01_dumpxml
** Attachment added: vm02_dumpxml
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2088274/+files/vm02_dumpxml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Serge and Leo,
We are using hardware RAID, no multipath.
We did not preserve any of host or VM syslog or bootlog entries from
that time. The messages.log shows a kernel restart at 12:31:16 on VM01.
We also have the postgres logs and they show a restart 2011-04-05
12:31:23 ...
database
See vm01 and vm02 virsh dumpxml - note that the configuration has been
changed due to performance testing and reconfig of the pinned cpu's to
reduce cross-chip task conflicts
** Attachment added: vm01_dumpxml
** Attachment added: vm02_dumpxml
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2088274/+files/vm02_dumpxml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767218
Title:
Serge,
We'd have to go back a ways to get the logs you need. What kind of
oopses did you have in mind?
I think most of it is explained above, i.e.:
1) An update to some component of libvirt and/or kvm was part of an
update to the VM _host_.
2) Upon installing the update, the update process
** Attachment added: dpkg.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2082471/+files/dpkg.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
** Attachment added: term.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2082497/+files/term.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Serge,
We'd have to go back a ways to get the logs you need. What kind of
oopses did you have in mind?
I think most of it is explained above, i.e.:
1) An update to some component of libvirt and/or kvm was part of an
update to the VM _host_.
2) Upon installing the update, the update process
** Attachment added: dpkg.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2082471/+files/dpkg.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767218
** Attachment added: term.log.1.gz
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/767218/+attachment/2082497/+files/term.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767218
14 matches
Mail list logo
