Zhi,
Regarding step 10 below, are you using usbdevice=’tablet’
in your domU config instead of the usbdevice=’mouse’ default? If not, doing so
may resolve the mouse sync issue to a far better degree than simply disabling
the Windows option you mention.
Dustin
From:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zhi Wang
Sent: Thursday, October 23, 2008 11:33
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Building from Source
I
spent many hours to try to build a working Xen from source code. This is what I
found for fedora 9.
Build HVM client in Fedora 9
- When installing fedora core 9, partition the disk
using LVM2. Create two virtual group: one for host and the other one for
guest. Select the development tools when install the OS.
- yum install mercurial
- yum install dev86 (for bcc, hvmloader need this)
- mv /lib/tls /lib/tls.disabled
- echo "hwcap 0 nosegneg" >
/etc/ld.so.conf.d/nosegneg.conf
- ldconfig
- make world
- ./install
- create an initrd by:
- # depmod 2.6.18-xen
- # mkinitrd -v -f --with=aacraid
--with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen
- If you will use, VNC's mouse maybe out of sync
with the host, in Windows, disable the "Enhance Pointer
Precision" option in the mouse configuration
As in steps 4 and 5, I tried to disable the nosegneg warning
during Xen start. But it may sometimes still appear. I have no idea why.
About the Linux distribution, some developers of Xen I happen to know use RHEL
5.2. Maybe you can try CentOS5.2.
Thanks
>Xen
Users,
>
>I
have always used XEN from the debian/ubuntu repositories, as I have had very
good experiences with the repository version. However, I now find myself
needing to build XEN from source, so that I can boot BSD based >guests
(needs to be compiled with vmxassist=n).
>
>I
have now spent well over 12 hours trying to get a build-from source
installation of XEN 3.3 on Ubuntu. I have finally gotten myself to a
somewhat working place - Dom0 now boots (although I get some error messages
>about apparmor support, etc), but when I go to create a DomU, it instantly
flips the DomU back off. I get a message from QEMU in the qemu-domain log....
"I/O request not ready: 0, pty:0, port: 0, data: 0, count: 0, size:
0". >Ugh.
>
>Most
likely, I need to start over (again), but I feel like I'm crawling through this
process. Are there any good guides out there on building 3.3 from source
on a clean system, or a repository with VMXASSIST=n already >built in, or a
workaround to rebuilding the whole thing?
>
>I'll
definitely owe someone a beer.
>
>Thank You,