Works for me. F31 KVM guest is installing on Q9550 box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
To manage notifications about
** Attachment added: "Check PPA [2} installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337555/+files/ppa2installed.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Log file for f31wks guest
** Attachment added: "Log file for f31wks guest"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337553/+files/fedora31wks.log
** Attachment removed: "PPA packages installed"
No luck when testing [2]. Reports are attached
** Attachment added: "PPA packages installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337552/+files/report.install.ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Verification new packages to be installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
To manage notifications about this bug go to:
Seems to work fine on i4790 (Haswell) box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
To manage notifications about this bug go to:
Penryn's architecture confirmed
** Attachment added: "/proc/cpuinfo file uploaded"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336211/+files/cpuinfo.penryn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done on Penryn's box
** Attachment added: "Requested reporting submitted"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336044/+files/Penryn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks a lot . I will do it at my earliest convenience this night.
Haswell i4770 is installed on small server 32 GB. Department's policy
doesn't allow me to test Ubuntu whichever release on bare metal. I
could test only on outdated CPU's box and it seems to be a core reason.
--
You received
I've got the same issue starting guest via virt-install even with serial
console.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
To
Reproduced via attempt to install KVM Guest F31 Server on Ubuntu 20.04
(bare metal)
** Attachment added: "/var/log/libvirt/qemu/fedora31.log - attempt to launch
F31 Server VM via Virt-manager on Ubuntu 20.04"
Public bug reported:
Description of problem:
On F22 Workstation
$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo dnf install redhat-rpm-config
$ cd tripleo-quickstart
$ export VIRTHOST=192.168.1.75
$ bash
Issue was escalated to Xen-devel mailing list. Libvirt-xen driver for nova has
not been tested with Neutron.
Details and xen-hotplug.log here
http://lists.xen.org/archives/html/xen-devel/2015-04/msg01856.html
--
You received this bug notification because you are a member of Ubuntu
Server
Issue was escalated to Xen-devel mailing list. Libvirt-xen driver for nova has
not been tested with Neutron.
Details and xen-hotplug.log here
http://lists.xen.org/archives/html/xen-devel/2015-04/msg01856.html
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Reproduced with same errors via devstack with nova.git already patched
per https://bugs.launchpad.net/nova/+bug/1425115. No manual intervention
from my side.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Reproduced with same errors via devstack with nova.git already patched
per https://bugs.launchpad.net/nova/+bug/1425115. No manual intervention
from my side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- nova can't scheduler instance with libvirt-xen driver
+ nova can't schedule instance with libvirt-xen driver
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Summary changed:
- nova can't scheduler instance with libvirt-xen driver
+ nova can't schedule instance with libvirt-xen driver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439645
Title:
Public bug reported:
This issue is closely related to bug
https://bugs.launchpad.net/nova/+bug/1425115.
Applying patch
$ git fetch https://review.openstack.org/openstack/nova
refs/changes/06/159106/5 git checkout FETCH_HEAD
in /opt/stack/nova
I was able to shutdown and restart system via
Public bug reported:
This issue is closely related to bug
https://bugs.launchpad.net/nova/+bug/1425115.
Applying patch
$ git fetch https://review.openstack.org/openstack/nova
refs/changes/06/159106/5 git checkout FETCH_HEAD
in /opt/stack/nova
I was able to shutdown and restart system via
/var/log/libvirt/libvirtd.log
root@ubuntu-wks:/var/log/libvirt# tail -f libvirtd.log
2015-04-02 10:02:35.124+: 4118: error : libxlVmStart:787 : internal error:
libxenlight failed to create new domain 'instance-0004'
2015-04-02 10:06:46.087+: 4117: error : libxlVmStart:787 : internal
/var/log/libvirt/libvirtd.log
root@ubuntu-wks:/var/log/libvirt# tail -f libvirtd.log
2015-04-02 10:02:35.124+: 4118: error : libxlVmStart:787 : internal error:
libxenlight failed to create new domain 'instance-0004'
2015-04-02 10:06:46.087+: 4117: error : libxlVmStart:787 : internal
Created link due to previous report:-
ln -s /usr/lib/xen-4.4/bin/pygrub /usr/bin/pygrub
/var/log/libvirt/libxl/instance-000d.log looks different , but
contains errors again.
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge online [-1] exited with
Created link due to previous report:-
ln -s /usr/lib/xen-4.4/bin/pygrub /usr/bin/pygrub
/var/log/libvirt/libxl/instance-000d.log looks different , but
contains errors again.
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge online [-1] exited with
Upload /var/log/libvirt/libxl/instance-000b.log
** Attachment added: Log file for VM failed to complete spawn
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1439645/+attachment/4364516/+files/instance-000b.log.gz
--
You received this bug notification because you are a member of
Upload /var/log/libvirt/libxl/instance-000b.log
** Attachment added: Log file for VM failed to complete spawn
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1439645/+attachment/4364516/+files/instance-000b.log.gz
--
You received this bug notification because you are a member of
Public bug reported:
Follow http://wiki.xen.org/wiki/OpenStack_via_DevStack
sudo apt-get install xen-hypervisor-4.4-amd64
sudo reboot
Get on Ubuntu 14.04.2 desktop
BUG : soft lockup - CPU#1 stuck for 23s!
on Ubuntu 14.04.2 Server
Kernel stack trace
** Affects: xen (Ubuntu)
Importance:
Public bug reported:
Follow http://wiki.xen.org/wiki/OpenStack_via_DevStack
sudo apt-get install xen-hypervisor-4.4-amd64
sudo reboot
Get on Ubuntu 14.04.2 desktop
BUG : soft lockup - CPU#1 stuck for 23s!
on Ubuntu 14.04.2 Server
Kernel stack trace
** Affects: xen (Ubuntu)
Importance:
Closed works on baremetal Ubuntu installs. My apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439167
Title:
Failure to install Xen 4.4 via native repos on Ubuntu 14.04.2
To manage
Closed works on baremetal Ubuntu installs. My apologies.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1439167
Title:
Failure to install Xen 4.4 via native repos on Ubuntu 14.04.2
Correct command is :-
$ iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
It keeps floating IPs 100% usable and security rules 100% effective
Command like :-
$ iptables -t nat -A POSTROUTING -s 172.24.4.0/24 -j MASQUERADE
disables floating IPs if 172.24.4.0/24 is devstack public network
Thank
Patch merged upstream https://review.openstack.org/#/c/163022/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426293
Title:
Devstack fails to load NovaDocker driver during stack.sh run on Ubuntu
Patch in git format
** Patch added: git.patch
https://bugs.launchpad.net/nova-docker/+bug/1426293/+attachment/4337374/+files/git.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426293
--- a/nova-docker/novadocker/virt/docker/vifs.py2015-03-07
17:32:24.118070981 +0300
+++ b/nova-docker/novadocker/virt/docker/vifs.py2015-03-07
17:35:36.698098732 +0300
@@ -248,6 +248,8 @@
run_as_root=True)
utils.execute('ip', 'netns',
Just finished testing my patch , it works fine. Am I supposed to submit
patch to upstream ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426293
Title:
Devstack fails to load NovaDocker driver
This patch allows to build Nova Docker driver with network enabled (
floating IPs are working)
** Patch added: dfw.patch
https://bugs.launchpad.net/ubuntu/+bug/1426293/+attachment/4337183/+files/dfw.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I would guess that in commit 9d06520645f28d96ef905a709f8ff0c27842b58b :-
- utils.execute('ip', 'netns', 'exec', container_id, 'ifconfig',
- if_remote_name, ip, run_as_root=True)
+ utils.execute('ip', 'netns', 'exec', container_id, 'ip', 'addr',
+ 'add', ip, 'dev', if_remote_name,
In meantime problem may be fixed as follows :-
Install working NovaDocker driver (with network alive, e.g. floating IPs) on
Ubuntu 14.04.2
via ./stack.sh
$ git clone http://github.com/stackforge/nova-docker.git
$ cd nova-docker
$ git revert 9d06520645f28d96ef905a709f8ff0c27842b58b
$ sudo pip
** Also affects: nova-docker
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426293
Title:
Devstack fails to load NovaDocker driver during stack.sh run on
Due to commit Sync oslo imports to be in line with Nova trunk
333656f4ad0e2c06f11eb8244bd6796110b9931d. (https://bugs.launchpad.net
/nova-docker/+bug/1425111)
In meantime Nova launch instance and starts container. Attempting
reproduce
Typo here, should be :-
I ping from 192.169.142.53 (host running stack.sh instance ) floating IP
192.168.10.154 ( private IP 50.0.0.13) . `tcpdump -vv -i eth0` is running
inside VM (192.168.10.154, 50.0.0.13)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
$ git clone https://git.openstack.org/openstack-dev/devstack
$ cd devstack
$ ./stack.sh
Tested on VMs (F21 KVM Hypervisor) 4 GB RAM , 2 VCPUs running stack.sh
instance with Ubuntu 14.04.2 (1).
My local.conf.
[[local|localrc]]
HOST_IP=192.169.142.52
Bug update :- On qbra7a715f5-02 ICMP replies from VM are already lost
** Description changed:
- $ git clone https://git.openstack.org/openstack-dev/devstack
- $ cd devstack
- $ ./stack.sh
+ $ git clone https://git.openstack.org/openstack-dev/devstack
+ $ cd devstack
+ $
Public bug reported:
The most recent versions ( approximately since 02/22/2015) of
.../stack/nova/openstack-common.conf doesn't contain entry
module=log
What causes stack.sh to crash with message
2015-02-24 10:07:05.567 | + service=n-cpu
2015-02-24 10:07:05.568 | + echo 'Error: Service
Tobias,
It's impossible to build usb redir enabled qemu version at Ubuntu because
package usb-redir
is NOT IN MAIN . I am fed up with Ubuntu struggling against spice and spice
server advantages.
I work only with Fedoras.
Take a look at
Public bug reported:
View build log :-
https://launchpadlibrarian.net/131270469/buildlog_ubuntu-raring-
amd64.qemu_1.3.0%2Bdfsg-5expubuntu3_UPLOADING.txt.gz
..
spice support yes (0.12.3/0.12.2)
rbd support yes
xfsctl supportyes
nss used no
usb net redir no
Now in my browser :-
..
spice support no (/)
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126390
Title:
The most recent qemu 1.3.0+dfsg-5expubuntu3 has usb redirection
disabled
What shoud I do to get usbredir 0.6-1 moved from universe to main in
13.04 Raring ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126390
Title:
The most recent qemu 1.3.0+dfsg-5expubuntu3 has usb
I believe if this page
https://launchpad.net/ubuntu/raring/+source/usbredir/0.6-1
would report main instead of universe problem will be resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Source package: usbredir-0.6-1
Availability: Currently in universe and in debian
Rationale: Many users want to benefit from qemu usb redirection like on Fedora
18,17
Security: no security history for the usbredir-0.6-1 (which the MIR is for)
QA: package works out of the
Public bug reported:
https://launchpadlibrarian.net/129880187/buildlog_ubuntu-quantal-
amd64.qemu_1.3.0%2Bdfsg-1~exp3ubuntu9_FAILEDTOBUILD.txt.gz
ERROR
ERROR: User requested feature spice
ERROR: configure was not able to find it
ERROR
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error:
Public bug reported:
Reason for upgrade is version qemu-kvm 1.2 ( or higher)
** Affects: qemu-kvm-spice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Serge,
I suspect this was meant to only affect the ubuntu qemu-kvm-spice (and
related) packages,
not upstream qemu, right?
I believe it's not a problem to verify.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@MikeB
Could you try PPA https://launchpad.net/~bderzhavets/+archive/lib-usbredir73
for spice/qxl W7 install. I just did it with no problems.
Qualification of bug as duplicate seems incorrect for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can start my Windows7 guest with both VGA and QXL drivers using KVM-
SPICE.
Clean install via
https://launchpad.net/~bderzhavets/+archive/lib-usbredir73 should not
have any KVM-SPICE. It installs QEMU_KVM 1.0 + USBREDIR ready to work with
SPICE 0.10.1
on clean Ubuntu Precise 64-bit.
If you made install as instructed, work just via /usr/bin/kvm. No dash
spice is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823494
Title:
Virt-manager upgrade 0.9.0 is not in sync with
However the packages from
https://launchpad.net/~bderzhavets/+archive/lib-usbredir73
don't remove the qemu-kvm-spice package
That's a core issue. Sorry, but clean instance 12.04 is required.
Otherwise, you are getting mess hardly predictable to behave.
--
You received this bug
@Mike,
Could you post :-
$ dpkg -l | grep spice
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823494
Title:
Virt-manager upgrade 0.9.0 is not in sync with libvirt
To manage notifications
Public bug reported:
In mean time download and dpkg-source
qemu-kvm_1.0+noroms.orig.tar.gz (4.7 MiB)
qemu-kvm_1.0+noroms-0ubuntu4.diff.gz (56.3 KiB)
qemu-kvm_1.0+noroms-0ubuntu4.dsc (2.2 KiB)
During 'debuild -rfakeroot -b -k45BD6814' generates an error :-
CC
View also https://launchpad.net/~bderzhavets/+archive/qemu-kvm-test/+packages
Build log :-
https://launchpadlibrarian.net/92518274/buildlog_ubuntu-precise-amd64
.qemu-kvm_1.0%2Bnoroms-0ubuntu5_FAILEDTOBUILD.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I believe libc6 2.14 works properly. You have upgraded from 2.13 up
to 2.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930181
Title:
qemu-kvm (1.0+noroms-0ubuntu4) fails to build on Ubuntu
Public bug reported:
Libusb bug #56 (affecting current release 1.0.8) seems to be fixed per
http://libusb.org/ticket/56.
View also http://ludovicrousseau.blogspot.com/2011/12/libusb-109-rc3.html
Libusb-1.0-0 (2:1.0.9~rc3-2) is accepted in Debian Unstable :-
Stefan,
Have you tried profile with following entries :-
vif = [ 'type=ioemu, mac=00:16:3f:03:01:14, bridge=virbr0 ' ]
...
xen_platform_pci=0
to load Precise HVM with emulated devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It looks like the netfront would take over as well but it is not set up.
This only works if in the config, the vif is not using type=ioemu.
Is it something surprising you ?
--- On Wed, 11/30/11, Stefan Bader stefan.ba...@canonical.com wrote:
From: Stefan Bader stefan.ba...@canonical.com
Is that what you would expect too Boris? (that's what happens on, e.g. Centos
5).
Yes.
However that's not what's happening
I never put xen_platform_pci=1( or 0) in Lucid HVM python profile.
Just used usual HVM-profile. It works for me and via virt-install as well.
I don't remember when
However, Lucid (and I think Maverick) still do not boot on Xen4 in HVM
mode
Ubuntu 10.04.3 does boot at Xen 4.1 Oneiric Dom0 in HVM mode ( not PV-
on-HVM)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Boris, are you suggesting the for pre-3.2 kernels, the fix is to backport the
3.2 fix (i.e commit
5fbdc10395cd500d6ff844825a918c4e6f38de37, remove XEN_PLATFORM_PCI config
option)?
No , I am not suggesting this back port.
XEN_PLATFORM_PCI should be equal y for Oneiric kernels (3.0.X),
Sorry, check 3.1.1 kernel on Oneiric :-
boris@boris-System-P5Q3:/boot$ cat config-3.1.1-030101-generic | grep
XEN_BLKDEV_FRONTEND
CONFIG_XEN_BLKDEV_FRONTEND=m
boris@boris-System-P5Q3:/boot$ cat config-3.1.1-030101-generic | grep
XEN_NETDEV_FRONTEND
CONFIG_XEN_NETDEV_FRONTEND=m
--
You
That's correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886521
Title:
CONFIG_XEN_PLATFORM_PCI should be y when building 3.1 kernel
To manage notifications about this bug go to:
Daily build of precise (11/25/11) is already running 3.2 kernel. Bug
seems to be fixed upstream.
boris@ubuntu1204:~$ uname -a
Linux ubuntu1204 3.2.0-1-generic #3-Ubuntu SMP Tue Nov 22 11:30:27 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
boris@ubuntu1204:~$ cat /boot/config-3.2.0-1-generic | grep
Public bug reported:
It comes with a new URI alias feature, which will be particularly useful for
users of tools like virsh and virt-install.
In the same way that SSH allows you to setup hostname aliases in
$HOME/.ssh/config, libvirt will now allow you to setup URI aliases in
Public bug reported:
It comes with a new URI alias feature, which will be particularly useful for
users of tools like virsh and virt-install.
In the same way that SSH allows you to setup hostname aliases in
$HOME/.ssh/config, libvirt will now allow you to setup URI aliases in
Experimental build libvirt 0.9.7
via git://anonscm.debian.org/pkg-libvirt/libvirt.git
tip commit e49612bea22c681aff95c974d36d009a5ae08a21
for Precise seems to fix the bug.
VirtManager behaves tolerant regarding domain shuts down ( up to 7 )
Limited testing has been done on daily
Yes, same solution on F16. I just had to rebuild
libvirt-0.9.7-1.fc14.src.rpm and get libvirt-0.9.7-1.fc16.src.rpm
to upgrade libvirt up to 0.9.7. Afterwards everything goes fine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Experimental build libvirt 0.9.7
via git://anonscm.debian.org/pkg-libvirt/libvirt.git
tip commit e49612bea22c681aff95c974d36d009a5ae08a21
for Oneiric, seems to fix bug Oneiric with 3.1.0-030100-generic.
Experimental build 0.9.7 for Precise currently is awaiting publishing
and will be
Experimental build libvirt 0.9.7
via git://anonscm.debian.org/pkg-libvirt/libvirt.git
tip commit e49612bea22c681aff95c974d36d009a5ae08a21
for Precise seems to fix the bug.
VirtManager behaves tolerant regarding domain shuts down ( up to 7 )
Limited testing has been done on daily
Yes, same solution on F16. I just had to rebuild
libvirt-0.9.7-1.fc14.src.rpm and get libvirt-0.9.7-1.fc16.src.rpm
to upgrade libvirt up to 0.9.7. Afterwards everything goes fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Tested on Daily build for Precise (11/10/2011)
VNC ( and Spice) session initiated via Virt-Manager 0.9.0 ( Libvirt
0.9.6) after domain shutdown :-
Error polling connection 'qemu:///system': Unable to read from monitor:
Connection reset by peer
Traceback (most recent
** Description changed:
Tested on Daily build for Precise (11/10/2011)
VNC ( and Spice) session initiated via Virt-Manager 0.9.0 ( Libvirt
0.9.6) after domain shutdown :-
- Error polling connection 'qemu:///system': Unable to read from monitor:
+ Error polling connection
Public bug reported:
Tested on Daily build for Precise (11/10/2011)
VNC ( and Spice) session initiated via Virt-Manager 0.9.0 ( Libvirt
0.9.6) after domain shutdown :-
Error polling connection 'qemu:///system': Unable to read from monitor:
Connection reset by peer
Traceback (most recent
** Description changed:
Tested on Daily build for Precise (11/10/2011)
VNC ( and Spice) session initiated via Virt-Manager 0.9.0 ( Libvirt
0.9.6) after domain shutdown :-
- Error polling connection 'qemu:///system': Unable to read from monitor:
+ Error polling connection
I pointed to the most recent PPAs.
The first one is :-
Building Spice-Gtk-0.7 via Debian Unstable with Gobject-introspection enabled
as of 08/20/11
https://launchpad.net/~bderzhavets/+archive/test-deb2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Just hard to remind, done a while ago.
Please, view bug ( fixed )
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494
It is resolves issue, which was connected to seabios, not to libvirt.
We have Libvirt 0.9.6 back ported to Oneiric and my build of Libvirt 0.9.6 on
Oneiric ,
** Changed in: libvirt (Ubuntu)
Status: Fix Released = Fix Committed
--
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/794470
Title:
Rebuild spice-gtk-0.6 on Oneiric
To manage
Official commit for 3.2
commit 5fbdc10395cd500d6ff844825a918c4e6f38de37
Author: Stefano Stabellini stefano.stabell...@eu.citrix.com
Date: Thu Sep 29 12:05:58 2011 +0100
xen: remove XEN_PLATFORM_PCI config option
Xen PVHVM needs xen-platform-pci, on the other hand xen-platform-pci
Issue closed in PPAs :-
Qemu-kvm 0.15.1 Spice USB Redirection support for Ubuntu Oneiric
https://launchpad.net/~bderzhavets/+archive/0151-usbredir
QemuSpice USB Redirection with back ported Libvirt 0.9.6 , new seabios 1.6.3
for Ubuntu Oneiric
I pointed to the most recent PPAs.
The first one is :-
Building Spice-Gtk-0.7 via Debian Unstable with Gobject-introspection enabled
as of 08/20/11
https://launchpad.net/~bderzhavets/+archive/test-deb2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just hard to remind, done a while ago.
Please, view bug ( fixed )
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/823494
It is resolves issue, which was connected to seabios, not to libvirt.
We have Libvirt 0.9.6 back ported to Oneiric and my build of Libvirt 0.9.6 on
Oneiric ,
** Changed in: libvirt (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794470
Title:
Rebuild spice-gtk-0.6 on Oneiric
To manage notifications
One more suggestion - please, include xen-blkfront, xen-netfront drivers
into initrd.img on ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886521
Title:
CONFIG_XEN_PLATFORM_PCI should be y when
Reproduced in Dom0
host : boris-System-P5Q3
release: 3.0.0-12-generic
version: #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011
machine: x86_64
nr_cpus: 4
nr_nodes : 1
cores_per_socket : 4
I believe, that patch above has to be applied to .config of any mainstream
kernel starting
with 3.0 , e.g 3.1,3.2. Otherwise , such feature as Ubuntu PVHVM DomUs will be
available
only for customers responsible for kernel rebuild in Ubuntu's style.
--
You received this bug notification
Changes done to kernel been rebuilt .
--- xenconf.3.1.0-030100-generic2011-11-06 11:03:39.225828270 +0400
+++ xenconf.3.1.0-2-vnc 2011-11-06 11:04:58.621827223 +0400
@@ -16,19 +16,20 @@
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
CONFIG_XEN_WDT=m
-CONFIG_XEN_FBDEV_FRONTEND=m
Public bug reported:
It allows to load PVHVM domain having xen_platform_pci=1 in python hvm-profile.
Also xen-blkfront and xen-netfront drivers are not included into inird.img on
ISO disk,
what requires :-
(initramfs) modprobe xen-blkfront
(initramfs) modprobe xen-netfront
(initramfs) exit
to
** Description changed:
It allows to load PVHVM domain having xen_platform_pci=1 in python
hvm-profile.
Also xen-blkfront and xen-netfront drivers are not included into inird.img on
ISO disk,
- what requires :-
+ what requires (at first boot) :-
(initramfs) modprobe xen-blkfront
root@boris-System-P5Q3:~# uname -a
Linux boris-System-P5Q3 3.1.0-030100-generic #201110241006 SMP Mon Oct 24
14:07:10 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Yes , i am running 3.1 Ubuntu's kernel for Dom0. I also believe that's a
trivial issue and kernel developer have
nothing to do with
apport-collect 886521 has been run on Xen Host where I tested Oneiric
with Ubuntu's 3.1 kernel as PV-on-HVM domain
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have noted that there is a newer version of the development kernel than
the
one you last tested when this
issue was found.
Please test again with the newer kernel and indicate in the bug if this issue
still exists or not.
I did all testing with the the most recent 3.1 Ubuntu's kernel
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886521
Title:
CONFIG_XEN_PLATFORM_PCI should be y when building 3.1 kernel
To
View also config-3.1.0-7.fc16.x86_64
** Attachment added: Fedora 16 kernel config file
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886521/+attachment/2586502/+files/config-3.1.0-7.fc16.x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 388 matches
Mail list logo
