I just tried kernel-2.6.32.10-1.2.92.xendom0.fc12.x86_64 from Mike
Young's repository on my MacBook and found that the video driver does
not seem to work. Lspci reports:
02:00.0 VGA compatible controller: nVidia Corporation GeForce 9400M (rev b1)
What is the grub.conf entry? Have you
I have been investigating the use of Xen with a Fedora 14 (devel)-based
Dom0. Until now, I have always used Michael Young's Dom0 kernels.
The first thing I did was try to build the current Fedora 14 kernel with
Xen Dom0 support. I began porting Michael's RPM specification to the
Fedora 14
I have built what may be my last Fedora 12 kernel
(2.6.32.26-174.2.xendom0.fc12) as Fedora 12 EOLs today (this is the same
Fedora patch level as the official 2.6.32.26-175.fc12 kernel which has
just been released). It is available at
This kernel works as expected with one exception. The exception has been
a nagging problem, but I have not reported it because 1) we are using
a research OS in DomU and 2) we are not clear if the problem is in our
code, Linux or Xen. But, here are the symptoms:
Occasionally (this seems to
This is something I raised on the upstream xen-devel mailing list. I
have not yet received any response, so I though I'd try to ask here:
I am using Xen with the included network-route and vif-route scripts. My
system runs Fedora 14 with Michael Young's Dom0 kernel.
When xend starts and
Now, the last issue remaining for me is the backend drivers. My
understanding is that, in the absence of backends being accepted
upstream, we can use QEMU-based drivers. This would be acceptable for
our work. Has anyone been using these with Fedora 15?
In theory the block driver should work
Now, the last issue remaining for me is the backend drivers. My
understanding is that, in the absence of backends being accepted
upstream, we can use QEMU-based drivers. This would be acceptable for
our work. Has anyone been using these with Fedora 15?
In theory the block driver should work
As reported earlier, I have been using 2.6.38-0.rc2.git3.2.xendom0.fc15
with good results. One thing I have come across is that power management
does not seem to work. For example, pm-suspend does not suspend my
system. Instead, the system merely becomes unresponsive. On the other
hand,
I have finally got a domU to boot in this sort of situation, having
found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub
as a bootloader. Note that you may have to use xl rather than xm
because they are deprecating xm and xm may not have support for qemu
block backends.
Does
On Wed, Feb 02, 2011 at 10:43:18PM +, M A Young wrote:
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen
(4.1.0-0.1.rc3.fc14) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
Here is
I have a new kernel (2.6.38-0.rc4.git3.1.xendom0.fc15) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2833991 . This uses the
Konrad's devel/next-2.6.38 branch (from
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git ), as I have been
having trouble which Jeremy's
I sent the following to xen-users, but thought I'd ask the Fedora
folks too.
I am running the OpenSSL s_server/s_time benchmark between two DomUs. The
two DomUs are running on separate machines, and they are the only
unprivileged domain running on their machine. Both machines have dual
core AMD
Here is another kernel (2.6.38-0.rc6.git6.1.xendom0.fc15) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2874240
The crash when a domU shuts down seems to be fixed.
I just had a chance to test this, along with the
xen-4.1.0-0.1.rc6.fc14.x86_64 Xen packages.
Two notable things have
We got another release candidiate xen-4.1.0-rc8 instead, built at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2929815
The final release has slipped to Friday. I am considering building the
release candidate as an official rawhide/F15 package so I can be sure to
get it into F15 in time
I have done an experimental kernel, which is a standard F15 2.6.38 kernel
plus the two packages needed to get the xen net backend working. In my
testing on an F15 host I could get a guest to boot from a text boot,
though X crashed. The build is at
Is anyone using OProfile with Xen? I am especially interested in the
passive profiling of Xen DomU domains.
I've attached a Xen patch against the Fedora oprofile package to a
report in Bugzilla, #693596. But, even with this patch I am getting
mixed results.
See also
The Xen Dom0 feature described at
http://fedoraproject.org/wiki/Features/XenPvopsDom0
has been pushed to Fedora 16. I don't think this should come as a
surprise. A lot of people are working hard on the kernel components,
but they did not make the Fedora 15 timeline.
--
Mike
:wq
--
xen
Has anyone else had trouble starting xend when SELinux is enforcing the
targeted policy on the various test releases of Fedora 15? I just
submitted a bug report at:
https://bugzilla.redhat.com/show_bug.cgi?id=706987
--
Mike
:wq
--
xen mailing list
xen@lists.fedoraproject.org
The old xm command allowed for a domain to be configured from and
command line using xm create /dev/null kernel=x ... Xl does not seem
to support this:
$ sudo xl create /dev/null
libxl: error: libxl_utils.c:328:libxl_read_file_contents /dev/null is not a
plain file: Success
Failed to read config
Has anyone had similar trouble?
No. But it sounds like the AVX disaster.
https://bugzilla.redhat.com/show_bug.cgi?id=801650
It seems to be.
I booted bare metal and used yum to install gdb and the debug symbols
for Python and glibc.
Then I rebooted in Xen. I found that gdb itself
I have done a temporary build of 4.2.0-rc2 for testing which is at
http://koji.fedoraproject.org/koji/taskinfo?taskID=4386920
This also adds the efi hypervisor back in for x86_64.
Note to other people: fedora kernels still don't have xen dom0 EFI patches
included,
mainly because dom0 EFI
I have done a temporary build of 4.2.0-rc2 for testing which is at
http://koji.fedoraproject.org/koji/taskinfo?taskID=4386920
This also adds the efi hypervisor back in for x86_64.
Note to other people: fedora kernels still don't have xen dom0 EFI
patches included,
mainly because dom0 EFI
I have successfully installed Fedora 18 Beta as Dom0 on one computer,
and am now trying to do the same on another. I am using all of the
standard Fedora 18 packages, including xen-4.2.0-6.fc18.x86_64.
On the second computer, I ended up with an EFI grub2 install.
I used yum to install xen, and
I have successfully installed Fedora 18 Beta as Dom0 on one computer,
and am now trying to do the same on another. I am using all of the
standard Fedora 18 packages, including xen-4.2.0-6.fc18.x86_64.
On the second computer, I ended up with an EFI grub2 install.
I used yum to install xen,
I've the same exact problem. I had to manually run grub2-mkconfig in
my all F17 boxes.
Did you update the kernel at the same time? That looks like what you
might get with grubby which is run (which doesn't handle xen very
well, which is why xen-hypervisor runs grub2-mkconfig).
This is also
The second Xen Test Day for the Xen 4.3 release cycle is going to be
next Wednesday, the 22nd of May!
We'll have the chance to test Xen 4.3 RC2, that will be out tomorrow.
For more information see:
- On Xen Test Days: http://wiki.xen.org/wiki/Xen_Test_Days
- On getting and testing
Has anyone else seen this:
https://bugzilla.redhat.com/show_bug.cgi?id=1188573 ?
The current Fedora 21 kernel crashes on my computer when booted in Dom0.
$ uname -a
Linux imp.flyn.org 3.18.3-201.fc21.x86_64 #1 SMP Mon Jan 19 15:59:31 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
Mike
Has anyone else seen things like "xl list" or xentop hang on Fedora 24?
# rpm -q kernel xen
kernel-4.5.5-300.fc24.x86_64
xen-4.6.1-10.fc24.x86_64
Running "strace xl list" produces the following, which seems to indicate
that the hang occurs when "xl list" writes to /dev/xen/xenbus:
>> Has anyone else seen things like "xl list" or xentop hang on Fedora 24?
>>
>> # rpm -q kernel xen
>> kernel-4.5.5-300.fc24.x86_64
>> xen-4.6.1-10.fc24.x86_64
>>
>> Running "strace xl list" produces the following, which seems to indicate
>> that the hang occurs when "xl list" writes to
What file-backed disk formats are supported by Xen using a Fedora Dom0? I
am testing xen-4.6.1-8.fc24.x86_64, and I have not been able to get the
"qcow2" and "vhd" formats to work. "Qcow" version 1 works fine with:
disk = [ "tap2:qcow:/var/lib/xen/images/test-data.xen-qcow,xvdb,w" ]
Is anyone running a Windows HVM guest with networking? I recently tried
to connect a Windows 7 HVM guest to my network using vif-nat. For some
reason, the setup does not work. Oddly, Dom0 lists the vif interface
associated with the guest as "NO-CARRIER" even though the DomU Windows
guest seems to
>> Is anyone running a Windows HVM guest with networking? I recently tried
>> to connect a Windows 7 HVM guest to my network using vif-nat. For some
>> reason, the setup does not work. Oddly, Dom0 lists the vif interface
>> associated with the guest as "NO-CARRIER" even though the DomU Windows
>>
32 matches
Mail list logo
