This bug was fixed in the package linux - 2.6.38-13.54
---
linux (2.6.38-13.54) natty-proposed; urgency=low
[Herton R. Krzesinski]
* Release Tracking Bug
- LP: #911195
[ Alex Bligh ]
* (config) Change Xen paravirt drivers to be built-in
- LP: #886521
[ Paolo Pisa
This bug was fixed in the package linux - 3.0.0-15.25
---
linux (3.0.0-15.25) oneiric-proposed; urgency=low
[Brad Figg]
* Release Tracking Bug
- LP: #910894
[ Upstream Kernel Changes ]
* Revert "clockevents: Set noop handler in clockevents_exchange_device()"
- LP: #
Upgraded a natty HVM installation to the proposed kernel and it was then
possible to use the pv drivers.
** Tags removed: verification-needed-natty
** Tags added: verification-done-natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/lucid-proposed/linux-lts-backport-natty
--
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 ma
This bug is awaiting verification that the kernel for Natty in -proposed
solves the problem (2.6.38-13.54). Please test the kernel and update
this bug with the results. If the problem is solved, change the tag
'verification-needed-natty' to 'verification-done-natty'.
If verification is not done by
** Branch linked: lp:ubuntu/oneiric-proposed/linux-ti-omap4
--
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 not
** Tags removed: verification-needed-oneiric
** Tags added: verification-done-oneiric
--
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
We checked on our end on cloud images, both downgrading precise to
3.0.0-15.24 and upgrading the release version of oneiric to 3.0.0-15.24
and it worked as expected.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
This bug is awaiting verification that the kernel for Oneiric in
-proposed solves the problem (3.0.0-15.24). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-oneiric' to 'verification-done-oneiric'.
If verification is not do
So it seems that type=ioemu is not only unnecessary, but also fails to
work with xm. Testing with
vif = [ 'mac=..., bridge=...']
was working with both stacks (xm or xl) and would default to the
emulated devices which could be forced to all emulated by changing the
xen_platform_pci to 0.
--
You
@Boris, no. But yes, it works. So emulated devices forceable through
guest config. Pv dvices only default by os unplugging andboth forcable
by os boot argument.
Btw, type=ioemu not working with unplugging seems to be limited to using
the xm stack. xl seems to work for me (now that gntdev is loaded
** Changed in: linux (Ubuntu Oneiric)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Natty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
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 Ubuntu.
** Description changed:
+ SRU justification:
+
+ Impact: Xen HVM guests (since around 2.6.36) will by default disable
+ (unplug) the emulated devices in favour of the paravirtualized drivers
+ when support for both is present (module or built-in). This would make
+ Xen installs more complicated (
Seems this would only be accepted with xl, while xm complains. And yes,
seems that xm works without gntdev loaded, but xl will fail to
initialize any xenbus (pv) devices when it is not loaded before starting
the instance... There has been a bug report about that. Cannot remember
whether it only was
Stefan
Attach is the config file for xen4. Normally I use the same config file
for pv and non pv guest, and let the gust pick what device driver it
want to use. Passing the disk as xvda will work with hvm guest with pv
and nonpv. The config file is used with xl command.
As side note if you don't
Stefan,
Yes, the unplug "feature" was added in Xen between 3.3 and 3.4 (the
magic port to support it), and it, um, somewhat lacks OS friendliness.
The config file to achieve desired results is also non-obvious. It
generates significant problems in moving VMs from Xen3 to Xen4, and also
upgrading d
Gihan/Diana: could you post a typical xen config file for xen4 that we
use, which works with both PV and non-PV OS's?
--
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_
I stripped the comments so it looks a bit simpler and smaller. And you
likely do not want the keymap line. ;)
** Attachment added: "My (working) config for precise"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/886521/+attachment/2614543/+files/hvm4-64.cfg
--
You received this bug not
So just generally trying to summarize my "issue" with Xen behaviour
here:
For the block device, no matter whether you have xvd? or hd? in the cfg,
there will be a pv and an emulated device. Depending on having the pci
platform driver and the pv driver built-in or as module, xen will remove
the emu
@Boris, not completely surprising but different from the behaviour for
the block device.
@Alex, Diana,
1. No I have no PPA, just compiled what is currently in the master-next branch
for natty and oneiric with the
config change applied.
2. The virtual net driver does *not* work with a device
Guys
If I am getting this correctly what Stefan is talking about the default
xen behaviour, net device emulation works bit differently than the disk
in xen. If you give the vif "type= ioemu" the host dom0 will not even
try to create a net_back device, and let qemu-dm to create qemu nic (
pretty m
RM_PCI should be "y" when building
3.1 kernel
To: bderzhav...@yahoo.com
Date: Wednesday, November 30, 2011, 12:11 PM
Alex, Diana, I think even with the built-in paravirt net and block
drivers there is still a problem which I think I saw on oneiric and
right now confirmed on natty. I think
Stefan,
We can test that (well Diana can :-) ). Some questions, as these bugs
tend to have near infinite combinatorial complexity:
1. Do you have a ppa or something with the kernel that you are using?
2. Are you saying the virtual net driver works if it is configured
type=iommu, or the net drive
Alex, Diana, I think even with the built-in paravirt net and block
drivers there is still a problem which I think I saw on oneiric and
right now confirmed on natty. I think it may still be unresolved even
upstream, but it was one issue I did not follow before oneiric release
as there where other pi
Diana has confirmed Maverick works ok too (albeit without pv drivers, as
expected). So this bug is solely Natty & Oneiric.
--
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_PLAT
Lucid runs fine (sounds like a testing error). We are testing Maverick
(which we think will work) and Natty (which we think won't) now.
--
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:
CO
Stefan: To be clear, we are talking about domU HVM with PV drivers.
In Precise, the HVM drivers are built in for all flavours. This is
logical because at least on domU installs which have an HVM backend (as
any cloud will), the PCI unplug mechanism will occur whether or not you
have PV driver modu
Also we changed block and netfrontend to be built in for precise. At
least Lucid I was booting in the past on a xen4 dom0 in HVM mode.
However usually using the emulated devices not the paravirtualized ones.
Traditionally we only had the paravirt drivers only built-in for the
virttual kernel packag
Andy: I have Diana Crisan our end figuring out what the problem is on
Lucid and/or Maverick.
--
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 bu
As this option is already removed in Precise (such that it is always
enabled) we can close this out as fixed there.
** Also affects: linux (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Medium
Status: Triaged
** Changed
I'll get the config we used that is giving us Lucid/Maverick problems
plus more details on what actually happens.
But at least we have Oneiric/Natty sorted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
> 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 P
Hmm. So we have xen configuration files set up for PV-on-HVM (in case
the guest OS can support it, as we have no way of knowing what the guest
OS is, as that's provided by the client), and our experience is that
Lucid does not install from the install CDs. Looking at the code, it
can't be the 'unpl
> 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.
https://bugs.launchpad.net/b
On Lucid (and I think Maverick), the CONFIG_XEN_PVHM and
CONFIG_XEN_PLATFORM_PCI settings are not defined, and indeed do not
exist in the code. However, Lucid (and I think Maverick) still do not
boot on Xen4 in HVM mode. I believe this is because these kernels behave
in the same way as later kernel
On Oneiric (and I think Natty), the problem is that CONFIG_XEN_PVHM is
defined as 'y' in the common config, but CONFIG_XEN_PLATFORM_PCI is
defined as 'm' in the common config. In various flavours,
CONFIG_XEN_NETDEV_FRONTEND and CONFIG_XEN_BLKDEV_FRONTEND are either
defined as 'm' or 'y'. However, t
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:
https://bug
So, in summary, for all pre-3.2 kernels in all flavours that have
CONFIG_XEN_PVHVM=y (i.e. the appropriate flavours in Lucid, Maverick, Natty,
Oneiric) we need to modify/add:
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_PLATFORM_PCI=y
For kernels without CONFIG_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 received
> 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),
(also, if we want to make sure install from DVD works, we should make
sure the install DVD kernel, which from memory is -generic, has
XEN_PVHVM=y and hence the other 3 options)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
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)? Whilst that would work, surely a less intrusive result would be
achieved by configuring CONFIG_XEN_PLATFORM_PCI=y
CONFI
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 XEN
I can confirm that no Ubuntu kernels (excepting some pre-Lucid) will
boot on Xen4 in HVM mode if dom0 is configured to allow PCI access (the
norm, and what you would want in case your guest OS's need it). What
happens is early on in the boot process, the pci unplug stuff is run,
resulting in /dev/s
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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 manag
Official commit for 3.2
commit 5fbdc10395cd500d6ff844825a918c4e6f38de37
Author: Stefano Stabellini
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 is
useless in any other cases.
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" whe
** Tags added: patch
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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 buildin
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 becaus
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
threads_per_co
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
+CON
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 s
** 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 m
> 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 k
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
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.
ht
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 that
** 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
(initram
** Package changed: ubuntu => linux (Ubuntu)
--
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 abou
60 matches
Mail list logo
