search for: boeni

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

Does anyone know the problem with missing device nodes (like /dev/hda1) in domU? Must the device nodes used in domU exist in the dom0? What i have to do, when some device nodes are missing in domU? Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''ve compiled the 3.0-devel version on SUSE Linux 9.3. The ony problem is the qla2300 driver, which will not start all correctly on boot. So i cannot see other partitions than sda. --------------------------------------------------------------------------------- QLogic Fibre Channel HBA Driver ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185 qla2300

Has anyone succeeded with bonding? Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

When i try to compile xen 3.0-devel with "make world", i''ve got the following compile error: gcc -m32 -march=i686 -Wall -W -g -Wp,-MD,.xenstore_read.o.d -I../../tools/libx c -I../../xen/include/public -I../../xen/include/public -I../../linux-2.6-xen-sp arse/include/asm-xen/linux-public -c -DCLIENT_read -o xenstore_read.o xenstore _client.c xenstore_client.c:16:16: xs.h: No

Funny thing. My Xen3 kernel does only find /dev/sda where i''m booting from, but not the other scsi disks like /dev/sdb.... (In fact all they aren''t real scsi disks. It''s a fibre channel SAN storage.) Has anyone an idea, why i can view with my Xen3 kernel only the first device? Thanks for any help. Stephan _______________________________________________ Xen-users

Kernel 2.6.12 contains a bad bug. So i need kernel 2.6.12.6. If i build Xen3 with make world it will still download/compile the old kernel 2.6.12. How can i build Xen3 with a newer kernel? Stephan <http://www.buchmesse.de/imperia/md/images/logos/fbm/2003/Logo100s150px.gif> 19. - 23. Oktober 2005 Halle 4.0 / Stand F1305 Reservieren Sie sich bereits heute über unsere Homepage

I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors: # mkinitrd Root device: /dev/sda3 (mounted on / as reiserfs) Module list: ata_piix mptbase mptscsih qla2300 reiserfs Kernel image: /boot/vmlinuz-2.6.11.12-xen0 Initrd image: /boot/initrd-2.6.11.12-xen0 Shared

I cannot compile the latest xen build (make world): make[4]: Entering directory `/setup/xen/xen-unstable/tools/firmware/acpi'' gcc -o acpigen -I. -I../../libxc acpi_build.c acpi_dsdt.c acpi_facs.c acpi_fadt. c acpi_gen.c acpi_madt.c acpi_rsdt.c acpi_gen.c: In function âmainâ: acpi_gen.c:44: warning: incompatible implicit declaration of built-in function â exitâ acpi_gen.c:51: warning:

I cannot compile the latest xen build (make world): make[4]: Entering directory `/setup/xen/xen-unstable/tools/firmware/acpi'' gcc -o acpigen -I. -I../../libxc acpi_build.c acpi_dsdt.c acpi_facs.c acpi_fadt. c acpi_gen.c acpi_madt.c acpi_rsdt.c acpi_gen.c: In function âmainâ: acpi_gen.c:44: warning: incompatible implicit declaration of built-in function â exitâ acpi_gen.c:51: warning:

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with