Re: XenServer?

2011-02-18 Thread Ivan Voras
On 18 February 2011 16:40, Hugo Silva h...@barafranca.com wrote:

 I haven't tested with high vcpu counts, but in this particular VM, it's been
 running happily with 2 VCPUs and no noticeable problems. No panics,   no
 noticeable performance problems (after the tso fix) and certainly not the
 famous 'time went backwards' problem.

No such luck here; I've just tried an amd64 machine (8-STABLE from
today) in a new installation of XenServer 5.6 and while the GENERIC
kernel works stable enough, the XENHVM kernel produces all kinds of
timer-related problems, accompanied by messages like:

Feb 18 23:20:03 xbsd kernel: calcru: runtime went backwards from
28669021884109 usec to 22622950 usec for pid 11 (idle)

The difference between 28669021884109 and 22622950 is huge! It almost
looks like a memory corruption.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: HVM paravirt block/nic drivers

2010-01-11 Thread Ivan Voras
The given command was slightly wrong; it should have been:

make kernel KERNCONF=XENHVM


2010/1/11 David ad...@dmarkey.com:
 install -o root -g wheel -m 555   zfs.ko /boot/kernel
 install -o root -g wheel -m 555   zfs.ko.symbols /boot/kernel
 === zlib (install)
 install -o root -g wheel -m 555   zlib.ko /boot/kernel
 install -o root -g wheel -m 555   zlib.ko.symbols /boot/kernel
 kldxref /boot/kernel
 make: don't know how to make XENHVM. Stop
 Any Idea?

 2010/1/11 James Smith james.sm...@m247.com

  Compile kernel in the normal way, using the XENHVM config.



 cd /usr/src

 make kernel XENHVM

 edit /etc/rc.conf



 Change network interface to re0, save and reboot.



 Regards,

 James Smith,

 *From:* David [mailto:ad...@dmarkey.com]
 *Sent:* 11 January 2010 11:01
 *To:* James Smith
 *Cc:* freebsd-xen@freebsd.org
 *Subject:* Re: HVM paravirt block/nic drivers



 Well, im using the AMD64 ISO image,



 So i'll have to recompile the kernel? Are there instructions anywhere?



 Thanks.



 David

 2010/1/11 James Smith james.sm...@m247.com

 Hi,

 Have you compiled XENHVM kernel?  It makes some improvements to networking.
  Ensure you add the correct device to /etc/rc.conf afterwards, I believe it
 changes to xn0 when running XENHVM.

 Regards,
 James Smith,

 -Original Message-
 From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org]
 On Behalf Of David
 Sent: 10 January 2010 23:43
 To: freebsd-xen@freebsd.org
 Subject: HVM paravirt block/nic drivers

 Hi Guys/Girls,


 Successfully got a FreeBSD 8 HVM DomU installed. I see its using the
 emulated block/nic drivers.

 Is there any work being done on writing paravirt drivers for FreeBSD in
 HVM?

 Regards,

 David

 ___
 freebsd-xen@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-xen
 To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org



 ___
 freebsd-xen@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-xen
 To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: HVM paravirt block/nic drivers

2010-01-11 Thread Ivan Voras
2010/1/11 David ad...@dmarkey.com:
 Sorry, I see i'm using paravirt block device drivers.

 Timecounters tick every 1.000 msec
 acd0: CDROM QEMU DVD-ROM/0.10.2 at ata1-master WDMA2
 xbd0: 5120MB Virtual Block Device at device/vbd/768 on xenbus0
 xbd0: attaching as ad0
 xbd1: 658MB Virtual Block Device at device/vbd/5632 on xenbus0
 xbd1: attaching as ad2

You could use for example glabel labels to avoid changing device names.

 xn0: Virtual Network Interface at device/vif/0 on xenbus0
 xn0: Ethernet address: 00:16:3e:03:68:45
 WARNING: WITNESS option enabled, expect reduced performance.
 GEOM: ad0s1: geometry does not match label (16h,63s != 255h,63s).
 Trying to mount root from ufs:/dev/ad0s1a
 lock order reversal:
  1st 0xff800a550778 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559
  2nd 0xff0001440400 dirhash (dirhash) @

You also appear to be using a CURRENT kernel, or at least a kernel
with debugging enabled - which is fine if you know you want it.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org