Xen4.1.0 and Fedora15 Block device bug?
by Travis
Hi guys,
I'm an administrator for a small cluster running ganeti2.3.1/xen4.1.0/drbd83
on centos5.6, with predominantly fedora14 instances. We've been running the
fedora 14 images pretty well, not many issues. However, I've noticed that in
an attempt to install fedora 15, the virtualized block devices are
unrecognized by anaconda. has anyone else seen this or is this a known
issue?
-Corasian
12 years, 11 months
Fedora 15 XEN 4.1 and kernel-2.6.38-1.xendom0.fc15.x86_64 - No HVM ??
by Outback Dingo
This is a Fedora 15 laptop with KDE spin... Ive proven and tested -pvm
Fedora 15 install via url, as working, though Im trying
to Install FreeBSD from ISO as there is no url install im
using kernel-2.6.38-1.xendom0.fc15.x86_64.rpm for the domO and XEN 4.1
installed from yum install
and the following grub.conf
title Fedora XEN 4.1.1 (2.6.38-1.xendom0.fc15.x86_64)
kernel /xen.gz dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
module /vmlinuz-2.6.38-1.xendom0.fc15.x86_64 ro
root=UUID=83dad5a3-729f-4365-a190-f90f7a22079d SYSFONT=latarcyrheb-sun16
LANG=en_US.UTF-8 KEYTABLE=us
module /initramfs-2.6.38-1.xendom0.fc15.x86_64.img
xm info shows
xm info
host : localhost.localdomain
release : 2.6.38-1.xendom0.fc15.x86_64
version : #1 SMP Tue Mar 15 21:28:00 UTC 2011
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 2
cpu_mhz : 2660
hw_caps :
bfebfbff:28100800:00000000:00003f40:009ae3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 3766
free_memory : 2694
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : .1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=1024M iommu=1 loglvl=all guest_loglvl=all
cc_compiler : gcc version 4.6.0 20110530 (Red Hat 4.6.0-9) (GCC)
cc_compile_by : dingo
cc_compile_domain : localdomain
cc_compile_date : Thu Jun 23 01:02:35 EDT 2011
xend_config_format : 4
virt-install --name frisbee3 --ram 512 --vnc --os-type=unix
--os-variant=freebsd7 --network bridge=virbr0 --file /home/dingo/oneric.img
--cdrom /home/dingo/FreeBSD-8.2-RC2-amd64-disc1.iso --force --hvm
Starting install...
Creating domain...
| 0 B
00:03
Domain installation does not appear to have been successful.
cat /var/log/xen/qemu-dm-frisbee3.log
domid: 2
config qemu network with xen bridge for tap2.0 virbr0
Using file /home/dingo/oneric.img in read-write mode
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
Watching /local/domain/2/cpu
char device redirected to /dev/pts/3
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 3e6df518-31f1-03e7-73e1-511eb535e14c-1
Time offset set 0
char device redirected to /dev/pts/4
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/3e6df518-31f1-03e7-73e1-511eb535e14c-1/vncpasswd.
medium change watch on `hdc' (index: 1):
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
vcpu-set: watch node error.
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling'
medium change watch on `/local/domain/2/log-throttling' - unknown device,
ignored
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
Soooo Any ideas ??
12 years, 12 months
