similar to: FreeBSD 4 XenU

Just wanted to try domU freebsd and found <http://216.239.59.104/search?q=cache:M_4r1b-RG- EJ:www.fsmware.com/xenofreebsd/5.3/xenbsdsetup.txt&hl=en&lr=&strip=1> but the webservice on www.fsmware.com seems to be down/unavailable. Any mirror? Or other working FreeBSD domU-kernels & images? Regards, /nils. _______________________________________________ Xen-devel mailing

Hi, I understand that 64-bit support for xen (from the side of host OSes) will be a little late, so i have a couple of questions: 1) Can i install a x86 32-bit xen kernel on x86_64 pc, without problems? 2)If i install a x86_64 xen kernel, can i run 32-bit host OSes on it? I know little about Xen, so i''d like to clear these out. Thanks

Any thoughts on setting breakpoints around hypercalls? ---------- Forwarded message ---------- From: Kip Macy <kip.macy@gmail.com> Date: Dec 26, 2005 12:14 AM Subject: setting breakpoints around hypercalls in a domU causes dom0 to lockup To: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser < Keir.Fraser@cl.cam.ac.uk> Stepping through hypercalls (at the source level, not

I''ve locked up my dom0 a couple of times this morning copying a 3GB file from local disk to an NFS mount(neither xend nor guests running). I don''t encounter this problem on the stock CentOS 4 kernel. The machine is a PowerEdge 2850 with 2 e1000 cards - the one in use is connected to a PowerConnect 2216 10/100 switch and has negotiated 100Mbit. I''ll check if the stock

Presumably as a result of recent changes, FreeBSD no longer works with writable page tables. In the short-term I''m more interested in functionality than performance. This patch disables them and fixes a compile issue. # This is a BitKeeper generated diff -Nru style patch. # # ChangeSet # 2005/04/29 19:26:00-07:00 kmacy@curly.lab.netapp.com # disable writable pagetables + compile

On 16/11/05, Kip Macy <kip.macy@gmail.com> wrote: > The way the initial memory space gets setup there is no way MFS could work. > It wasn''t an anticipated use. I guess somewhere either in FreeBSD GNATS or > xen''s bugzilla there should be i386-xen FreeBSD bugs filed for me to track. I intend to file a bug report sooner or later, but in the meantime I decided to

CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `vmcoreinfo_show'': /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `vmcoreinfo_size_xen'' /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `paddr_vmcoreinfo_xen'' make[4]: ** [.tmp_vmlinux1]

It looks like I can no longer map a page as uncacheable. Is this intentional? -Kip _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Using the 2.0.6 demo cd image, I booted the supplied freebsd image and rsync''d the file system to an NFS server. However I don not seem to be able to succesfully boot from it the system just hangs here: xn0: bpf attached xn0: Ethernet address: aa:00:00:61:1c:d4 lo0: bpf I have modified /sbin/start_freebsd.sh and /etc/xen/freebsd.py to generate the following configuration: xendemo:~#

I encountered a problem with dom0 when rebooting and running an intel gigabit card using the pro/1000 driver. When the system tries to shut down I get the following output of an strace command : ......... 17:10:49.063616 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000029> 17:10:49.063689 ioctl(3, 0x8913, 0xbffffc80) = 0 <0.000018> 17:10:49.063751 ioctl(3, 0x8914, 0xbffffc80) =

One of the things that I''ve always thought was weird, but didn''t pay too close attention to is the fact that GETDOMAININFO will return a valid result even if we give it a domid that is no longer valid. Looking at the code we get back the first valid domain after the domid we pass in. What is the reason for this design choice? When I request the attributes of a process I

I converted a physical maschine running CentOS 4.6 to a Xen VM on a CentOS 5 host. Almost everything was running when I decided to rsync /lib and /usr a while later in order to get updated files and get the one or two non-working programs to work. There are differences because of the xenU kernel I didn't think about. I forgot to exclude rpm database and /lib/modules. Because the synced

Hi xen users, I''d like xen0 to be the controller and xenU(1) to be a firewall/router with 4 subnets (WAN, LAN, DMZ, TEAM) each with 1 of 4 physical nics attached to it. Using FC4 with xen-3.0.0-7 with linux kernel 2.6.12.6, default make world configurations, box is athlon cpu, 512M, 4 nics. On boot all nics are recognized, lspci shows them to be present. In xenU there are four ifcfg

I see the following with a FreeBSD 5.3 DomU on 2.0.7 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xca7a0088 fault code = supervisor read, page not present instruction pointer = 0x819:0xc0183343 stack pointer = 0x821:0xca069d30 frame pointer = 0x821:0x0 code segment = base 0x235, limit 0x8485e7c3, type 0x9

Hi! May anyone assist me with booting FreeBSD DomU (under Debian Dom0). Now I''m using the kernel-current, downloaded from Kip Macy site at http://www.fsmware.com/xenofreebsd/7.0/download/ The problem is that I can''t specify _any_ root, the kernel can recognize: Mount point / had 1 dangling refs Manual root filesystem specification: <fstype>:<device> Mount

Hello. I''m new to the list and I hope this is not a FAQ. I searched the archives and didn''t find an answer... Quick question : Is there a limitation if the vif code cutting at 1500 bytes ?? I''m trying to implement an IPv6 router/Firewall (2 XenU) Xen 2.0.6, Linux 2.6 is used on xen0 and XenU. The physical machine has 2 interfaces, eth0 (which is connected to an

Hello, please can someone on the list point me to the right direction how to build xen0 and xenU kernels for linux-2.6.27-xen.hg? A make world KERNELS="linux-2.6-xen0 linux-2.6-xenU" leads me to the error: select-linux-arch: x86 select-linux-image: cannot determine Linux image to use for x86 in build-linux-2.6.27-xen0_x86_32 cp: missing destination file operand after

from the README: " These are smaller builds with just selected modules, intended primarilly for developers that don''t like to wait for a -xen kernel to build. The -xenU kernel is particularly small as it does not contain any physical device drivers, and hence is only useful for guest domains." correct me here, but does that mean for a typical rollout you want to

There is no CONFIG_SCSI to enable in xenU. Is there any reason for this? I want to try out iSCSI and obviously it needs scsi support. Or would I be better doing it in dom0 and exporting it? thanks James

Hi, I''m trying to run Xen 3.0 on my amd64 UP machine. So far xen0 is working fine but there is a problem with mounting rootfs on xenU kernel. Is there something else that needs to be compiled into xenU 3.0 kernel? $ grep XEN kernel-xenU-x86_64-3.0.config CONFIG_XEN=y CONFIG_ARCH_XEN=y # XEN # CONFIG_XEN_PRIVILEGED_GUEST is not set # CONFIG_XEN_PHYSDEV_ACCESS is not set