Except for the consoles petitecloud does it much more smoothly (see thread
on getting linux to run on bhyve on -RELEASE for the script) namely it
should not need conditional logic (instead of being autogenerated on demand)
On Thu, Jan 23, 2014 at 10:44 PM, Craig Rodrigues wrote:
> Hi,
>
> I
Hi,
I put together some scripts for starting a BHyve VM
when a system boots. When the system boots, the console
of the VM uses /dev/nmdm. It is possible to connect
to the console of the VM with: cu -l /dev/nmdm0B
It is a bit rough, but works nicely.
Does someone out there have better scripts
I will have this or something like this encapslated into the petitecloud
run scripts by monday (as well fixing the issues in the other thread)
On Thu, Jan 23, 2014 at 5:20 PM, Jonas Bülow wrote:
> Hi,
>
> I managed to get it working again. I did the last grub step wrong. So, the
> step-by-step
Hi,
I managed to get it working again. I did the last grub step wrong. So, the
step-by-step instructions how to install ubuntu 13.10 are:
kldload vmm
kldload if_tap
kldload bridgestp
kldload if_bridge
ifconfig tap0 create
ifconfig bridge0 create
ifconfig bridge0 up
ifconfig bridge0 addm tap0 addm
The original err=22 sounds like he might of attempted to run as non-root?
On Thu, Jan 23, 2014 at 4:45 PM, Neel Natu wrote:
> Hi Jonas,
>
> On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow
> wrote:
> > I had one working ubuntu13.10 vm instance but I'm unable to reproduce it.
> > When I try to star
Hi Jonas,
On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow wrote:
> I had one working ubuntu13.10 vm instance but I'm unable to reproduce it.
> When I try to start the vm I get:
>
> /usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s
> 2,virtio-blk,./vm/vm1/vm1.img -s 3,virtio-net,tap1 -s
> 4,ah
I had one working ubuntu13.10 vm instance but I'm unable to reproduce it.
When I try to start the vm I get:
/usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s
2,virtio-blk,./vm/vm1/vm1.img -s 3,virtio-net,tap1 -s
4,ahci-cd,./vm/vm1/vm1.iso -S 31,uart,stdio vm1
vm exit[0]
reason V
On Wednesday, January 22, 2014 7:54:47 pm Tycho Nightingale wrote:
>
> Hi,
>
> Interest? Yes! Matter of fact, I have some scraps of 8259 support lying
around here if you are keen to have a starting point.
I think most of 8259A could live in the hypervisor in userland. I think all
that would
On Wednesday, January 22, 2014 9:48:20 pm Neel Natu wrote:
> Hi John,
>
> On Wed, Jan 22, 2014 at 2:15 PM, John Baldwin wrote:
> > Is there any interest in supporting more "legacy" setups via bhyve? In
> > particular, I'd like to take a whack at improving the PCI INTx support, but
> > that can i
Hi Jonas,
On Thu, Jan 23, 2014 at 9:34 AM, Jonas Bülow wrote:
> There is no bhyve process when this happens.
>
I am at a loss to explain this.
Do you happen to have a console log or shell history that may help in
figuring this out?
Even better would be if you can reproduce this and I can debug
There is no bhyve process when this happens.
/j
> 23 jan 2014 kl. 18:07 skrev Neel Natu :
>
> Hi Jonas,
>
>> On Thu, Jan 23, 2014 at 8:00 AM, Jonas Bülow wrote:
>> I will describe the steps when I manage to reproduce the installation.
>> Right now I get stuck with undestroyable vm instances:
>
Hi Jonas,
On Thu, Jan 23, 2014 at 8:00 AM, Jonas Bülow wrote:
> I will describe the steps when I manage to reproduce the installation.
> Right now I get stuck with undestroyable vm instances:
>
> root@bulow:/mnt/bhyve-script # ls /dev/vmm/
>
> lin0
>
> root@bulow:/mnt/bhyve-script # bhyvectl --de
I will describe the steps when I manage to reproduce the installation.
Right now I get stuck with undestroyable vm instances:
root@bulow:/mnt/bhyve-script # ls /dev/vmm/
lin0
root@bulow:/mnt/bhyve-script # bhyvectl --destroy --vm=lin0
errno = 22
On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsj
Could you elaborate what you did to get it working?
On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow wrote:
> Success. I have a working ubuntu 13.10 running under bhyve on FreeBSD
> 10.0-RELEASE.
>
>
>
> /J
>
>
> On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman
> wrote:
>
> >
> >
> >
> > On Thu, Ja
Success. I have a working ubuntu 13.10 running under bhyve on FreeBSD
10.0-RELEASE.
/J
On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman
wrote:
>
>
>
> On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow wrote:
>
>> I do use the precanned bhyve-script "vm0" (if that is what you mean). It
>> explicitl
Yes, but I don't see why the ubuntu installer creates a partition that is
too small. It is too small whatever size I give the vm.
On Thu, Jan 23, 2014 at 3:04 PM, Lars Engels wrote:
> Am 2014-01-23 12:58, schrieb Jonas Bülow:
>
>
> /dev/mapper/c--182--181--143--31--vg-root 960.4M936.1M
Am 2014-01-23 12:58, schrieb Jonas Bülow:
/dev/mapper/c--182--181--143--31--vg-root 960.4M936.1M 0
100% /target
--> The created partition for / is too small.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mai
The commands used are:
#grub-bhyve -r cd0 -m ./vm/lin1/device.map -M 4096 lin1
where device.map is:
#cat vm/lin1/device.map
(hd0) ./vm/lin1/lin1.img
(cd0) ./vm/lin1/lin1.iso
Bhyve is started with:
#/usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s
2,virtio-blk,./vm/lin1/lin1.img -s 3
I connect using ssh to a FreeBSD host and run bhyve. so Alt+Fn is not
applicable. But your idea is applicable. :-)
Running df -h in the "emergency shell" in the ubuntu installer (after it
failed installing the grub bootloader) gives:
~ # df -h
FilesystemSize Used Available U
Am 2014-01-23 11:53, schrieb Jonas Bülow:
FWIW, I extracted the syslog for the failing ubuntu installation. The
failing grub install shows up as:
Jan 23 10:51:08 grub-installer: info: architecture: amd64/generic
Jan 23 10:51:08 in-target: Reading package lists...
Jan 23 10:51:08 in-target: Readi
On Thu, Jan 23, 2014 at 5:53 AM, Jonas Bülow wrote:
> FWIW, I extracted the syslog for the failing ubuntu installation. The
> failing grub install shows up as:
>
Thanks does not help me immediately (might help someone else) but it will
be very helpful over the next few days to a week as we add l
FWIW, I extracted the syslog for the failing ubuntu installation. The
failing grub install shows up as:
Jan 23 10:51:08 grub-installer: info: architecture: amd64/generic
Jan 23 10:51:08 in-target: Reading package lists...
Jan 23 10:51:08 in-target: Reading package lists...
Jan 23 10:51:08 in-targe
On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow wrote:
> I do use the precanned bhyve-script "vm0" (if that is what you mean). It
> explicitly mentions linux support. bhyveload can't be user for other images
> than FreeBSD so I don't know how to use your script for a linux OS
>
Since I have not use
I do use the precanned bhyve-script "vm0" (if that is what you mean). It
explicitly mentions linux support. bhyveload can't be user for other images
than FreeBSD so I don't know how to use your script for a linux OS.
I assume the image is file backed as I have not assigned a dedicated
partition to
Sorry for the repost
I am currently attempting to import a linux instance into bhyve via
petitecloud but here is the script that PC would generate for such a
instance tell me if something like it works: (just replace the mentions of
freebsd with linux ones):
#!/bin/sh
pw lock petitecloud
truncat
-- Forwarded message --
From: Aryeh Friedman
Date: Thu, Jan 23, 2014 at 4:38 AM
Subject: Re: Linux on BHyVe in 10.0-RELEASE
To: Jonas Bülow
Try:
truncat --size 10G disk.img
bhyve -d disk.img
On Thu, Jan 23, 2014 at 4:37 AM, Jonas Bülow wrote:
> I tried to run from an US
I tried to run from an USB drive with a standard file backend (non ZFS?).
Mounted as:
/dev/da5p1 on /mnt (ufs, local, soft-updates)
Installation of ubuntu still fails when trying to install the grub
bootloader.
/J
On Thu, Jan 23, 2014 at 9:58 AM, Aryeh Friedman wrote:
> Does using the standa
Does using the standard file backed bhye work?
On Thu, Jan 23, 2014 at 3:56 AM, Jonas Bülow wrote:
> fwiw, I do not have any /dev/zvol in the host. I'm using a vanilla FreeBSD
> 10.0-Release install using ZFS.
>
> /J
>
>
> On Thu, Jan 23, 2014 at 9:24 AM, Michael Dexter
> wrote:
>
> >
> > Here'
fwiw, I do not have any /dev/zvol in the host. I'm using a vanilla FreeBSD
10.0-Release install using ZFS.
/J
On Thu, Jan 23, 2014 at 9:24 AM, Michael Dexter
wrote:
>
> Here's what I've found so far:
>
> vmrun.sh does not like zvols and I am hoping for:
>
> sh vmrun.sh -m 1024 -d /dev/zvol/zroo
I am currently playing with it but from the above I suspect the issue is
attempting to use a zvol what happens if you go direct like for example
/vms/pri/ (sorry for using petitecloud notatoin but XXX being the
location of the raw disk) it should work... I do know when I was playing
with QEMU b
> So, the conclusion is that it's not possible to run Linux on bhyve
running on 10.0-RELEASE ?
Not at all - there have been lots of reports of it working.
It is known that there is a problem with using zvols for guest images,
though this is related to GEOM and not specific to bhyve.
We j
So, the conclusion is that it's not possible to run Linux on bhyve running
on 10.0-RELEASE ?
/J
On Thu, Jan 23, 2014 at 9:24 AM, Michael Dexter
wrote:
>
> Here's what I've found so far:
>
> vmrun.sh does not like zvols and I am hoping for:
>
> sh vmrun.sh -m 1024 -d /dev/zvol/zroot/vm3 vm3
>
Here's what I've found so far:
vmrun.sh does not like zvols and I am hoping for:
sh vmrun.sh -m 1024 -d /dev/zvol/zroot/vm3 vm3
It gets as far as:
Writing partition tables [In Progress ]
Initializing ada0p2[ Failed ]
I am trying to figure out wh
33 matches
Mail list logo