If you're experiencing this problem, could you please attach
/proc/cpuinfo ?
Thanks,
:-Dustin
** Summary changed:
- Certain VMs do not run under KVM using 2.6.30-rc5 kernel
+ Certain VMs do not run under KVM using karmic's kernel
--
Certain VMs do not run under KVM using karmic's kernel
https:
I can reproduce this. My windows 7 VM will only boot to where it says
"Starting Windows". The animation that usually appears above it does not
and one of the two VCPUs pegs out.
If I set my emulator in the XML configuration to a shell script of:
exec /usr/bin/kvm -cpu qemu32 "$@"
Then the VM sta
Can anyone reproduce this on an up-to-date karmic system, running qemu-
kvm-0.11?
:-Dustin
** Package changed: kvm (Ubuntu) => qemu-kvm (Ubuntu)
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.laun
Confirmed on linux-image-2.6.31-9-generic with kvm=1:84+dfsg-0ubuntu16 +
libvirt-bin=0.7.0-1ubuntu3 on karmic.
WinXP would run through the install but not boot after the reboot.
Same with Win7
Then running Win7 from the command line with '-cpu qemu32' allowed it to
boot.
--
Certain VMs do not
Confirming this on Kernel 2.6.28-15-generic #49-Ubuntu SMP/KVM 0.9.1
VMs running OpenSolaris 9, FreeBSD 7.2 and Windows XP SP2 all hand with
the following from dmesg...
[135369.886301] kvm: 26463: cpu0 unhandled wrmsr: 0xc0010117 data 0
[135369.896799] kvm: 26463: cpu0 unhandled rdmsr: 0xc0010117
Just confirming that I have the problem on 9.04, 2.6.28-13-generic -
2.6.28-11-generic works fine. I was hoping the KVM update that just got
pushed fixed the problem, but no go.
There is also a bug posted on Red Hat's Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=510695
** Bug watch add
I can confirm the problem exists with the latest Karmic kernel:
ml...@mlund-kubuntu:~$ uname -a
Linux mlund-kubuntu 2.6.31-3-generic #19-Ubuntu SMP Tue Jul 14 16:04:41 UTC
2009 i686 GNU/Linux
Running the VM with Qemu and kqemu enabled works fine, but it is a lot
slower (of course)
--
Certain V
Host: Ubuntu Jaunty with kernel 2.6.30-020630-generic
KVM: 84+dfsg-0ubuntu12
Adding -cpu qemu32 made kvm work well.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Bugs, which
Adding -cpu core2duo,-nx made my karmic image boot again. Same for -cpu
qemu64,-nx. But without the -nx, it doesn't boot.
I'm on jaunty with 2.6.28-13-generic.
Bug #396219 is related, if not duplicated.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/
@Iggy:
the options "-cpu qemu64,-nx" got my windows bootet again, but it restarts all
of a sudden.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Between the lines; I can conform as as well:
2.6.28-11-generic is OK
2.6.28-13-generic VM (Windows XP with SP3) is not working.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
I've tried to upgrade kvm from 84 to 87, but it did not work.
Host: Ubuntu Jaunty with kernel 2.6.30-020630-generic
KVM: 87
/usr/local/kvm/bin/qemu-system-x86_64 -S -M pc -m 384 -smp 1 -name xp
-uuid 24101b4d-dd28-45c5-3934-b790fc0eef4a -monitor pty -pidfile
/var/run/libvirt/qemu//xp.pid -localti
Ubuntu Karmic's kernel is now on 2.6.31-2.15.
Can anyone reproduce this problem on a 2.6.31 kernel?
:-Dustin
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
libvirt's suggestion to get custom command line parameters i to use a
wrapper script that calls kvm + your options + all options passed to it
and set that as your executable. Why they don't allow adding options, I
don't know. That's your best bet. Running it like you did will never
work because lib
I ran
t...@rad4-x300:~$ sudo kvm -S -M pc -m 512 -smp 1 -name x300-alfresco
-uuid a43c32e7-f0d5-bbb4-3784-d55fe13027da -monitor pty -pidfile
/var/run/libvirt/qemu//x300-alfresco.pid -boot c -drive
file=/home/tomg/VMs/x300-alfresco,if=ide,index=0,boot=on -drive
file=,if=ide,media=cdrom,index=2 -net
For people with this issue, does using "-cpu qemu64,-nx" on your kvm
command line help?
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have a same problem. Windows XP guest os can not be accessed with vnc.
Host: Ubuntu Jaunty with kernel 2.6.30-020630-generic
KVM: 84+dfsg-0ubuntu12
/usr/bin/kvm -S -M pc -m 384 -smp 1 -name xp -uuid 24101b4d-
dd28-45c5-3934-b790fc0eef4a -monitor pty -pidfile
/var/run/libvirt/qemu//xp.pid -local
Same problem here. Fresh Jaunty images built with ubuntu-vm-builder
moments ago are hanging over after "Starting up ...". Hardy images work
fine.
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are
I have the same problem: after today's upgrade to kernel 2.6.28-13, my
virtual machines with default Jaunty installation stopped working, they
hang after displaying grub devices and 'Starting up', spinning the CPU.
This is my KVM start command:
gksudo -- kvm -hda mname/kvm.img -m 512 -net nic -n
I have the same problem but booting all my Ubuntu VMs which are running
Hardy. I was using Jaunty with the server kernel (to get access to full
4GB memory) originally and upgraded to 2.6.30 generic kernel to fix my
Intel Graphics issues. After this all my KVMs will not boot fully. It
does the PO
I have also had a similar problem. Booting Windows XP worked fine this
morning until I received an auto-update that included a new kernel.
When I boot 2.6.28-13-generic, it fails. When I boot 2.6.28-11-generic,
it works fine.
When it fails: The bios screen shows. I can get into the windows boot
Just to add another data point: My Windows XP kvm guest stopped working
after a kernel upgrade this morning. With 2.6.28-13-generic Windows does
not work, booting into 2.6.28-11-generic repairs that issue.
Volker
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.
I am using 'Virtual Machine Manager' / libvirt.
My kvm command line is as follows:
b...@gecko2:~$ ps -wwfp $(pgrep -d, -x kvm)
UIDPID PPID C STIME TTY TIME CMD
bob 26562 1 91 19:38 ?00:01:30 /usr/bin/kvm -S -M pc -m 384
-smp 1 -name WindowsXP -uuid c4de242a-13
I'm marking this confirmed, as several users have confirmed this issue
(though I haven't myself).
I also added a linux kernel task for this, as the issue looks to be
there.
To the reporters: can you please paste your kvm command line as reported
by "pgrep kvm" ?
:-Dustin
** Also affects: linux
I can confirm that my Windows XP, Windows 7 RC and OpenSolaris 08.11
virtual machines all fail to boot under KVM with kernel 2.6.30.
I first encountered this problem when I switched from the stock Jaunty
2.6.28 kernel to 2.6.30-rc5. This comment is just to confirm that the
problem persists with t
I should point out that all the Win XP VMs functioned without issues on
2.6.28 (the default Jaunty 32bit kernel).
--
Certain VMs do not run under KVM using 2.6.30-rc5 kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm also experiencing a similar (possible the same) KVM problem on
Jaunty with various Win XP virtual machines, with kernel
2.6.30-020630-generic #020630 SMP. Running VMs via virt-manager, it
appears that the Windows VMs actually boot, but the VNC screen remains
blank/black. The screen goes blank r
Sorry, I meant OpenSolaris 08.11 (not 09.11) above.
(Actually, on further testing it appears that my OpenSolaris VM is not
booting all the way under 2.6.28-10 either, but it certainly gets much
further than it does using the newer kernel.)
--
Certain VMs do not run under KVM using 2.6.30-rc5 ker
28 matches
Mail list logo
