qemu-system-ppc with rhel-server-6.6-ppc64-dvd.iso
by Gary Gatling
Has anyone been able to emulate a PPC system to run RHEL 6 in qemu? I had a
build for epel 6 that was failing on ppc64. (It does work on epel 7 ppc
however)
I was hoping to figure out what is wrong by taking a closer look via ppc
emulation and running rpmbuild within it.
But when I try to install it on a fedora 21 laptop I get
qemu-system-ppc -boot d -cdrom rhel-server-6.6-ppc64-dvd.iso -m 1024 -hda
ppcdisk.img
http://i.imgur.com/qDm2m0t.png
Maybe some other distro would work better for this then fedora 21? Or is
there something I have to type at openboot prompt to get the installer
started?
I can run
qemu-system-ppc -boot d -cdrom rhel-server-6.6-ppc64-dvd.iso -m 1024 -hda
ppcdisk.img -prom-env 'auto-boot?=false'
and then I can do a "dir" on the dvd iso. I just can't seem to boot it.
I was able to boot a ubuntu ppc mini.iso. Just not RHEL 6 ppc iso.
Thanks for any ideas anyone has.
7 years, 9 months
Cannot disconnect CD if cdrom is boot device
by Andrew Ruch
Hello,
I recently upgraded from Fedora 20 to Fedora 22. I'm running
libvirt-1.2.13.1-1.fc22.x86_64 and virt-manager-1.2.0-1.fc22.noarch.
I'm no longer able to disconnect a CD from the CDROM device if the
device is enabled as a boot device. I'm using virt-manager to manage
the guests.
This is my workflow. I have a RHEL 6 installer with a custom
kickstart. I install the guest using the my custom RHEL ISO, meaning
the CDROM is enabled as a boot device. During the post phase of the
kickstart, the RHEL ISO is ejected and a custom configuration ISO is
inserted to finish the custom part of the installation. This used to
work in Fedora 20. I now get the following error:
unsupported configuration: boot order 1 is already used by another device
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/addhardware.py", line
1420, in change_config_helper
define_func(devobj=devobj, do_hotplug=True, **define_args)
File "/usr/share/virt-manager/virtManager/domain.py", line 804, in define_disk
self.hotplug(**hotplug_kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1111, in hotplug
self.attach_device(device)
File "/usr/share/virt-manager/virtManager/domain.py", line 1041, in
attach_device
self._backend.attachDevice(devxml)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 508, in
attachDevice
if ret == -1: raise libvirtError ('virDomainAttachDevice()
failed', dom=self)
libvirtError: unsupported configuration: boot order 1 is already used
by another device
I also noticed that even after install, if the CDROM device is enabled
as a boot device, no media can be connected/disconnected while the
guest is running. I know this could be avoided by disabling it as a
boot device, but I would expect it to work more like it used to in
Fedora 20. Is there something else I can set in my configuration that
would allow me to connect/disconnect media if it's a bootable device?
Or do I need to open an issue?
Thanks,
Andrew Ruch
7 years, 12 months
unable to boot rhel5 guest with 3.19.7-200.fc21.x86_64
by Reartes Guillermo
Hi,
Since a couple of days i noticed that i cannot boot a rhel5 guest on
my F21 machine.
Today i was able to test it properly by rebooting a couble of times.
There seems to
be some issue with kernel 3.19.7-200.fc21.x86_64
Did anybody experienced something similar?
HOST: FEDORA: 21
CPU: AMD FX(tm)-6100
* With KERNEL: 3.19.7-200.fc21.x86_64
GUEST
* RHEL5: 5.11
* KERNEL: 2.6.18-404-el5 (also tried: 2.6.18-400.1.1.el5, 2.6.18-398.el5 )
* RESULT: Guest HANGS, with 100% vcpu usage after grub (no nash...
kernel alive, etc)
* If i try booting from the RHEL5 5.11 release iso image (cdrom),
it works...
* With KERNEL: 3.19.5-200.fc21.x86_64
GUEST
* RHEL5: 5.11
* KERNEL: 2.6.18-404-el5 (also tried: 2.6.18-400.1.1.el5, 2.6.18-398.el5 )
* RESULT: Guest boots normally. No known issues. (also booting the
iso also works)
Thanks in advance.
8 years
