Xen-kernel with no PAE support
by Filipe Miranda
Hello,
Since I have a thinkpad T41 with a non PAE CPU, unfortunately the xen-kernel
that comes with the FC6 does not work.
I know that the upstreams of the xen-kernel for FC6 will only work on CPUs
with PAE support, but what would be the best way to have a xen-kernel what
would have no-PAE support?
I downloaded the src xen-kernel file from the FC6 repositories and tried to
disable the PAE support. No success, it seems that the xen itself is PAE
aware.
Is there any *smart* suggestion on how to compile or get a xen-kernel that
would work on a non-PAE CPU?
Regards,
--
---
Filipe T Miranda
17 years, 4 months
SELinux HVM unfriendly?
by Robert Thiem
When getting hardware virtualisation running on my machine I noticed that
xen couldn't find my file backed disk unless I put selinux back to
permissive.
In /var/log/messages qemu-dm, ifconfig and python (running in the context
of xend_t) are triggering a lot of denies.
Is this usual, or have I messed up my SELinux policy somehow?
Paravirt seems happy enough, and I could just add a "setenforce
permissive" to the startup for whatever infrequently used full virt
systems I build. It's just a bit strange as selinux had been surprisingly
quiet so far on FC6.
Robert
17 years, 4 months
RHEL4 inside FC5/FC6 Dom0?
by Adrian Chadd
Hiya,
I'd like to install RHEL4 inside a FC5 or FC6 Dom0 to do some Squid development
and regression testing on. Has anyone done this? Any pointers to what I should be
looking at doing?
Bootstrapping Debian under Debian wasn't too hard - just debootstrap into a new
filesystem, then start domU up to finish configuration. I've had absolutely no luck
with the FC5 and FC6 supplied xenguest-install python stuff to bootstrap PVM guests.
Thanks,
Adrian
17 years, 5 months
memory allocation issue
by George Hill
Sorry for the repost, but this got burried as a possible follow-up to an old post. Was
Error: (12, 'Cannot allocate memory')
Sometimes I get a cannot allocate memory error when I try to create a guest.
I have plenty of memory. When I reboot the host, I no longer get the error.
Any ideas on how to fix this problem? Thanks for your help.
# xm create /etc/xen/FC6.virt3
Using config file "/etc/xen/FC6.virt3".
Error: (12, 'Cannot allocate memory')
The end of the log shows the following:
[2006-11-28 19:11:00 xend 2851] DEBUG (image:467) hvm shutdown watch registered
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] ERROR (XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363, in initDomain
raise VmError(str(exn))
VmError: (12, \047Cannot allocate memory\047)
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=3
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(3)
[2006-11-28 19:11:00 xend 2851] DEBUG (image:479) hvm shutdown watch unregistered
[2006-11-28 19:11:00 xend 2851] ERROR (xswatch:70) read_watch failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xswatch.py", line 66, in watchMain
res = watch.fn(we[0], *watch.args, **watch.kwargs)
File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 489, in hvm_shutdown
reason = vm.readDom(\047control/shutdown\047)
AttributeError: \047NoneType\047 object has no attribute \047readDom\047
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
17 years, 5 months
Error: (12, 'Cannot allocate memory')
by George Hill
Sometimes I get a cannot allocate memory error when I try to create a guest.
I have plenty of memory. When I reboot the host, I no longer get the error.
Any ideas on how to fix this problem? Thanks for your help.
# xm create /etc/xen/FC6.virt3
Using config file "/etc/xen/FC6.virt3".
Error: (12, 'Cannot allocate memory')
The end of the log shows the following:
[2006-11-28 19:11:00 xend 2851] DEBUG (image:467) hvm shutdown watch registered
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] ERROR (XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 195, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1363, in initDomain
raise VmError(str(exn))
VmError: (12, \047Cannot allocate memory\047)
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=3
[2006-11-28 19:11:00 xend.XendDomainInfo 2851] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(3)
[2006-11-28 19:11:00 xend 2851] DEBUG (image:479) hvm shutdown watch unregistered
[2006-11-28 19:11:00 xend 2851] ERROR (xswatch:70) read_watch failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xswatch.py", line 66, in watchMain
res = watch.fn(we[0], *watch.args, **watch.kwargs)
File "/usr/lib64/python2.4/site-packages/xen/xend/image.py", line 489, in hvm_shutdown
reason = vm.readDom(\047control/shutdown\047)
AttributeError: \047NoneType\047 object has no attribute \047readDom\047
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
17 years, 5 months
virDomainCreateLinux() failed
by Bill Davidsen
FC6, xen installed, latest updates as of five minutes ago. ASUS
P5LD2-R2.0 board, Intel 6600 CPU, 2GB RAM, 1.5TB disk.
PAE on, virtualization on. xend running, "xm list" works, shows one domain.
Install of any fully virtualized o/s fails. Sample output:
Would you like a fully virtualized guest (yes or no)? This will allow
you to run unmodified operating systems. yes
How much RAM should be allocated (in megabytes)? 256
Would you like to enable graphics support? (yes or no) no
Starting install...
libvir: Xen Daemon error : GET operation failed: No such domain OpenBSD-4.0
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error
creating domain: Disk image does not exist:
/home/davidsen/Virtual_Machines/OpenBSD-4.0a')
Failed to create domain OpenBSD-4.0
Traceback (most recent call last):
File "/usr/sbin/xenguest-install", line 396, in ?
main()
File "/usr/sbin/xenguest-install", line 360, in main
dom = guest.start_install(conscb)
File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line
355, in start_install
self.domain = self.conn.createLinux(cxml, 0)
File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed')
libvirt.libvirtError: virDomainCreateLinux() failed
Tried from CD, same error. Tried from xenguest-install and virt-manager,
same error.
VMware under Windows installs everything, but that's not where I need it
installed.
Any thoughts?
17 years, 5 months
xen partitioning for Vista
by Ian Patton
I added a new drive to use with a fully virtualized Xen domain. I intend to
run Vista on it. Should the partition be formatted? If so, should it be
formatted using ext3 or ntfs? Should the Windows installer do the
partitioning? I asked this as part of a multi-part question previously an
only got a partial answer excluding this.... On my system, the partition is
/dev/hdc1
On my first attempt at getting Vista to work, I used a file instead of a
partition and it worked. It worked for a very short period of time. Vista
would boot and I could see the desktop. The only thing that did not work
was the network, which I was sure would be an easy fix. I installed a few
patches and some other software via Yum and at some point Vista stopped
booting. I decided to add a new 120G disk for it to use and start over, but
ever since I have not been able to get it to run. None of the logs show
anything helpful. It runs for about 5 seconds, and I can see it boot from
the ISO that I made, but after it loads the progress bar to 100% it tries to
change the screen resolution or something and the processor drops to 0% and
nothing else happens.
Meanwhile, i have learned a bit about using Xen and tried to help others on
the list, but still have gotten nowhere with my own problems. I will be
posting a nice howto once i get all the steps and facts straight.
Thanks in advance,
Ian Patton
17 years, 5 months
Intel graphics problems: [ajackson@redhat.com: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6]
by Daniel P. Berrange
For anyone with an Intel graphics card who is experiancing hangs upon
boot / starting X under the Xen kernel, then I recommend testing this
updated X server RPm from updates-testing. It makes X use its own
x86 realmode emulator instead of relying on Xens. Send feedback to
the fedora-test-list(a)redhat.com if you have issues with this update.
Regards,
Dan.
----- Forwarded message from Adam Jackson <ajackson(a)redhat.com> -----
> Date: Wed, 15 Nov 2006 16:27:14 -0500
> From: "Adam Jackson" <ajackson(a)redhat.com>
> To: fedora-test-list(a)redhat.com
> Subject: Fedora Core 6 Test Update: xorg-x11-server-1.1.1-47.1.fc6
>
> ---------------------------------------------------------------------
> Fedora Test Update Notification
> FEDORA-2006-1237
> 2006-11-15
> ---------------------------------------------------------------------
>
> Product : Fedora Core 6
> Name : xorg-x11-server
> Version : 1.1.1
> Release : 47.1.fc6
> Summary : X.Org X11 X server
> Description :
> X.Org X11 X server
>
> ---------------------------------------------------------------------
>
> * Wed Nov 15 2006 Adam Jackson <ajackson(a)redhat.com> - 1.1.1-47.1.fc6
> - xorg-x11-server-1.1.1-int10-muxing.patch: Build both the vm86 and x86emu
> backends for BIOS calls on x86; prefer x86emu when running under Xen dom0
> since Xen's vm86 handling is flaky.
[snip changelogs]
>
> ---------------------------------------------------------------------
> This update can be downloaded from:
> http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/
>
> a5fc3ad6348f22bf0ac1379c2a58fc3bcb4155a9 SRPMS/xorg-x11-server-1.1.1-47.1.fc6.src.rpm
> a5fc3ad6348f22bf0ac1379c2a58fc3bcb4155a9 noarch/xorg-x11-server-1.1.1-47.1.fc6.src.rpm
> eafd7064ca6bbdd9e1fc1b0eae41878ef15defed ppc/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.ppc.rpm
> 58df8ab98a74cebbb1ed54886bf5c53431abf6ee ppc/xorg-x11-server-Xorg-1.1.1-47.1.fc6.ppc.rpm
> 8ae4230c83cfe5c7a1770e7b317e788ecf7a0d1b ppc/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.ppc.rpm
> 4b70dcf48e75c657e3fbf8dd77ace737d3a2a663 ppc/xorg-x11-server-sdk-1.1.1-47.1.fc6.ppc.rpm
> 360640e2ecb7055a059e8b73de4a865ddfd69dba ppc/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.ppc.rpm
> e1fcc733f9a9a0f84783e06054a876ae2e3120d1 ppc/xorg-x11-server-Xnest-1.1.1-47.1.fc6.ppc.rpm
> 584ad2bbf57c36e6aaedd9b7b68744cf88051dec ppc/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.ppc.rpm
> 729588c5283e9276c3342cbe11a22649204ba378 x86_64/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.x86_64.rpm
> 2e3e7a06ef8991469192ae4ce79df18e3b90375b x86_64/xorg-x11-server-Xorg-1.1.1-47.1.fc6.x86_64.rpm
> 0f4c5d1ec62a327bc1ece26b9661fa961b94d197 x86_64/xorg-x11-server-sdk-1.1.1-47.1.fc6.x86_64.rpm
> 3a5896dbb22523a8d51318197e7a842c4cce620c x86_64/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.x86_64.rpm
> 18f3afc3274e9cca963207e5d8476b9129bcef9d x86_64/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.x86_64.rpm
> 5366c9326e7fe40cf90a67d5b7953484a43d0e23 x86_64/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.x86_64.rpm
> b6125b5a79d48dd6dcc08e1821f55cab13b944ce x86_64/xorg-x11-server-Xnest-1.1.1-47.1.fc6.x86_64.rpm
> ab77099f59a79dc35ec6261344dc3498810ad750 i386/xorg-x11-server-Xorg-1.1.1-47.1.fc6.i386.rpm
> c4650da3cf8455bd68a81325d8b20236b9c93020 i386/xorg-x11-server-Xnest-1.1.1-47.1.fc6.i386.rpm
> 194a3c89736942f35b5ae4fdab7c670c986b37ba i386/xorg-x11-server-Xephyr-1.1.1-47.1.fc6.i386.rpm
> 7ed8bf3d750c6dcc1f819dc80a91d79d7d73af27 i386/xorg-x11-server-sdk-1.1.1-47.1.fc6.i386.rpm
> e3b589d56b2bb641a6cb17774b4e296cc2b4b7cb i386/debug/xorg-x11-server-debuginfo-1.1.1-47.1.fc6.i386.rpm
> f6e45c51bdbf4bd633095d1808f0e5b3b7ce2007 i386/xorg-x11-server-Xdmx-1.1.1-47.1.fc6.i386.rpm
> 5213b46a432e69dda9af2a178658c60b64b5dca9 i386/xorg-x11-server-Xvfb-1.1.1-47.1.fc6.i386.rpm
>
> This update can be installed with the 'yum' update program. Use 'yum update
> package-name' at the command line. For more information, refer to 'Managing
> Software with yum,' available at http://fedora.redhat.com/docs/yum/.
> ---------------------------------------------------------------------
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>
----- End forwarded message -----
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
17 years, 5 months
Guest OS Reboot
by Li, Shuo
Hi,
I installed FC5 as a guest OS on FC6 host system. I used the GUI version
of virt-manager. The installation finished OK. As I tried to boot guest
OS using xm create -c GuestFC5, the guest OS came up. But before for it
allowed me to login, it rebooted itself. It continued to reboot itself.
(most likely when it was trying to automount, but I am not certain about
this) Could someone point me to where the problem is?
Best
Shuo Li
17 years, 5 months
Re: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on Dell poweredge
by . .
>From: fedora-xen-request(a)redhat.com
>Reply-To: fedora-xen(a)redhat.com
>To: fedora-xen(a)redhat.com
>Subject: Fedora-xen Digest, Vol 12, Issue 52
>Date: Mon, 27 Nov 2006 12:00:10 -0500 (EST)
>
>Message: 1
>Date: Mon, 27 Nov 2006 16:50:52 +0100 (CET)
>From: Paul Wouters <paul(a)xelerance.com>
>Subject: Re: [Fedora-xen] FC6 w updates: xenguest-install.py hangs on
> Dell poweredge
>To: ". ." <porjo38(a)hotmail.com>
>Cc: fedora-xen(a)redhat.com
>Message-ID: <Pine.LNX.4.64.0611271648590.27487(a)tla.xelerance.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>On Mon, 27 Nov 2006, . . wrote:
>
> > On Mon, 20 Nov 2006, Paul Wouters wrote:
> >
> > > >xenguest-install -n ftp.xtdnet.nl -f
> > > >/children/ftp.xtdnet.nl/ftp.xtdnet.nl.img --nographics -p -l
> > > > >ftp://dl.xs4all.nl/pub/mirror/fedora/core/6/i386/os/ -x "noacpi
>noapic"
> > > >-r 1024
> > > >
> > > >
> > > >(the noapic noacpi was a test in the hope tht it would fix my issue).
> > > >
> > > >Also, I can still do xm shutdown and then I see the system halting.
> >
> > >Using kpartx and losetup, I checked the filesystems. They hasn't been
> > >any writing apart from formatting done to the disk. So no logfiles of
> > >the anaconda installer to see what went wrong either :
> >
> > >Paul
> >
> > Hi,
> >
> > I'm having exactly the same issue trying to load a new Xen guest system.
>My
> > setup is:
> >
> > AMD64, 1Gig RAM, SATA Hard disk
> > Fedora Core 6 x86_64 - Dom0
> >
> > I'm using FC6 for the guest system also, installing to a partition of
>the hard
> > disk - /dev/sda15
> > The installation source is an NFS mount of the FC6 DVD media (in the
>local DVD
> > drive).
> >
> > It gets to the "Starting install process. This may take several
>minutes..."
> > and just sits there. Every couple of minutes, the DVD drives spins up
>and
> > reads but nothing else happens - like it's stuck in a loop of some kind.
>The
> > log files in /var/log/xen don't give any clues.
>
>I did not get past this yet. I ended up doing a manual yum install with
>yum:
>
>yum -c yum-xen.conf --installroot=/mnt -y groupinstall Base
>
>Though perhaps next time I'll use a qemu install using the ISO DVD.
>
>Paul
>
>
>
>------------------------------
>
>--
>Fedora-xen mailing list
>Fedora-xen(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>End of Fedora-xen Digest, Vol 12, Issue 52
>******************************************
Hi Paul,
That's a good idea. I'm only somewhat familiar with this method - I
understand that you are mounting the Guest filesystem to /mnt then using yum
to install packages onto it. Do you have a good 'howto' you can recommend
that describes this procedure. Also, could you cat your yum-xen.conf file
for me? I'm not sure what you mean by a 'qemu install' - can you elaborate
on that?
Thanks,
Ian.
_________________________________________________________________
Advertisement: Looking to expand your DVD collection? Go to
www.tradingpost.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fwww%2Etradingpost%2Ecom%2...
17 years, 5 months
