Re: freebsd guest on azure
On 2019-03-23 18:57, tech-lists wrote: On Sat, Mar 23, 2019 at 09:31:17PM +0800, Frank Leonhardt wrote: As to your question, what I've done is run a ZFS pool and simply send a snapshot. That's a good idea. I presumed I'd be stuck just with UFS. My most favoured way of doing this is having a zfs-vol backed vm on a freebsd host but it's not my choice. I can't remember now if I made it boot from ZFS as I prefer to boot from UFS this is me. I like to boot off something fast and simple. and use ZFS for the rest. But I think I did this with Azure exactly because I wanted to copy the disk around. It was early last year so you can't quite me on it. If you're not sure about sending datasets on ZFS then ask. Yes please how are you invoking sending a dataset in this context? For example, are you using compression for the data stream? If so, what sort? Is there anything else pertinent to the azure context when using zfs send? I have a nagging feeling that Azure insisted on its version of FreeBSD and did not install from a normal CD image. But even if this was the case, it could be different now. If it did I would have attached another vdisk for the zpool, but it means you can't transfer the OS partition. However, I don't want to do this anyway... Now I run everything in a jail, which means that the OS partition contains nothing but the base OS. I just move the jail to another host and run it there. This is also a great way of getting several VMs whilst only paying for one. So I'm only moving the dataset with the jail on it. Your friend here is the "zfs send" command. For obvious reasons (on a running system) you need to take and send a snapshot. The send command serializes the dataset and sends it to stdout (but not if it's a tty, as that would be silly). zfs recv does the opposite. You can copy datasets with something like zfs send z/test@today | zfs recv junk/foo if you want to send it to another host, use ssh. To be precise: zfs send z/test@today | ssh anotherhost zfs recv junk/foo One annoying feature was that data used to be decompressed and re-compressed on a send. You could then pipe it through compress if you wanted to save WAN bandwidth. However, since 11.2 (and 12.0) a --compressed option has appeared, which leaves the data in the state it was stored. This relies on the zpool on the other end supporting the same compression method, so I've not used this in anger yet. Using lz4 compression is normally no-brainer. Regards, Frank. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: freebsd guest on azure
On 23 March 2019 20:54:15 GMT+08:00, tech-lists wrote: >Hi, > >If you're running a freebsd instance on azure, > >1. can you back up the instance > >-without azure's own tools >-or with azures own tools (and I imagine it costs extra) > >2. or if you can't directly back up the instance, apart from tarring up >the directories you need to keep and downloading them from the >instance, >what do you do? First off, if I'm doing this on Azure then someone with deep pockets and a Microsoft fixation is paying. I thought I'd make that clear! As to your question, what I've done is run a ZFS pool and simply send a snapshot. I can't remember now if I made it boot from ZFS as I prefer to boot from UFS and use ZFS for the rest. But I think I did this with Azure exactly because I wanted to copy the disk around. It was early last year so you can't quite me on it. If you're not sure about sending datasets on ZFS then ask. Regards, Frank. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: The status of docker
On 19 January 2019 15:31:11 GMT, Rainer Duffner wrote: > > >> Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : >> >> Has this project been completed and now only needs testing, or has it >been abandoned, or maybe the approach has changed and I am looking in a >wrong place? > > > > >AFAIK, it’s dead. > >Docker is a Linux-thing. > >Your best bet is to run Linux in bhyve. > IIRC there have been two projects to port docker. One was using jails for containerisation, the other was doing it the Linux way somehow. Given the way Docker is used (for running downloaded preconfigured binary containers) that it's not really a BSD ethos thing. Anyway, both Docker ports stopped. Docker is a moving target, and I think that had a lot to do with it. As Duffner said - bhyve. It you're containerising BSD applications just unpack a tarball into a jail. Unless you want K8S functionally. Last time I looked there was nothing doing on that front. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Xen on FreeBSD 11.1 - Auto creating VMs on boot
On 02/02/2018 17:14, David Salvisberg wrote: Hello, I recently switched from Debian as my Dom0 to FreeBSD to make use of ZFS without having to rely on zfs-on-linux. The experience has been pretty good so far, albeit a bit more limited compared to Debian obviously. One of the things I haven't been able to figure out is /etc/xen/auto or rather /usr/local/etc/xen/auto in FreeBSDs case. It doesn't look like Xen on FreeBSD ships with any of the configuration options for this feature, possibly due to lack of support for save and restore. I don't really need save and restore but auto spawning VMs on boot would be a nice thing to be able to do without having to write my own rc.d script or something along those lines. Is there a way to make use of the auto creation feature on FreeBSD Xen or is that feature just missing entirely due to the lack of save/restore functionality? If there is no builtin way, I'd appreciate any recommendations for writing my own scripts to make sure that they're only being run after Xen has been fully initialized and is ready for xl create commands. Best Regards David Salvisberg ___ Hi David, I'm not using Xen right now and I'm afraid I can't remember - which means it can't have been an issue. The easy way to kick of something on boot is the traditional "/etc/rc.local" script. Automation "enthusiasts" like to complicate things and are a bit disparaging of this simple way of running whatever you want on startup. The file probably doesn't even exist on your system. So create it. The contents will look something like: cd /usr/something/my-xen-configs xl create somemachine.cfg xl create someothermachine.cfg xl create yetanothermachine.cfg echo All done! This assumes xl is on the search path of the environment when rc.local is run. I never assume, so I'd use the full path to "xl". Avoid unexpected results! This is a normal shell script, so you can do more complex things like: for vm in `ls /usr/something/my-xen-configs` ; do xl create $vm ; done But this is getting dangerously close to automation ;-) Regards, Frank. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: How to setup graphical Linux vm in bhyve ? Continued from (Re: A question about VirtualBox USB support)
I'm not a fan of virtualization except as a last resort when a chroot/jail/zone doesn't cut it. So I'm not necessary the best person to ask. My guess is that you have a problem with your virtual BIOS image or possibly GRUB. I think I've had CentOS 7 running on Bhyve (could have been Xen) using VNC but it took forever to boot, and gave me little pleasure. What machine definition are you using? The config for Windoze wasn't the same IIRC. Change the VGA card and definitely the IDE driver hardware. Not AHCI. I can't remember the exact twist. Regards, Frank. -- Sent from my Cray X/MP with small fiddling keyboard. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Windows XP and Xen -Mouse Trouble
Does anyone happen to know what's causing this? Windows XP original release (i.e. SP zero) is fine (connecting using VNC). As soon as you install SP2: 1) Windows Hardware Mangler shows two mice - a PS/2 and a QEMU HID compatible one. 2) There's a mystery PCI device. 3) After a few seconds the mouse pointer sticks. If you disable and enable the QEMU mouse it comes back for a few (~30) seconds and sticks again. (There's no option to disable the PS/2 one). It feels like Plug and Pray "finds" it and screws it up again. 4) SP3 doesn't fix it. I haven't tried it with SP1. Fortunately the keyboard is fine and I'm used to using that for most things anyway. It's bugging me - does anyone know what I need to enable/disable and how? Thanks, Frank. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Any support creating a Windows Server 2012 unattended install
On 13/07/2017 09:35, Harry Schmalzbauer wrote: Bezüglich Paul Webster's Nachricht vom 13.07.2017 10:22 (localtime): Ah ha we can now see installs, perfect thank you harry! just what I needed I thought we still had no way of seeing the install process You can run anything that provides a UEFIx64 loader with VNC-graphics, due to the ongoing effort of many bhyve developers. Thank goes to them! I'll second that! I wish I'd known this 18 months ago (but then it wasn't available then). Does you know if it works with OS/2 and Windows XP/98? ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Any support creating a Windows Server 2012 unattended install
On 13/07/2017 09:07, Paul Webster via freebsd-virtualization wrote: Or alternatively any of you guys have one that I can use? I was following https://wiki.freebsd.org/bhyve/Windows but I can not seem to get it to work; though it may be because I had to convert the 'install.esd' file to 'install.wim' as the disk does not have one. If I just the ISO I ended up creating in virtualbox it just seems to go into a standard install, but that might be because it detected a graphics adapter. FWIW I gave up on that game. I now create VMs with vbox in headless mode using a VNC viewer somewhere else on the network. But my requirements are (possibly) different - I often need to run them under ESX, but getting them running with bhyve is "interesting". I also want to run specific older versions of Windoze (and OS/2). I can't imagine why I'd want to run a current Microsoft Server ;-) ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows XP
On 22/02/2017 18:58, Peter Grehan wrote: Hi Frank, bhyve doesn't support anything older than Vista, That's correct, though I'm hoping to support XP and Server 2003 at some point. and I'm unclear as to whether it supports 32-bit versions of that. It doesn't, nor any 32-bit version of Windows after that, mainly since they require BIOS and not all the support is there in the UEFI/CSM BIOS emulation. As above, hoping to rectify that at some point. later, Thanks for that. Virtualbox is is then, for now. Although I could probably run Windows 7-64 Windows XP Mode to get DOS running! I'll push ahead with the compilation (don't use packages. and even then with X it gets a bit crazy and out of comfort zone). Regards, Frank. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Windows XP
Can anyone help me running Windows 5.1 (XP) as a VM under FreeBSD? bhyve doesn't support anything older than Vista, and I'm unclear as to whether it supports 32-bit versions of that. I tried compiling Virtualbox a while back, but after a few days it was still going so I put it on the back burner. It wasn't clear how I'd get a Windows XP image on it anyway. So what's the best way to do this? I need it to run various Windows 32-bit utilities, USB related (e.g. dongle servers, USB connected hardware ). I do have site-licensed Windows XP disks. Not to mention DOS software! Thanks, Frank. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
