Hey guys,
there is a anoying bug in libvirt-migrate-qemu-machinetype. It will
remove the vnc password from any changed xml. Reason: the script
triggers "virsh dumpxml", this command doesn't return the vnc password.
virsh should be able to also return the password with "virsh dumpxml
domain-id --s
I tried 3.2.0-27-generic and 3.11.0-18-generic from the precise repos.
Also a vanilla 3.10.18 and 3.10.28 based on the 3.2.0-27-generic config
file. I tried these ubuntu packages for qemu: saucy (1.5.0+dfsg-
3ubuntu5.3) and trusty (1.7.0+dfsg-3ubuntu5). Also the plain qemu from
http://wiki.qemu-p
Hi Serge,
You should be able to reproduce this with any iso from
http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.0/
Let me know if you need more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This happens also with vanilla kernel, so its more an qemu-kvm bug then
kernel related
** Package changed: linux (Ubuntu) => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746114
Tit
Tested this with vanilla Qemu 1.7.1 and 1.5. I have no issues with these
vanilla versions. the bug seems to be ubuntu related
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746114
Title:
FreeBSD free
Hi,
could anybody offer me some ideas for debugging. Or has anybody some
thoughts about this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746114
Title:
FreeBSD freeze during boot when runni
** Summary changed:
- FreeBSD freeze when running in Qemu KVM on AMD
+ FreeBSD freeze during boot when running in Qemu KVM on AMD and Intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746114
Title:
Forgot to mention:
I've tested this on two different CPUs:
model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
so this isn't only AMD related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hey Guys,
I ran into the same bug as Gijs Peskens did. My FreeBSD virtual
maschines are freezing at the boot menu if the beastie logo is enabled
and if I use a qemu version from saucy (1.5.0+dfsg-3ubuntu5.3) or trusty
(1.7.0+dfsg-3ubuntu5). Version 1.2.0+noroms-0ubuntu2.12.10.6 and 1.0
+noroms-0u
Dear Dave,
for Markus and me the oops was fixed in 3.5.0-18. I haven't seen your
"intel(0)..." messages on my test systems, where did you get them?
dmesg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Dear Christopher,
Daniel wrote to me in a personal email "usermodesetting was _never_ supported
on these machines. " (talking about Ivy Bridge chipsets).
As written by Markus in the initial post, we had an OOPS/Kernel Panic with the
i915 driver and the first official Ubuntu 12.10 driver (3.5.1
I talked to Daniel Vetter, he is responsible for the i915 driver and
works for Intel. He told me that this chipset series doesn't support the
parameter nomodeset. So this bug report can be closed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
My and Daniels email about this problem:
http://lists.freedesktop.org/archives/intel-
gfx/2012-November/022707.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle
FYI: the error is still present in the newest 3.7-rc6 mainline release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null); R
Hi,
my previous posts were not accurate enough, sorry for that. To clarify some
facts:
The Raring Kernel 3.7.0-0.5 and the newer one from last night 3.7.0-1.7 are as
buggy as the real quantal kernel. Their dmesg output is the same as mentioned
in my comment #42. Also as written in post #49, t
I justed tested several other raring Kernel:
3.6.4-030604-generic
3.6.6-030606-generic
3.7.0-030700rc1-generic
3.7.0-030700rc2-generic
3.7.0-030700rc3-generic
3.7.0-030700rc4-generic
they are all working, dmesg output looks like the one posted in #42
--
You received this bug notification becaus
** Attachment added: "dmesg 3.7.0-030700rc5 without nomodeset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+attachment/3431295/+files/dmesg_no_nomodeset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I tested the 3.7.0-030700rc5 #20120835 too,
looks like it works without the kernelparameter nomodeset:
[9.374325] [drm] Initialized drm 1.1.0 20060810
[9.429448] pci :00:00.0: Intel Ivybridge Chipset
[9.429524] pci :00:00.0: detected gtt size: 2097152K total, 262144K
mappa
@Joseph
I tested together with Markus 3.5.0-16.25 and several older ones, all
are working.
In 3.5.0-17.26 were some drm/i915 related things added.
Booting the 17.26 prints the following at boot:
* Starting load fallback graphics devices [fail]
the curious thing is
19 matches
Mail list logo
