Anytime I shutdown or restart (the guest will successfully restart) an
f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install
to fail. Attempts to restart virt-manager hang at "Connecting". no
luck restarting xend, libvirtd, or even xenstored, only solution I've
found is a dom0 reboot! Same problem on 2 different host systems,
different hardware, dom0 installed by different people. I have no
trouble with <=f8 guests on either of these boxes.
more details at
I assume other people are successfully running f9 guests on f8 dom0?!
No one else having this issue?
I'm pleased to announce the first release of 'virt-what', which is a
simple shell script that detects if you are running inside a virtual
machine, and prints some "facts" about that virtual machine. This is
a frequently requested feature.
Home page: http://et.redhat.com/~rjones/virt-what/
Source and RPMs: http://et.redhat.com/~rjones/virt-what/files/
So far we can detect:
- QEMU and KVM (but not distinguish between them)
- Microsoft VirtualPC
I'm hoping that people who run or develop other virtualization
technology will be able to contribute snippets to detect those.
It's worth saying (before Dan Berrange says it anyway) that although
people often think they need this sort of feature, in most cases using
this script is the WRONG THING. If you need a specific virtualization
feature, then add code to your application to detect that feature.
eg. If you need to make Xen hypervisor calls, your application should
try to open /proc/xen/privcmd. As Dan once put it:
A shell script just printing out 'native', 'dom0' or 'domU' is too
simplistic to be broadly useful to management applications. The
concepts are also ill-defined, eg 'native' as a concept can be a
baremetal kernel, or a fully-virtualized guest, or both. 'DomU' does
not distinguish full or paravirt. The distinction of 'dom0' vs
'native' is irrelevant in non-Xen virtualization systems (eg KVM).
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
I'm a bit confused, if it will be possible to run a F8-DomU on top of a Fedora10-Dom0?
Currently I'm using a Fedora8-DomU with PCI-Passthrough on a Fedora8-Dom0 for being able to use an ISDN-Card with badly designed drivers. And since the vendor's closed souce driver doesn't support kernel versions >= 2.6.22, it would be great, if i could still use that ISDN-Card in it's existing DomU without losing the benefits of upcoming Fedora 10.
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
----- Forwarded message from Keir Fraser <keir.fraser(a)eu.citrix.com> -----
From: Keir Fraser <keir.fraser(a)eu.citrix.com>
To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com>
Date: Fri, 22 Aug 2008 12:53:35 +0100
Subject: [Xen-devel] ANNOUNCE: Xen 3.3.0 released!
We're pleased to announce the official release of Xen 3.3.0!
This is a major new release with a host of new features including:
- Power management (P & C states) in the hypervisor
- HVM emulation domains ('qemu-on-minios') for better scalability,
performance and security
- PVGrub: boot PV kernels using real GRUB inside the PV domain
- Better PV performance: domain lock removed from pagetable-update paths
- Shadow3: optimisations to make this the best shadow pagetable algorithm
yet, making HVM performance better than ever
- Hardware Assisted Paging enhancements: 2MB page support for better TLB
- CPUID feature levelling: allows safe domain migration across systems with
different CPU models.
- PVSCSI drivers for SCSI access direct into PV guests
- HVM framebuffer optimisations: scan for framebuffer updates more
- Device passthrough enhancements
- Full x86 real-mode emulation for HVM guests on Intel VT: supports a much
wider range of legacy guest OSes
- New qemu merge with upstream development
- Many other changes in both x86 and IA64 ports
You can get the source using mercurial from:
A pre-prepared source tarball is available from:
(please ignore the 'Xen 3.2' graphic used in the download listing :-).
Keir (on behalf of the whole Xen dev team)
Xen-devel mailing list
----- End forwarded message -----
Given that xen is entering feature freeze for updated release ~August
is it too early to ask what the *hopes* are for xen in fedora10?
xen 3.3.0 (or late rc) or is this still likely to be 3.2.1 or 3.2.2?
kernel 2.6.27(or late rc) with pv_ops for 32 and 64 bit, dom0 and domU?
updates to libvirt/virt-manager as usual
So I'm using F9 on a laptop installed with rootfs disk encryption. Now I
wanted to run a dom0 xen on it, so i had to go back to a 2.6.21 based
f8 kernel. This kernel did not boot, due to sd_mod not being included
in the initrd. scsi_mod is there, but sd_mod is not. Rebuilding the
fc8xen initrd on f9 using mkinitrd --preload sd_mod resolved that issue.
Additionally, there is a missing "clear" somewhere, so the xen boot
lines and the kernel boot lines interleave badly.
Where should I report this so the next f8xen kernel update will have
Next, I'm getting the following error, after unlocking the encrypted
security: class 31 is incorrect, found x_drawable, but should be drabable
security: the definition of a class is incorect
SElinux: Could not load policy file /etc/selinux/targeted/policy/policy.23: Invalid argument
and then the machine halts.
Note that f9 has been the first version where I didnt run into SElinux
issues and I'm surprised that I found myself not disabling it yet, so
congrats on that front.
I'm trying to boot Xen mounting the /usr directory through NFS.
I get though the following error:
Starting xen daemons: xenstored blktapctrl xenconsoled xendTraceback (most
recent call last):
File "/usr/sbin/yum-updatesd", line 39, in <module>
File "/usr/lib64/python2.5/site-packages/gamin.py", line 39,
err = _gamin.Errno()
TabError: inconsistent use of tabs and spaces in indentation
Does anyone know what that means?
I'm trying to create a Debian DomU on a Fedora Dom0.
I can't do this using virt-install and I don't know how to use config files
to create a VM on a Fedora Dom0 (I just know on Debian Dom0, using
Could someone help me?
Marcel Damásio Moreira
9º período de Ciência da Computação - UFES
Estagiário do NPD - UFES
I've tried three times to install Fedora Core 9 as a PV guest on a
Centos 5 host. Every time, it gets most of the way through the install,
and then hangs on installing openoffice.org-writer2latex-0.5-2.fc9.i386.
The first two attempts were with the official FC9 DVD, and for the third
I tried the Unity respin from 7/18/08.
Does anyone know what the problem could be? Alternatively, what useful
information could I provide to this list? Thanks.