Re: 9.1R?
On Sun, 23 Dec 2012 18:36:54 +0900 moto kawasaki wrote: > It might be better to disable rxcsum, txcsum, and lro, too. > My understanding is the point is the 'NIC hardware' is not the real > one but emulation by Xen Host, so that those 'off loading' makes > context switch storm between domU and dom0. > # please kindly correct me if wrong. You're actually quite correct as this is a source of network problems on many different domU OSes. ___ 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: 9.1R?
On 26/12/12 21:00, Mark Felder wrote: On Wed, 26 Dec 2012 10:17:25 +0900 moto kawasaki wrote: Official Support of FreeBSD as domU. # Didn't someone talk about it on this ML ?? or my imagination ?? I've mentioned it. The domU tools scripts are being redesigned to be more platform agnostic and a guy on that team at Citrix has been having me assist him with figuring out how to pull data in the format he needs as there are new features coming to XenServer. It looks like Citrix has interest in FreeBSD because a client wants to do a large deployment, and NetBSD will be easy too. They want these tools to be in FreeBSD ports and NetBSD's pkgsrc, so it will be well integrated with the community and the way the OS already is maintained. It just sounds like Citrix will be pushing patches to the port maintainer in the future (unless they take it over themselves). Overall, things are looking bright for FreeBSD/Xen users. ___ 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" Hi all :), As far as I get some free time... gonna do a check of all this bugs (some of them I knew) and if it requires... will talk to Citrix people in order to help or get some help doing something to get all possible solved... Happy new year, Regards, ___ 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: 9.1R?
On Wed, 26 Dec 2012 10:17:25 +0900 moto kawasaki wrote: > Official Support of FreeBSD as domU. > # Didn't someone talk about it on this ML ?? or my imagination ?? I've mentioned it. The domU tools scripts are being redesigned to be more platform agnostic and a guy on that team at Citrix has been having me assist him with figuring out how to pull data in the format he needs as there are new features coming to XenServer. It looks like Citrix has interest in FreeBSD because a client wants to do a large deployment, and NetBSD will be easy too. They want these tools to be in FreeBSD ports and NetBSD's pkgsrc, so it will be well integrated with the community and the way the OS already is maintained. It just sounds like Citrix will be pushing patches to the port maintainer in the future (unless they take it over themselves). Overall, things are looking bright for FreeBSD/Xen users. ___ 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: 9.1R?
Jay, I wanted to mention "XenServer Tools", from Citrix, as a part of Official Support of FreeBSD as domU. # Didn't someone talk about it on this ML ?? or my imagination ?? Thank you! jwest> Moto wrote... jwest> >looking forward to FreeBSD 9.1 and Citrix official xen-tool for FreeBSD :-) jwest> jwest> "official" xen support at 9.1 doesn't currently exist. As I understand it... jwest> that's on the drawing board (including dom0 support) for release 10. -- moto kawasaki 090-2464-8454 ___ 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: 9.1R?
Moto wrote... >looking forward to FreeBSD 9.1 and Citrix official xen-tool for FreeBSD :-) "official" xen support at 9.1 doesn't currently exist. As I understand it... that's on the drawing board (including dom0 support) for release 10. ___ 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: 9.1R?
Mark wrote >You're not running XCP or XenServer. That's why you don't have those bugs. Exactly. I can confirm the bugs previously mentioned definitely exist and are 100% reproduceable. ___ 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: 9.1R?
>Also, if you aren't aware, here is my personal list of Xen bugs: - Shutdown via Xen fails to poweroff. It doesn't issue any normal shutdown commands, but tells the Xen code in the kernel to start a shutdown. It's broken on the kernel side. kern/171118 Also, NetBSD's workaround for this is to enable powerd, but we can't when we're running XENHVM and I suspect their powerd is a completely different beast. I can confirm this as a problem as well, on x86 64bit PVM. FreeBSD VM sits at "press any key to reboot". Soon as I press any key, then the VM shuts down. I don't recall why, but something made me think that FreeBSD was responding to a VM shutdown with 'shutdown -h now' when it should be responding with 'shutdown -p now", which seemed to work correctly. - If you use PF with Xen HVM your performance will suck. Known bug. kern/154428 Set net.inet.tcp.tso=0 as a workaround. We don't use PF under Xen, so can't comment. - "Deactivating" a network interface is an option after enabling the xe-guest-utilities scripts. Please don't do that. It seems to cause a panic every time. kern/171138 Also, this happens when you try to change the VLAN assigned to an interface. We have not tried this, good to know. Additional bugs I believe all mentioned here already 1) 64bit PVM won't mount filesystems, after install have to change fstab adpXpY references to adXpY (or something similar, don't have it in front of me). 2) 64bit PVM won't boot with a virtual CD/DVD drive attached, have to remove it from the command line. I know there's other bugs, but the above ones are pretty much show-stoppers for getting freebsd up under XenServer. Fortunately, there's workarounds. Best, Jay West ___ 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: 9.1R?
Thank you very much for your list of bugs. I am running FreeBSD 8.2/9.0 (amd64 XENHVM) on XenServer 5.6SP2/6.0.2/6.1, feld> Also, if you aren't aware, here is my personal list of Xen bugs: feld> feld> - Shutdown via Xen fails to poweroff. It doesn't issue any normal shutdown commands, feld> but tells the Xen code in the kernel to start a shutdown. It's broken on the kernel feld> side. kern/171118 feld> Also, NetBSD's workaround for this is to enable powerd, but we can't feld> when we're running XENHVM and I suspect their powerd is a completely different beast. feld> feld> - If you use PF with Xen HVM your performance will suck. Known bug. feld> kern/154428 feld> Set net.inet.tcp.tso=0 as a workaround. It might be better to disable rxcsum, txcsum, and lro, too. My understanding is the point is the 'NIC hardware' is not the real one but emulation by Xen Host, so that those 'off loading' makes context switch storm between domU and dom0. # please kindly correct me if wrong. feld> - "Deactivating" a network interface is an option after enabling the xe-guest-utilities scripts. feld> Please don't do that. It seems to cause a panic every time. kern/171138 feld> Also, this happens when you try to change the VLAN assigned to an feld> interface. - FreeBSD 9.0 XENHVM panics during boot sequence if it runs on XenServer 6.1. Remove (virtual) CD/DVD drive from guest configuration. http://list-archives.org/2012/10/10/freebsd-xen-freebsd-org/xenbusb_nop_confighook_cb-timeout/f/4227874455 And Yes, I have some experience successful live-migration with those ports. Special Thanks to author! Thank you!! looking forward to FreeBSD 9.1 and Citrix official xen-tool for FreeBSD :-) -- moto kawasaki 090-2464-8454 ___ 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: 9.1R?
You're not running XCP or XenServer. That's why you don't have those bugs. ___ 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: 9.1R?
On 12/22/12 07:29, Mark Felder wrote:
> On Fri, 21 Dec 2012 12:26:36 -0600
> Jay West wrote:
>
>> All our FreeBSD use is now under Xenserver 6.1. I was curious, given the
>> port of xe-guest-utilities that allows online migrations and such. after
>> installing those tools (thus PVM/64), should we be changing our mount points
>> to refer to the xen hd device (xbdX) or continue to use adX inside the VM
>> for filesystem mounts (kinda like we need to change the network device {ex.
>> bgeX} to xnX)? Just looking for a sanity check J
>
> You'll notice that /dev/xbd* doesn't actually exist :-)
>
FWIW:
> Also, if you aren't aware, here is my personal list of Xen bugs:
>
> - Shutdown via Xen fails to poweroff. It doesn't issue any normal shutdown
> commands,
> but tells the Xen code in the kernel to start a shutdown. It's broken on
> the kernel
> side. kern/171118
> Also, NetBSD's workaround for this is to enable powerd, but we can't
> when we're running XENHVM and I suspect their powerd is a completely
> different beast.
>
netbsd-dom0# xm shutdown firewall-2
(xm console firewall-2)
FreeBSD/amd64 (firewall-2.xxx.local) (cuau0)
login: pflog0: promiscuous mode disabled
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...4 4 3 1 1 0 0 done
All buffers synced.
Uptime: 2d13h50m8s
acpi0: Powering system off
root@netbsd-dom0:/usr/pkg/etc/xen/conf#
Works here. But that FreeBSD domU is 10-CURRENT..
9.1-PRERELEASE also works though:
FreeBSD/amd64 (haproxy-2.xxx.local) (cuau0)
login: pflog0: promiscuous mode disabled
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...9 9 7 6 1 1 1 0 0 0 done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
All buffers synced.
Uptime: 2d13h50m0s
acpi0: Powering system off
root@netbsd-dom0:/usr/pkg/etc/xen/conf#
> - If you use PF with Xen HVM your performance will suck. Known bug.
> kern/154428
> Set net.inet.tcp.tso=0 as a workaround.
>
Hmm. I'm running PF on all the FreeBSD domUs and notice no slowdown. The
traffic isn't that much, 1000 states and 300 searches/s (pfctl -si) on
the application servers. The load balancers are slightly higher, 4000
states and 900 searches/s. Still nothing spectacular but again, no problems.
I do remember this being an issue at some point in the past though.
> - "Deactivating" a network interface is an option after enabling the
> xe-guest-utilities scripts.
> Please don't do that. It seems to cause a panic every time. kern/171138
> Also, this happens when you try to change the VLAN assigned to an
> interface.
No idea about this.
___
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: 9.1R?
On Fri, 21 Dec 2012 12:26:36 -0600
Jay West wrote:
> All our FreeBSD use is now under Xenserver 6.1. I was curious, given the
> port of xe-guest-utilities that allows online migrations and such. after
> installing those tools (thus PVM/64), should we be changing our mount points
> to refer to the xen hd device (xbdX) or continue to use adX inside the VM
> for filesystem mounts (kinda like we need to change the network device {ex.
> bgeX} to xnX)? Just looking for a sanity check J
You'll notice that /dev/xbd* doesn't actually exist :-)
Also, if you aren't aware, here is my personal list of Xen bugs:
- Shutdown via Xen fails to poweroff. It doesn't issue any normal shutdown
commands,
but tells the Xen code in the kernel to start a shutdown. It's broken on the
kernel
side. kern/171118
Also, NetBSD's workaround for this is to enable powerd, but we can't
when we're running XENHVM and I suspect their powerd is a completely
different beast.
- If you use PF with Xen HVM your performance will suck. Known bug.
kern/154428
Set net.inet.tcp.tso=0 as a workaround.
- "Deactivating" a network interface is an option after enabling the
xe-guest-utilities scripts.
Please don't do that. It seems to cause a panic every time. kern/171138
Also, this happens when you try to change the VLAN assigned to an
interface.
___
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"
9.1R?
As one of the many that have been delaying a major production rollout in
anticipation of the release of 9.1, I've been anxiously awaiting. No
announcement yet, but I did notice ftp.freebsd.org has an amd64 9.1-Release
iso for download. Given the date of the file as 12/4 I'm a little hesitant
to just jump on it and start building VM's.. Anyone else notice/use this
yet?
All our FreeBSD use is now under Xenserver 6.1. I was curious, given the
port of xe-guest-utilities that allows online migrations and such. after
installing those tools (thus PVM/64), should we be changing our mount points
to refer to the xen hd device (xbdX) or continue to use adX inside the VM
for filesystem mounts (kinda like we need to change the network device {ex.
bgeX} to xnX)? Just looking for a sanity check J
Jay West
EZwind.net
PO Box 460474
Saint Louis, MO 63146
Voice: (314) 262-4143 ext 1000
Toll Free: (866) 343-2589
Fax: (314) 558-9284
jw...@ezwind.net
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential
and is intended exclusively for the person(s) to whom it is addressed. Any
use, copying, retention
or disclosure by any person other than the intended recipient or the
intended recipient's designees
is strictly prohibited. If you are not the intended recipient or their
designee, please notify the
sender immediately by return e-mail and delete all copies.
___
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"
