Re: Virtualization of FreeBSD
On Fri, 08 Jun 2007 22:47:42 +0300
Thanos Rizoulis <[EMAIL PROTECTED]> wrote:
> One serious tip about Vmware, is that when selecting disks, you can
> select a *physical* disk instead of a virtual and proceed with
> installation on that physical disk. Or you can keep a freebsd server
> installed on a virtual disk, then connect a physical disk on the same VM
> and dump/restore as you please. It has been tested with over 7GB OS
> installs and works like a charm.
cool, i knew about using the physical disk option, but hadn't used it for
restore/dump :)
thx
_
{Beto|Norberto|Numard} Meijome
"Quality is never an accident, it is always the result of intelligent effort."
John Ruskin (1819-1900)
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
O/H Norberto Meijome έγραψε: you mean problems with the lnc0 , as seen by FBSD in the VM? interesting, i've never had any problems, but I run VMWare server under Centos 4. I'll give the e1000 a try :) thx for the tip. send any mail to "[EMAIL PROTECTED]" Under various versions of vmware, lnc0 just choked and caused disconnection under the first few seconds in a simple stress situation (eg a 4MB file transfer over SSH, or some equal samba file transfer). The em driver was the solution to all these problems. If I remember correctly, selecting a x64 edition of guest OS or selecting 2 CPU cores, provides you directly with em instead of lnc. My opinion about MS virtual PC is that it gave me the once in a lifetime opportunity to capture a full BSOD in bitmap file. I put it as a desktop in a public PC, and laughed as everyone kept pressing Ctrl-Alt-Del. I dumped MS virtual PC shortly after. One serious tip about Vmware, is that when selecting disks, you can select a *physical* disk instead of a virtual and proceed with installation on that physical disk. Or you can keep a freebsd server installed on a virtual disk, then connect a physical disk on the same VM and dump/restore as you please. It has been tested with over 7GB OS installs and works like a charm. -- RTFM and STFW before anything bad happens _ Thanos Rizoulis Electronic Computing Systems Engineer Larissa, Greece FreeBSD/PCBSD user ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
Norberto Meijome wrote:
On Wed, 6 Jun 2007 21:18:16 -0400
"Maxim Khitrov" <[EMAIL PROTECTED]> wrote:
You mean the info in general, or the e1000 part? I never had any
errors in my Windows sys log. However, if you use the default network
adapter you will have problems. I don't remember what the exact error
is, but I remember that when downloading the ports tree, for example,
it will periodically interrupt the transfer. Something about dropped
packets, or something else like that. Never had problems with e1000,
but the network only seems to perform at about 1/2 of what the host OS
can handle.
you mean problems with the lnc0 , as seen by FBSD in the VM? interesting, i've
never had any problems, but I run VMWare server under Centos 4.
I'll give the e1000 a try :) thx for the tip.
_
{Beto|Norberto|Numard} Meijome
"It is not the strongest of the species that survive, nor the most intelligent,
but the one most responsive to change." Charles Darwin.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
FYI:
The em driver will only be getting better in 6.x soon, because
there's going to be a backport from CURRENT taking place in the near future.
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
On Wed, 6 Jun 2007 21:18:16 -0400
"Maxim Khitrov" <[EMAIL PROTECTED]> wrote:
> You mean the info in general, or the e1000 part? I never had any
> errors in my Windows sys log. However, if you use the default network
> adapter you will have problems. I don't remember what the exact error
> is, but I remember that when downloading the ports tree, for example,
> it will periodically interrupt the transfer. Something about dropped
> packets, or something else like that. Never had problems with e1000,
> but the network only seems to perform at about 1/2 of what the host OS
> can handle.
you mean problems with the lnc0 , as seen by FBSD in the VM? interesting, i've
never had any problems, but I run VMWare server under Centos 4.
I'll give the e1000 a try :) thx for the tip.
_
{Beto|Norberto|Numard} Meijome
"It is not the strongest of the species that survive, nor the most intelligent,
but the one most responsive to change." Charles Darwin.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
Le 07/06/2007 à 00:09:31-0400, [EMAIL PROTECTED] a écrit > At 07:45 PM 6/6/2007, Sean Murphy wrote: > > Is anyone running virtualization of FreeBSD servers on VMware or other > > virtualization software? What experiences have you had, good or bad? > > Been wanting to ask the same... I've heard of virt' software for some time > but didn't realize what it could really do. Then on a tip, I started > playing with micros$$ts Virtual PC a couple weeks ago. Wow! It runs > windoze 2000 and FreeBSD apparently fine on a windoze 2000 host. In the > last couple weeks I've been doing a lot of experimentation with FreeBSD and > Samba and windoze that I've been procrastinating about for lack of a spare > box to run things on. Very impressive for free stuff from the evil empire > :) > > But from what I've heard, VMware has better performance. And there are some > things in ports (qemu?) also. For my purposes Billy's product is working > well, but I'd like to hear of better things, esp those that run on windoze, > which I'm stuck with for my desktop boxen. > >From many years I've running perfectly many FreeBSD guest on a vmware-linux host. I've no problem. Every thing is rock-stable. Something you need to known : 1/ vmware (and Virtual PC) said there Virtual System can run any x86 OS. It's not true. Sometime you need a new version of vmware-software to run a new version of the Linux/FreeBSD. 2/ vmware have release a free version of vmware-server, try and you can known ;-) 3/ vmware software run on Linux/Windows, but the guest can be «anything» (see point 1) 4/ You loose only 5-10% on CPU performance on a guest. 5/ You loose much much more on the I/O disk performance, for production it's good idea to have a very high speed disk on the host. In my point of vue vmware is very fine thing for running many OS (different) on same computer. If you want run only FreeBSD, you can use jail technologie (man jail) it's very different technics (you have only one kernel for many instance of FreeBSD). Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Jeu 7 jui 2007 10:29:34 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
[EMAIL PROTECTED] wrote: At 07:45 PM 6/6/2007, Sean Murphy wrote: Is anyone running virtualization of FreeBSD servers on VMware or other virtualization software? What experiences have you had, good or bad? Been wanting to ask the same... I've heard of virt' software for some time but didn't realize what it could really do. Then on a tip, I started playing with micros$$ts Virtual PC a couple weeks ago. Wow! It runs windoze 2000 and FreeBSD apparently fine on a windoze 2000 host. In the last couple weeks I've been doing a lot of experimentation with FreeBSD and Samba and windoze that I've been procrastinating about for lack of a spare box to run things on. Very impressive for free stuff from the evil empire :) But from what I've heard, VMware has better performance. And there are some things in ports (qemu?) also. For my purposes Billy's product is working well, but I'd like to hear of better things, esp those that run on windoze, which I'm stuck with for my desktop boxen. -RW The pecking order works like so IMHO under Windows: 1. VMWare. 2. M$ VPC. 3. Qemu. -Vmware has the best performance overall from what I've seen, and has 64-bit support on 64-bit processors, so it wins hands down. -M$ VPC has better performance than Qemu from what I've seen, but only has 32-bit support, so that's out. -Getting Qemu started on Windows (at least for me), was a pain in the a$$. I eventually gave up because it was so slow and the hardware virtualization wasn't that great. I run CURRENT and 6.2-RELEASE on my desktop under Windows because hardware support for all my devices isn't quite there yet, and for development. It's ok, except when I do CPU intensive tasks, where the virtual CPU clock per VM skews a lot/slows down, and this screws up shutting down the VMs (they get stuck before FS syncing's started). Solution is to run ntpdate before shutdown, to update the VM time. I'm running VMware server on XP x64 with 4GB of RAM and a Core 2 Duo 6700 CPU. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
At 07:45 PM 6/6/2007, Sean Murphy wrote: Is anyone running virtualization of FreeBSD servers on VMware or other virtualization software? What experiences have you had, good or bad? Been wanting to ask the same... I've heard of virt' software for some time but didn't realize what it could really do. Then on a tip, I started playing with micros$$ts Virtual PC a couple weeks ago. Wow! It runs windoze 2000 and FreeBSD apparently fine on a windoze 2000 host. In the last couple weeks I've been doing a lot of experimentation with FreeBSD and Samba and windoze that I've been procrastinating about for lack of a spare box to run things on. Very impressive for free stuff from the evil empire :) But from what I've heard, VMware has better performance. And there are some things in ports (qemu?) also. For my purposes Billy's product is working well, but I'd like to hear of better things, esp those that run on windoze, which I'm stuck with for my desktop boxen. -RW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
On 6/6/07, Mikel King <[EMAIL PROTECTED]> wrote: > On 6/6/07, Sean Murphy <[EMAIL PROTECTED]> wrote: >> Is anyone running virtualization of FreeBSD servers on VMware or >> other >> virtualization software? What experiences have you had, good or bad? > > At home I run have several FreeBSD installs running on Windows 2003 > VMWare Server. The only reason I'm doing this is because FreeBSD > doesn't support my raid controller, so I'm stuck with windows. > > Overall it works fine. However, you do have terrible disk (and to a > lesser extent network) performance. I use these installs mostly for > developing and testing software, so it's not a big deal for me. Here > are a few tips for getting the most out of a FreeBSD server on VMWare > (this is for Windows only): > > - If you have enough memory, add prefvmx.minVmMemPct = "100" and > prefvmx.useRecommendedLockedMemSize = "TRUE" to VMWare config.ini (App > Data under All Users). That will keep all the VM memory in ram instead > of swapping it to the disk. The rest of the settings go into your > FreeBSD.vmx file. > > - Disable named memory file: mainMem.useNamedFile = "FALSE" > > - Disable page sharing: sched.mem.pshare.enable = "FALSE" > > - Disable memory trimming: MemTrimRate = "0" > > - Be sure to use Intel gigabit network adapter: > ethernet0.virtualDev = "e1000" > > In previous versions of VMWare Server you had to configure your > kern.hz sysctl to be 100. Otherwise your clock would run very slow. I > think they fixed it in the latest version, but just keep that in mind. > > Disk performance is quite bad. For example, doing a full extract of > the ports tree takes my server around 16 minutes. On my old laptop > with a crappy hard drive it takes only 8 or so minutes. So that's > something to keep in mind, you're not going to be able to use VMs as a > file server. For most other uses it works fine. > > - Max Maxim, Thanks for this useful info. Where ever did you come across this? Ever observe any oddities in the Windows SysLogs regarding LAN adapter errors? Cheers, Mikel You mean the info in general, or the e1000 part? I never had any errors in my Windows sys log. However, if you use the default network adapter you will have problems. I don't remember what the exact error is, but I remember that when downloading the ports tree, for example, it will periodically interrupt the transfer. Something about dropped packets, or something else like that. Never had problems with e1000, but the network only seems to perform at about 1/2 of what the host OS can handle. Most of those configuration options I just gathered over time of reading the VMWare forums, people's blogs, and other places. The disk problem is the only one I couldn't find a decent solution to. I tried using IDE and SCSI disks, but the results are the same. If you read the release notes for VMWare Server, you'll notice that they actually don't claim FreeBSD 6.2 or 6.1 support, only 6.0. I never tested 6.0, but I get the feeling that FreeBSD is in general not very high on VMWare's to-support list. Maybe in the future they'll improve things. Oh one more thing I forgot to mention. After you install FreeBSD, install perl5.8 and then the VMWare tools. That will let you do a clean shutdown of the system by using the off button on VMWare console (more useful when the host OS is going down). However, the script that comes by default with VMWare tools doesn't actually power down the machine. Instead it does shutdown -h, so the thing keeps running. To fix this, open /usr/local/etc/rc.d/vmware-tools.sh, do a search for '--background' and on the next line add '--halt-command "/sbin/shutdown -p now"'. That will allow the VM to properly shutdown. Keep in mind that because VMWare tools depend on the /proc system to know when it is running, doing things like `vmware-tools.sh status` will not give you accurate information. Instead use `top` to make sure 'vmware-guestd' is in there. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
On Wednesday 06 June 2007 19:11:16 Maxim Khitrov wrote: > On 6/6/07, Sean Murphy <[EMAIL PROTECTED]> wrote: > > Is anyone running virtualization of FreeBSD servers on VMware or other > > virtualization software? What experiences have you had, good or bad? > > At home I run have several FreeBSD installs running on Windows 2003 > VMWare Server. The only reason I'm doing this is because FreeBSD > doesn't support my raid controller, so I'm stuck with windows. > > Overall it works fine. However, you do have terrible disk (and to a > lesser extent network) performance. I use these installs mostly for > developing and testing software, so it's not a big deal for me. Here > are a few tips for getting the most out of a FreeBSD server on VMWare > (this is for Windows only): > > - If you have enough memory, add prefvmx.minVmMemPct = "100" and > prefvmx.useRecommendedLockedMemSize = "TRUE" to VMWare config.ini (App > Data under All Users). That will keep all the VM memory in ram instead > of swapping it to the disk. The rest of the settings go into your > FreeBSD.vmx file. > > - Disable named memory file: mainMem.useNamedFile = "FALSE" > > - Disable page sharing: sched.mem.pshare.enable = "FALSE" > > - Disable memory trimming: MemTrimRate = "0" > > - Be sure to use Intel gigabit network adapter: ethernet0.virtualDev = > "e1000" > > In previous versions of VMWare Server you had to configure your > kern.hz sysctl to be 100. Otherwise your clock would run very slow. I > think they fixed it in the latest version, but just keep that in mind. > > Disk performance is quite bad. For example, doing a full extract of > the ports tree takes my server around 16 minutes. On my old laptop > with a crappy hard drive it takes only 8 or so minutes. So that's > something to keep in mind, you're not going to be able to use VMs as a > file server. For most other uses it works fine. > > - Max > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" i too used to run 4 FreeBSDs in VMware server, they ran great for me, i ran 2 DNS servers, an apache server, and a sendmail server. performance was acceptable. my VMware host was suse 10.1. sean, you might also take a look at jails for freebsd. conceptually, its a lot like virtualization, altho it does have its differences. once you get your jails up and running, you really wouldnt know the difference, and performance is basically as fast as the host computer can go. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Virtualization of FreeBSD
On 6/6/07, Sean Murphy <[EMAIL PROTECTED]> wrote: Is anyone running virtualization of FreeBSD servers on VMware or other virtualization software? What experiences have you had, good or bad? At home I run have several FreeBSD installs running on Windows 2003 VMWare Server. The only reason I'm doing this is because FreeBSD doesn't support my raid controller, so I'm stuck with windows. Overall it works fine. However, you do have terrible disk (and to a lesser extent network) performance. I use these installs mostly for developing and testing software, so it's not a big deal for me. Here are a few tips for getting the most out of a FreeBSD server on VMWare (this is for Windows only): - If you have enough memory, add prefvmx.minVmMemPct = "100" and prefvmx.useRecommendedLockedMemSize = "TRUE" to VMWare config.ini (App Data under All Users). That will keep all the VM memory in ram instead of swapping it to the disk. The rest of the settings go into your FreeBSD.vmx file. - Disable named memory file: mainMem.useNamedFile = "FALSE" - Disable page sharing: sched.mem.pshare.enable = "FALSE" - Disable memory trimming: MemTrimRate = "0" - Be sure to use Intel gigabit network adapter: ethernet0.virtualDev = "e1000" In previous versions of VMWare Server you had to configure your kern.hz sysctl to be 100. Otherwise your clock would run very slow. I think they fixed it in the latest version, but just keep that in mind. Disk performance is quite bad. For example, doing a full extract of the ports tree takes my server around 16 minutes. On my old laptop with a crappy hard drive it takes only 8 or so minutes. So that's something to keep in mind, you're not going to be able to use VMs as a file server. For most other uses it works fine. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Virtualization of FreeBSD
Is anyone running virtualization of FreeBSD servers on VMware or other virtualization software? What experiences have you had, good or bad? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
