Hi,
Ok, I seem to have sent an earlier and not-well-though-out version of
the patch - attaching the correct one now (I dug into this a couple of
months ago and needed some time to remember the details). I tried it
with your test setup and - module loads/unloads cleanly, but will
freeze the vbox Fr
On Thu, Feb 6, 2014 at 7:59 PM, Juergen Lock wrote:
> On Thu, Feb 06, 2014 at 05:16:15PM +0200, Shteryana Shopova wrote:
>> Hi all,
>>
>> Sorry for top posting but I'm new to the list and came across this
>> thread while playing with bhyve these days. To apply the patch -
>>
>> #cp patch-unit3mino
On Thu, Feb 06, 2014 at 05:16:15PM +0200, Shteryana Shopova wrote:
> Hi all,
>
> Sorry for top posting but I'm new to the list and came across this
> thread while playing with bhyve these days. To apply the patch -
>
> #cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/
>
> compile an
Hi all,
Sorry for top posting but I'm new to the list and came across this
thread while playing with bhyve these days. To apply the patch -
#cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/
compile and install the module.
I've been running kqemu under current with the attached patc
>
> I use bare grub-bhyve/bhyve/bhyvectl, wrapped in a shell script in the
> manner of vmrun.sh, although fitted to my needs, nothing special. I
> didn't have a chance to use petitecloud yet.
>
>
Got it worked out and after a fix a few other small bugs (like the webui
start/stop working inconsisten
2014-01-29 Aryeh Friedman :
>
>
>
> On Tue, Jan 28, 2014 at 11:56 PM, Aryeh Friedman
> wrote:
>>
>> Where did you get the orignial starter script for this from was it from
>> vmrun or the petitecloud sample script I posted... 2 reasons for asking:
>>
>> 1. It is turning out to be annoying inflexib
On Tue, Jan 28, 2014 at 11:56 PM, Aryeh Friedman
wrote:
> Where did you get the orignial starter script for this from was it from
> vmrun or the petitecloud sample script I posted... 2 reasons for asking:
>
> 1. It is turning out to be annoying inflexible in-terms of the values of
> various parame
Where did you get the orignial starter script for this from was it from
vmrun or the petitecloud sample script I posted... 2 reasons for asking:
1. It is turning out to be annoying inflexible in-terms of the values of
various parameters (I can compensate for most of this in my personal
playing wit
2014-01-28 Aryeh Friedman :
> Seems like it is a processor motherboard combo thing (see other thread)
>
ah, ok. good to know :)
--
Markiyan.
>
> On Sun, Jan 26, 2014 at 9:26 AM, Markiyan Kushnir
> wrote:
>>
>> yes, once I posted it I realized that these sysctls are not relevant
>> at this stage
Seems like it is a processor motherboard combo thing (see other thread)
On Sun, Jan 26, 2014 at 9:26 AM, Markiyan Kushnir <
markiyan.kush...@gmail.com> wrote:
> yes, once I posted it I realized that these sysctls are not relevant
> at this stage.
>
> There was a segfault, was that bhyvectl? May
yes, once I posted it I realized that these sysctls are not relevant
at this stage.
There was a segfault, was that bhyvectl? May be it makes sense for
someone (a bhyve dev) to inspect it?
--
Markiyan.
2014-01-26 Aryeh Friedman :
>
>
>
> On Sun, Jan 26, 2014 at 8:46 AM, Markiyan Kushnir
> wrote
# uname -a
FreeBSD ishtar 10.0-STABLE FreeBSD 10.0-STABLE #0 r261180: Sun Jan 26
08:18:07 EST 2014 root@ishtar:/usr/obj/usr/src/sys/GENERIC amd64
On Sun, Jan 26, 2014 at 8:48 AM, Markiyan Kushnir <
markiyan.kush...@gmail.com> wrote:
> the host built out of revision:
>
> 15:45:test-bhyve# u
On Sun, Jan 26, 2014 at 8:46 AM, Markiyan Kushnir <
markiyan.kush...@gmail.com> wrote:
> hmm...
>
> 15:45:test-bhyve# md5 ubuntu-12.04.3-server-amd64.iso
> MD5 (ubuntu-12.04.3-server-amd64.iso) = 2cbe868812a871242cdcdd8f2fd6feb9
>
# md5 ubuntu/ubuntu.iso
MD5 (ubuntu/ubuntu.iso) = 2cbe868812a87124
also check out these sysctls:
net.link.tap.user_open: 0 -> 1
net.link.tap.up_on_open: 0 -> 1
2014-01-26 Markiyan Kushnir :
> the host built out of revision:
>
> 15:45:test-bhyve# uname -a
> FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0
> r260573: Mon Jan 13 08:05:15 UTC 2014
> r.
the host built out of revision:
15:45:test-bhyve# uname -a
FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0
r260573: Mon Jan 13 08:05:15 UTC 2014
r...@vm0.mkushnir.mooo.com:/work/obj/work/src.svnup/sys/MAREK amd64
2014-01-26 Markiyan Kushnir :
> hmm...
>
> 15:45:test-bhyve# md5 ub
hmm...
15:45:test-bhyve# md5 ubuntu-12.04.3-server-amd64.iso
MD5 (ubuntu-12.04.3-server-amd64.iso) = 2cbe868812a871242cdcdd8f2fd6feb9
2014-01-26 Aryeh Friedman :
> # ls
> ubuntu.iso
> # kldstat
> Id Refs AddressSize Name
> 17 0x8020 16167b0 kernel
> 21 0xf
# ls
ubuntu.iso
# kldstat
Id Refs AddressSize Name
17 0x8020 16167b0 kernel
21 0x81a12000 2a44 uhid.ko
31 0x81a15000 34d3 ums.ko
# kldload vmm
# kldload if_tap
# kldload bridgestp
# kldload if_bridge
# ifconfig tap0 create
# ifconf
what did you mean by "touch the cd"?
--
Markiyan.
2014-01-26 Aryeh Friedman :
>
>
>
> On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir
> wrote:
>>
>> 2014/1/26 Aryeh Friedman :
>> >> mkdir ubuntu
>> >> ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
>> >> create the file ubuntu/
2014-01-26 Aryeh Friedman :
>
>
>
> On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir
> wrote:
>>
>> 2014/1/26 Aryeh Friedman :
>> >> mkdir ubuntu
>> >> ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
>> >> create the file ubuntu/device.map with the following content (2 lines):
>> >
On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir <
markiyan.kush...@gmail.com> wrote:
> 2014/1/26 Aryeh Friedman :
> >> mkdir ubuntu
> >> ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
> >> create the file ubuntu/device.map with the following content (2 lines):
> >> (hd0) ./ubuntu
2014/1/26 Aryeh Friedman :
>> mkdir ubuntu
>> ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
>> create the file ubuntu/device.map with the following content (2 lines):
>> (hd0) ./ubuntu/ubuntu.img
>> (cd0) ./ubuntu/ubuntu.iso
>>
>> truncate -s 8G ubuntu/ubuntu.img
>>
>> grub-bhyve -
> mkdir ubuntu
> ...fetch ubuntu13.10 iso image and put it in ubuntu/ubuntu.iso
> create the file ubuntu/device.map with the following content (2 lines):
> (hd0) ./ubuntu/ubuntu.img
> (cd0) ./ubuntu/ubuntu.iso
>
> truncate -s 8G ubuntu/ubuntu.img
>
> grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048
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
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
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
Yes, if "using zvol" is the same thing as using ZFS for the guest image.
I tried setting DEVTYPE to "" with the same result.
/J
On Thu, Jan 23, 2014 at 8:16 AM, Peter Grehan wrote:
> Hi Jonas,
>
>
> Installation starts and everything looks good until it tries to install
>> the
>> grub boot l
Hi Jonas,
Installation starts and everything looks good until it tries to install the
grub boot loader. That last step fails. Exiting the installer and running:
#sh lin1 start
Gives a grub prompt.
Any hints?
Are you using a zvol for the guest disk image ?
later,
Peter.
___
Hi.
I tried to create an ubunto13.10 image using the bhyve-script (from
http://bhyve.org/bhyve-script.tar) without success.
Copied vm0 to lin1 and changed VMOS to "linux" and VMOSVER to
"ubuntu13.10".
Then run:
#sh lin1 iso
Installation starts and everything looks good until it tries to install
Thanks, I'll test your image.
2014/1/22 Peter Grehan
> Hi Takuya,
>
>
> * Debian 7.3 with bhyve-scripts
>> Able to install, bootup!
>> But serial console sometimes outputs "AT+GCAP" or something, looks like AT
>> command?
>> Maybe I mis-configured Debian during installation?
>>
>
> I think I
2014/1/22 Takuya ASADA
> Append results using bhyyve-scripts.
>
> * CentOS 6.5 with bhyve-scripts
> Dies at same place: Unknown WRMSR code 391, val 200f, cpu 0
>
>
This issue was resolved by back-porting -CURRENT patch:
svn co svn://svn.freebsd.org/base/head
cd head
svn diff -r259634:r259635
Hi Takuya,
* Debian 7.3 with bhyve-scripts
Able to install, bootup!
But serial console sometimes outputs "AT+GCAP" or something, looks like AT
command?
Maybe I mis-configured Debian during installation?
I think I saw this but it eventually popped up a login prompt.
Guessing it was attempting
>
>
> * Ubuntu 13.10 with bhyve-scripts
> Dies at same place: (initramfs)
> Anyway I'll test with ahci-cd, which is point-outed by Peter.
>
> No this was wrong, bhyve-scripts already uses ahci-cd, I could
install&boot Ubuntu 13.10 without problem.
___
fre
Append results using bhyyve-scripts.
* CentOS 6.5 with bhyve-scripts
Dies at same place: Unknown WRMSR code 391, val 200f, cpu 0
* Ubuntu 13.10 with bhyve-scripts
Dies at same place: (initramfs)
Anyway I'll test with ahci-cd, which is point-outed by Peter.
* Debian 7.3 with bhyve-scripts
Abl
2014/1/22 Peter Grehan
> On 1/21/14 9:20 PM, Takuya ASADA wrote:
>
>> Looks like CentOS 6.5 with bhyve-script fails on same place:
>> Unknown WRMSR code 391, val 200f, cpu 0
>>
>> Did you succeeded with 10.0-RELEASE? not -CURRENT?
>>
>
> The MSR access is dependent on the host CPU model, and
On 1/21/14 9:20 PM, Takuya ASADA wrote:
Looks like CentOS 6.5 with bhyve-script fails on same place:
Unknown WRMSR code 391, val 200f, cpu 0
Did you succeeded with 10.0-RELEASE? not -CURRENT?
The MSR access is dependent on the host CPU model, and doesn't show up
on desktop variants.
la
Looks like CentOS 6.5 with bhyve-script fails on same place:
Unknown WRMSR code 391, val 200f, cpu 0
Did you succeeded with 10.0-RELEASE? not -CURRENT?
2014/1/22 Matt Donovan
>
> I have gotten Centos 6.5 to boot however I used the bhyve scripts which
> can be gotten at bhyve.org. haven't tr
Hi Takuya,
* Ubuntu 13.10
Almost boot-up but couldn't mount cdrom.
That's a Linux issue - there isn't a virtio block driver in the
installer's initrd so it can't be used as the backend for the ISO image.
Use ahci-cd instead for the ISO.
I've been able to boot Ubuntu 12.04/13.04/13.10/14
Oh, I didn't know bhyve-script.tar is still on bhyve.org (I didn't notice
there's "Tools" tab on the page).
I'll try it.
2014/1/22 Matt Donovan
> Hello
>
> On Jan 21, 2014 8:38 PM, "Takuya ASADA" wrote:
> >
> > Hmm, looks like neel@ adding ignoring unimplemented MSR access patch on
> > -CURREN
Since I have not personally looked into doing this I have no idea if the
following idea will work or not (it is on my personal todo list for the
next week or so though) and that is to create a new HyperV subclass in
PetiteCloud for bhyve-grub (you should only need to override loadVm(...)
and there
Hello
On Jan 21, 2014 8:38 PM, "Takuya ASADA" wrote:
>
> Hmm, looks like neel@ adding ignoring unimplemented MSR access patch on
> -CURRENT.
> Does it means we can't use (some version of) Linux on 10.0-RELEASE?
>
>
https://github.com/freebsd/freebsd/commit/5dab6f9ed3816204ff73fd075abfaba1ed5c7673
Hmm, looks like neel@ adding ignoring unimplemented MSR access patch on
-CURRENT.
Does it means we can't use (some version of) Linux on 10.0-RELEASE?
https://github.com/freebsd/freebsd/commit/5dab6f9ed3816204ff73fd075abfaba1ed5c7673
2014/1/22 Takuya ASADA
> Hi,
>
> I want to know which Linux d
Hi,
I want to know which Linux distribution is supported on BHyVe
(+grub2-bhyve) in 10.0-RELEASE.
I tried to these distributions, but I haven't succeeded to install any
choice.
On these tests, I used modified vmrun.sh script for all test, source code
is here:
https://gist.github.com/syuu1228/85524
68 matches
Mail list logo
