This is equivalent to 1844421
** 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/1845033
Title:
xenbus: Avoid deadlock during suspend
Note - this has also been backported to 4.11 RC2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844421
Title:
Linux VM deadlock during migration
To manage notifications about this bug go to:
https:
Public bug reported:
The following program will cause a Linux VM running under Xen to
deadlock if a suspend/migrate is attempted:
-
import pyxs.client
import time
c = pyxs.client.Client(xen_bus_path="/dev/xen/xenbus")
c.connect()
c.transaction()
while True:
time.sleep(1000)
-
When
My apologies for the previous comment - I was looking at the tags which
were broken, not which are fixed. Only 5.2 and later are fixed
(https://github.com/torvalds/linux/commit/d10e0cc113c9e1b64b5c6e3db37b5c839794f3df)
Regarding the auto commenter, as this is a backport request for an issue
that w
This is the behaviour for me as well - if I use anything other than the
web app the computer seems stable, but the computer is unresponsive a
few seconds after I open the Amazon web app.
SSH still works, but killing the webapp does not bring the computer back
under control and I have not found a w
Possibly a duplicate of https://bugs.launchpad.net/nouveau/+bug/1309044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313077
Title:
computer HANGS COMPLETLY when y try to enter to amazon lens
To m
We've identified a workaround that can get the VM uuid:
root@ubuntulucidlynx1004:~# xenstore-read domid
2
root@ubuntulucidlynx1004:~# xenstore-read /local/domain/2/vm
/vm/6fddd486-b376-647d-d7d4-9acf0e164722
It is the /vm/ path which has the incorrect permissions, however
the UUID is in /local/do
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/ v3-3-precise boots
but v3-2-39-precise does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clippe
3.3 and 3.4 both boot... Am trying some earlier kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifications about this bug
Unfortunately -rc1, -rc2 and -rc3 all boot on my machine... Sorry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifications abou
And the xen dmesg
** Attachment added: "working_xen_dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/470/+attachment/3534589/+files/working_xen_dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Okay - I wasn't sure that it was so clear! I thought there was a plan to
backport the quantal kernel to precise as the LTS, but anyway!
See attached for the xen dmesg and host dmesg from a successful boot
with original Xen and quantal kernel.
** Attachment added: "working_dmesg.log"
https://b
We've already identified that a quantal development kernel (linux-
image-3.5.0-22-generic) works with no dom0_mem option, so I imagine that
the latest kernel would also work - is there a particular version that
you'd like me to try?
If xen upstream thinks the kernel should be fixed, then is questi
I can confirm it's bootable with the patch.
Many thanks Stefan, and sorry for the delay in responding to the last
message!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Precise kerne
Interesting bit of the normal dmesg boot looks to be:
[0.00] mtrr_cleanup: can not find optimal value
[0.00] please specify mtrr_gran_size/mtrr_chunk_size
[0.00] e820: update [mem 0xcf70-0x] usable ==> reserved
[0.00] e820: update [mem 0x22800-0x22bf
Do you want me to try the above "hack" as a patch to confirm that it
works? I wasn't sure from the comments if this is a proposed fix or
not!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Tit
Correction from previous (now hidden) comment - sorry, pasted wrong log.
Added the arguments requested by Konrad. If there are other kernels
you'd like us to try to pinpoint which kernel introduced the issue,
please let me know.
(XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.5) (stefan.ba...@cano
Added the arguments requested by Konrad. If there are other kernels
you'd like us to try to pinpoint which kernel introduced the issue,
please let me know.
(XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.5) (stefan.ba...@canonical.com)
(gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Tue Jan
I know that 3.5.0-36 is a dev kernel - I followed
http://packages.qa.ubuntu.com/qatracker/milestones/223/builds/25321/downloads
to test it just to try and debug where the issue was.
Very curiously setting an explicit dom0 memory does allow the machine to
boot - that was a surprise to me!
I don't
I've updated to clarify it was kernel 3.2.0-36 which is failing (sorry -
I tried to set this as the package but it switched to the source package
and therefore lost the version information). A colleague reports that
3.2.0-15 is successful
** Description changed:
- Precise kernel is not bootable,
** Description changed:
- Precise kernel 3.2.0-36 is not bootable (Note that 3.2.0-15 was
- bootable), however upgrading to Oneiric kernel (linux-
- image-3.5.0-22-generic) resovles the issue. Serial output from Precise
- kernel is:
+ Precise kernel is not bootable, however upgrading to Quantal k
Set to confirmed as per automated instructions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Precise kernel not bootable under Xen - alloc_l1_table
To manage notifications about this
Cannot generate log files since the server does not boot.
** Description changed:
- Precise kernel is not bootable, however upgrading to Oneiric kernel
- (linux-image-3.5.0-22-generic) resovles the issue. Serial output from
- Precise kernel is:
+ Precise kernel 3.2.0-36 is not bootable (Note tha
Public bug reported:
Precise kernel is not bootable, however upgrading to Oneiric kernel
(linux-image-3.5.0-22-generic) resovles the issue. Serial output from
Precise kernel is:
(XEN) Xen version 4.1.2 (Ubuntu 4.1.2-2ubuntu2.5) (stefan.ba...@canonical.com)
(gcc version 4.6.3 (Ubuntu/Linaro 4.6.
We suspect it may be a permissions bug in the way xenstore is set up by
XAPI.
# list_domains
id | uuid | state
5 | 0dae370c-753d-5ef0-e3e0-e3a5e93d6203 |B
# xenstore-ls -fp | grep /vm/0dae370c-753d-5ef0-e3e0-e3a5e93d6203/uuid
/vm/0dae370c-753d-5ef0-e3e0-e3
25 matches
Mail list logo
