chrupol
2011-Nov-12 09:18 UTC
[Xen-users] ### Problem with Xen4 on Debian as FreeBSD DomU ###
Hello i trying start to run FreeBSD 8.2 amd64 iso image on Xen 4 but when i trying start machine in log QEMU i see a errors: -- domid: 21 -c config qemu network with xen bridge for tap21.0 eth0 Using file /dev/loop0 in read-only mode Using file /dev/listonosz/freebsd in read-write mode Using file /dev/listonosz/freebsd-swap in read-write mode Watching /local/domain/0/device-model/21/logdirty/cmd Watching /local/domain/0/device-model/21/command char device redirected to /dev/pts/0 qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 9efb47e1-af05-7067-2d99-4f5792aa4e02 Time offset set 0 populating video RAM at ff000000 mapping video RAM from ff000000 xs_read(/local/domain/0/device-model/21/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/9efb47e1-af05-7067-2d99-4f5792aa4e02/vncpasswd. medium change watch on `hdc'' (index: 0): /dev/loop0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 -- cut please help me with this problem I made 2 LVM disk freebsd and freebsd-swap and i trying load ISO image as file and phy as loop`ack -- View this message in context: http://xen.1045712.n5.nabble.com/Problem-with-Xen4-on-Debian-as-FreeBSD-DomU-tp4986590p4986590.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Florian Heigl
2011-Nov-14 21:49 UTC
Re: [Xen-users] ### Problem with Xen4 on Debian as FreeBSD DomU ###
Hi, 2011/11/12 chrupol <gregor@szu.pl>:> Hello i trying start to run FreeBSD 8.2 amd64 iso image on Xen 4I don''t know about your issue. I will add info about how my FreeBSD domU''s config looks. Maybe this will help you solving your issue. it took me long enough to have something working. Note on the first install I still used the tap network drivers and accordingly something like ifconfig_rl0. Once the kernel was installed, we can use the Xen PV drivers for disk and network and get great performance. As you see the kernel still has debug symbols. It was reasonably fast anyway, dtc_admin = "xxx" kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' memory = 256 name = "xen10" vcpus = 1 #pae=0 #acpi=0 #apic=0 vif = [ ''mac=00:16:3E:xxx, ip=xxxx, bridge=eth0'' ] disk=[ ''phy:/dev/vgxen/xen10,xvda,w'', ''phy:/dev/vgxen/xen10swap,xvdb,w'', ''phy:/dev/vgxen/xen10data,xvdc,w'', ] vfb = [ "type=vnc,vncdisplay=10,vncpasswd=xxxx" ] cdrom="/var/lib/dtc-xen/ttyssh_home/xen10/" boot="c" nographic=0 vnc=1 stdvga=1 serial=''pty'' cpus = ''^0,^1,2-7'' # ignore that line i think it''s not even correct. This is the kernel config: cpu I686_CPU ident XEN makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols makeoptions MODULES_OVERRIDE="" options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption #options SCHED_4BSD options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AUDIT # Security event auditing # Debugging for use in -current options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don''t run witness on spinlocks for speed options PAE nooption NATIVE option XEN nodevice atpic nodevice isa options MCLSHIFT=12 # To make an SMP kernel, the next two lines are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC #device atkbdc # AT keyboard controller #device atkbd # AT keyboard device psm # PS/2 mouse device pci #device kbdmux # keyboard multiplexer # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf'' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that ''bpf'' is required for DHCP. device bpf # Berkeley packet filter And last, rc.conf hostname="xxx.wartungsfenster.de" ifconfig_xn0="inet xxxx netmask 255.255.255.224 -tso" static_routes="dom0 default" #route_gw="-host xxx/32 -iface -interface xn0" # Ignore that only needed at hetzner #route_default="default xxx" sshd_enable=yes inetd_enable=yes inetd_flags=-wW fail2ban_enable=yes apache22_enable=yes bacula_fd_enable="YES" ntpd_enable="YES" pf_enable="YES" I hope you get it to work. Otherwise you might want to take this to the freebsd-xen list at freebsd.org Greetings, Florian -- the purpose of libvirt is to provide an abstraction layer hiding all xen features added since 2006 until they were finally understood and copied by the kvm devs. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Florian Heigl
2011-Nov-14 21:52 UTC
Re: [Xen-users] ### Problem with Xen4 on Debian as FreeBSD DomU ###
I just had to grab the wrong kernel config, didn''t I? This is the amd64 config, much shorter. Include GENERIC ident XENHVM makeoptions MODULES_OVERRIDE="" device pf device pflog device pfsync # # Adaptive locks rely on a lock-free pointer read to determine the run state # of the thread holding a lock when under contention; under a virtualisation # system, the thread run state may not accurately reflect whether the thread # (or rather its host VCPU) is actually executing. As such, disable this # optimisation. # options NO_ADAPTIVE_MUTEXES options NO_ADAPTIVE_RWLOCKS # Xen HVM support options XENHVM device xenpci Sorry :) Florian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users