Thanks for the Detail Robin!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in QEMU:
Invalid
Status in
TL;DR: pass '-vga none' with -nographic, or redirect the screen
somewhere!
I ended up digging into this after it was mentioned by smoser. The bug
is invalid because of a bad assumption in the QEMU inputs. smoser's
workaround of usb=off removes USB as a workaround.
The kernel, OpenFirmware, and
As noted, Xenial kernel is not supporting POWER7 cpu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
** Changed in: qemu
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in
Build target was changed to P8 starting with Xenial. Previously it had
been a P7 target. I would expect Xenial kernel to have problems booting
on a P7 model. IMO this kernel bug is invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I should also mention that the original command used will work if we
specify which cpu type to use:
qemu-system-ppc64 -m 256 \
-cpu POWER8 \
-display none -nographic \
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 \
-machine pseries \
-drive
Here's an update.
The Xenial kernel doesn;t like the emulated POWER7 cpu that the command
line being used generates by default.
processor : 0
cpu : POWER7 (raw), altivec supported
clock : 1000.00MHz
revision: 2.3 (pvr 003f 0203)
timebase:
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
@leftyfb - what exactly is IBM asking to verify? Whether kvm works
under powervm? Did smoser's info help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
ok. so after playing some, this all comes down to needing 'usb=off' on
the qemu command line.
works:
qemu-system-ppc64 -enable-kvm -machine usb=off -device
virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive
if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive
Note, that Michael Roth's comments are probably valid. I suspect that
if leftyfb ever saw this working on powerVM host, then it was through
the kvm_pr module. In my experience, that works generally pretty well
(buit my testing has only ever been done powerNV host).
--
You received this bug
I have also shown that this issue has the exact same results on PowerNV
above.
** Changed in: qemu
Status: Invalid => Confirmed
** Changed in: qemu (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
PowerVM mode is an LPAR. It is not a kvm instance trying to run an KVM
within. This was also working in 14.04 without issue and is being asked
of us from IBM to certify
2. the xenial cloud images
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in QEMU:
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv. A workaround is to use the isos which do
The PowerVM machine I've been using for these tests has the following
output:
ubuntu@alpine01:~/kvm$ cat /proc/cpuinfo | grep platform
platform: pSeries
The PowerNV server has the following output:
ubuntu@binacle:~$ cat /etc/issue; uname -a ; ppc64_cpu --smt ; cat
/proc/cpuinfo |grep
Sorry, I copied the wrong thing:
sudo qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=seed.iso,if=virtio
@mdroth
I don't think PPC supports kvm the same way as x86:
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -m 256 -display none
-nographic -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive
@serge-hallyn
ubuntu@alpine01:~/kvm$ cat /etc/issue; uname -a ; ppc64_cpu --smt
Ubuntu Xenial Xerus (development branch) \n \l
Linux alpine01 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256
If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know. Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.
--
You received this bug notification because you are a member of Kernel
Packages,
ubuntu@alpine01:~$ sudo ppc64_cpu --smt=1
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1 2 3 4 5 6 7
Core 1:8*9101112131415
Core 2: 16* 17181920212223
Core 3: 24* 25262728
4.4.0-16 also works.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64
Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I
can boot the installed image (with same kernel) just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1*2*3*4*5*6*7*
Core 1:8*9* 10* 11* 12* 13* 14* 15*
Core 2: 16* 17* 18* 19* 20* 21* 22* 23*
Core 3: 24* 25* 26* 27* 28* 29* 30* 31*
Core 4: 32* 33*
Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=my-seed.img,if=virtio
** Attachment added: "crash.png"
Hm - I can boot a wily cloud image, just not a xenial one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
27 matches
Mail list logo
