Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE )
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 FreeBSD 10 host if I try to run openbsd 5.5 VM (my
FreeBSD current host freezes too if I try to run a VirtualBox VM with
vmm.ko and nmdm.ko modules loaded, not sure why).
I tested it again on a FreeBSD current host running on real hardware
with a number of VMs/OSes and the results I got are -
* Ubuntu-12.04.4 both amd64 and i386 fail to boot from CD - get stuck
somewhere after a purple screen
* Debian 7.3.0 both amd64 and i386 boot and install fine from CD,
booting from hard disk gets stuck at GRUB though
* FreeBSD 10 i386 boots from CD and disk, however is very slow
(installation took literally several hours)
* pfSense 2.1 i386 works fine
* OpenBSD 5.5 i386 boots and installs from CD, boots from disk after
installation only when ACPI is disabled at boot
* OpenBSD 5.5 amd64 boots and installs from CD, booting the installed
OS from disk however crashes qemu late around starting sndiod with
RAX= RBX=1a938686c340 RCX=1a91832031e5
RDX=1a938dc82b64
RSI=0012 RDI=1a938686c350 RBP=1a938dfb6f60
RSP=7f7ebf30
R8 =1a938dfb6f60 R9 =000d R10=
R11=
R12=1a91832031e5 R13=0012 R14=1a9392ff4000
R15=
RIP=1a938db21c7d RFL=00010246 [---Z-P-] CPL=3 II=0 A20=1 SMM=0
HLT=0
ES =0023 bfff 00aff300 DPL=3 DS16 [-WA]
CS =002b bfff 00affb00 DPL=3 CS64 [-RA]
SS =0023 bfff 00aff300 DPL=3 DS16 [-WA]
DS =0023 bfff 00aff300 DPL=3 DS16 [-WA]
FS =0023 bfff 00aff300 DPL=3 DS16 [-WA]
GS =0023 bfff 00aff300 DPL=3 DS16 [-WA]
LDT= 8200 DPL=0 LDT
TR =0030 80011000 0067 8900 DPL=0 TSS64-avl
GDT= 80011068 003f
IDT= 8001 0fff
CR0=e001003b CR2=1a938686c348 CR3=3f498000 CR4=07b0
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
Unsupported return value: 0x
and
kqemu: closed by pid=26323
kqemu: aborting: Unexpected exception 0x0d in monitor space
in dmesg. This however looks like a problem with kqemu-kmod not
related to the KPI changes. I tested this with kqemu-kmod-devel with
the patch applied and qemu-0.11.1_13 since obviously KQEMU support was
dropped in later versions. Considering that kqemu support was dropped
in newer versions of qemu however, the patch is probably useless and
kqemu-kmod ports should just be marked obsolete.
cheers,
Shteryana
On Thu, Feb 6, 2014 at 10:12 PM, Juergen Lock n...@jelal.kn-bremen.de wrote:
The commit does look relevant but testing your patch on a 10.0-RC1
vbox guest (it's what I had available) with the RC1 iso like so:
# kldload kqemu
% qemu-system-x86_64 -cdrom /dev/cd0 -m 512 -curses -enable-kqemu
panics like this:
--
10rc1amd64mbr2 dumped core - see /var/crash/vmcore.1
--- kqemu-freebsd.c~2014-02-07 20:00:33.656255395 +0200
+++ kqemu-freebsd.c 2014-02-08 08:43:19.209100708 +0200
@@ -105,17 +105,29 @@
*/
struct kqemu_page *CDECL kqemu_alloc_zeroed_page(unsigned long *ppage_index)
{
+#if __FreeBSD_version 130
pmap_t pmap;
+#endif
vm_offset_t va;
vm_paddr_t pa;
+#if __FreeBSD_version = 130
+va = kmem_malloc(kernel_arena, PAGE_SIZE, M_ZERO | M_WAITOK);
+#else
va = kmem_alloc(kernel_map, PAGE_SIZE);
+#endif
+
if (va == 0) {
kqemu_log(kqemu_alloc_zeroed_page: NULL\n);
return NULL;
}
+
+#if __FreeBSD_version = 130
+pa = vtophys(va);
+#else
pmap = vm_map_pmap(kernel_map);
pa = pmap_extract(pmap, va);
+#endif
/* kqemu_log(kqemu_alloc_zeroed_page: %08x\n, pa); */
*ppage_index = pa PAGE_SHIFT;
return (struct kqemu_page *)va;
@@ -125,7 +137,11 @@
{
if (kqemu_debug 0)
kqemu_log(kqemu_free_page(%p)\n, page);
+#if __FreeBSD_version = 130
+kmem_free(kernel_arena, (vm_offset_t) page, PAGE_SIZE);
+#else
kmem_free(kernel_map, (vm_offset_t) page, PAGE_SIZE);
+#endif
}
/* return kernel address of the physical page page_index */
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org
kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE )
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 patch (plain
text below in case the attachment is removed) for a couple of months
now and the module is loaded successfully -
root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu
kqemu version 0x00010300
kqemu: KQEMU installed, max_locked_mem=4120624kB.
root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v
FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014
The original commit that broke kqemu-kmod is from March 9th, 2013, so
the patch should be applicable to 10-STABLE too. Reports on
success/failures welcome.
cheers,
Shteryana
P.S. Example on getting a headless VM with vbox -
#VBoxManage createvm --name MyServer --ostype Windows7 --register
#VBoxManage createhd --filename MyServer.vdi --size 20
#VBoxManage storagectl MyServer --name IDE Controller --add ide
--controller PIIX3
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 0 --device 1 --type hdd --medium MyServer.vdi
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 1 --device 0 --type dvddrive --medium
/home/myserver/install.iso
#VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on
--bridgeadapter1 em0 --nictype1 82540EM
#VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd
#VBoxHeadless -n -m 5901 -s MyServer
The VM is then accessible via vncviewer to the IP of the original
machine port 5901
--- kqemu-freebsd.c.orig2014-02-06 16:03:15.881335406 +0200
+++ kqemu-freebsd.c2014-02-06 16:04:25.951329106 +0200
@@ -109,7 +109,12 @@
vm_offset_t va;
vm_paddr_t pa;
+#if __FreeBSD_version = 130
+va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK);
+#else
va = kmem_alloc(kernel_map, PAGE_SIZE);
+#endif
+
if (va == 0) {
kqemu_log(kqemu_alloc_zeroed_page: NULL\n);
return NULL;
patch-unit3minorfix
Description: Binary data
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org
Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE )
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 and install the module.
I've been running kqemu under current with the attached patch (plain
text below in case the attachment is removed) for a couple of months
now and the module is loaded successfully -
root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu
kqemu version 0x00010300
kqemu: KQEMU installed, max_locked_mem=4120624kB.
root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v
FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014
The original commit that broke kqemu-kmod is from March 9th, 2013, so
the patch should be applicable to 10-STABLE too. Reports on
success/failures welcome.
cheers,
Shteryana
P.S. Example on getting a headless VM with vbox -
#VBoxManage createvm --name MyServer --ostype Windows7 --register
#VBoxManage createhd --filename MyServer.vdi --size 20
#VBoxManage storagectl MyServer --name IDE Controller --add ide
--controller PIIX3
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 0 --device 1 --type hdd --medium MyServer.vdi
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 1 --device 0 --type dvddrive --medium
/home/myserver/install.iso
#VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on
--bridgeadapter1 em0 --nictype1 82540EM
#VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd
#VBoxHeadless -n -m 5901 -s MyServer
The VM is then accessible via vncviewer to the IP of the original
machine port 5901
--- kqemu-freebsd.c.orig2014-02-06 16:03:15.881335406 +0200
+++ kqemu-freebsd.c2014-02-06 16:04:25.951329106 +0200
@@ -109,7 +109,12 @@
vm_offset_t va;
vm_paddr_t pa;
+#if __FreeBSD_version = 130
+va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK);
+#else
va = kmem_alloc(kernel_map, PAGE_SIZE);
+#endif
+
if (va == 0) {
kqemu_log(kqemu_alloc_zeroed_page: NULL\n);
return NULL;
Oh well kqemu isn't even used by vbox, it's for emulaotors/qemu when
built with the KQEMU knob and run with -enable-kqemu or -kernel-kqemu,
and fixing _that_ needs most likely more changes than this. (I.e. I
think I tried something similar and only got a panic. And also qemu
uses kqemu-kmod-devel, kqemu-kmod is only left for people still using
even older qemu forks.)
Sorry...
Juergen
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org
Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE )
On Thu, Feb 6, 2014 at 7:59 PM, Juergen Lock n...@jelal.kn-bremen.de 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-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/
compile and install the module.
I've been running kqemu under current with the attached patch (plain
text below in case the attachment is removed) for a couple of months
now and the module is loaded successfully -
root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep
kqemu
kqemu version 0x00010300
kqemu: KQEMU installed, max_locked_mem=4120624kB.
root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v
FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014
The original commit that broke kqemu-kmod is from March 9th, 2013, so
the patch should be applicable to 10-STABLE too. Reports on
success/failures welcome.
cheers,
Shteryana
P.S. Example on getting a headless VM with vbox -
#VBoxManage createvm --name MyServer --ostype Windows7 --register
#VBoxManage createhd --filename MyServer.vdi --size 20
#VBoxManage storagectl MyServer --name IDE Controller --add ide
--controller PIIX3
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 0 --device 1 --type hdd --medium MyServer.vdi
#VBoxManage storageattach MyServer --storagectl IDE Controller
--port 1 --device 0 --type dvddrive --medium
/home/myserver/install.iso
#VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on
--bridgeadapter1 em0 --nictype1 82540EM
#VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd
#VBoxHeadless -n -m 5901 -s MyServer
The VM is then accessible via vncviewer to the IP of the original
machine port 5901
--- kqemu-freebsd.c.orig2014-02-06 16:03:15.881335406 +0200
+++ kqemu-freebsd.c2014-02-06 16:04:25.951329106 +0200
@@ -109,7 +109,12 @@
vm_offset_t va;
vm_paddr_t pa;
+#if __FreeBSD_version = 130
+va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK);
+#else
va = kmem_alloc(kernel_map, PAGE_SIZE);
+#endif
+
if (va == 0) {
kqemu_log(kqemu_alloc_zeroed_page: NULL\n);
return NULL;
Oh well kqemu isn't even used by vbox, it's for emulaotors/qemu when
Well, the VirtualBox off topic was caused by someone saying in an earlier thread
me and
Dee (personally and not as the petitecloud development team) would be
willing to give $50 to anyone who can get kqemu running on 10 and/or show
how to get vbox to work headless
built with the KQEMU knob and run with -enable-kqemu or -kernel-kqemu,
and fixing _that_ needs most likely more changes than this. (I.e. I
think I tried something similar and only got a panic. And also qemu
Did you really try it? Can you explain then why it works for me with
both kqemu-kmod-devel and kqemu-kmod?
Can you please explain why this commit -
http://svnweb.freebsd.org/base?view=revisionrevision=248084 - is
(ir-)relevant to the patch proposed?
uses kqemu-kmod-devel, kqemu-kmod is only left for people still using
even older qemu forks.)
Sorry...
Juergen
cheers,
Shteryana Shopova
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 inconsistently) I will post a version boots linux as a guest (later tonight likely when I get back from work) as a CFT -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 be it makes sense for someone (a bhyve dev) to inspect it? -- Markiyan. 2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com: 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) = 2cbe868812a871242cdcdd8f2fd6feb9 doing the sysctl does no good -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
2014-01-28 Aryeh Friedman aryeh.fried...@gmail.com: 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 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 be it makes sense for someone (a bhyve dev) to inspect it? -- Markiyan. 2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com: 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) = 2cbe868812a871242cdcdd8f2fd6feb9 doing the sysctl does no good -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 with it to make it fit into petitecloud) 2. It uses a non-existent option (-I) Both are characterstics of petitecloud scripts but not so much of vmrun.sh (the main reason I do not recommend using petitecloud scripts except as nothing but barebone starter scripts if you use them to make your own). The reason for bringing all the above up is I am having a very hard time getting it to work and if it is from petitecloud can you please kindly walk me through how you went from my script to yours... the main issue I am attempting to over come is currently PC assumes that there is a single disk that represents the instance (a running instance is nothing more then loading it into RAM and wrapping a hyperv around it) [e.g. something like /vms/import/ubu.img] and that it contains *ALL* the data that is needed to boot (i.e. no other files are needed)... so far it appears (and I hope I am wrong) there is no way to force a linux instance into this model because you have to have the disk, the cd and the device map in the same dir but kept as separate files namely something like this: linux/ device.map disk.img cd.img seems to be the only model grub2-bhyve will be able to boot (symlinks at least on the surface seem to be a no go also...)... there are the following problems with this model though when doing mass VM's: * You have to copy the CD repeatedly to the boot dir (this is likely why openstack does not support cd based installs) * It makes for a really messy when attempting to make sure you completely nuke a vm when you delete it (currently pettiecloud does not delete the disk when the instance is deleted but this will be an option soon an likely the default) Of course the long term solution is unified off disk (vs. off loader) booting but until then any good work arounds? On Tue, Jan 28, 2014 at 6:23 AM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 2014-01-28 Aryeh Friedman aryeh.fried...@gmail.com: 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 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 be it makes sense for someone (a bhyve dev) to inspect it? -- Markiyan. 2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com: 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) = 2cbe868812a871242cdcdd8f2fd6feb9 doing the sysctl does no good -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 2014/1/26 Aryeh Friedman aryeh.fried...@gmail.com: 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 ubuntu I narrowed it down to this line.. namely any time I touch the cd it does that weird staff... btw it also seg faults if you type anything... I am using 12.04.3 LTS Aryeh, could you please clarify what did you do and what you wanted to achieve (is your screen shot an X session?). I managed to successfully install and run Ubuntu Server 13.10 as a bhyve instance as Jonas described, without X of course. Aside form that, I found that disk partitioning with LVM (one of options during Ubuntu install) didn't work for me. -- Markiyan. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
2014-01-26 Aryeh Friedman aryeh.fried...@gmail.com: On Sun, Jan 26, 2014 at 6:28 AM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 2014/1/26 Aryeh Friedman aryeh.fried...@gmail.com: 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 ubuntu I narrowed it down to this line.. namely any time I touch the cd it does that weird staff... btw it also seg faults if you type anything... I am using 12.04.3 LTS I just tried ubuntu-12.04.3-server-amd64.iso, everything goes smoothly on my side. Provided that you replicated the scenario correctly, I would suggest to minimize your host environment, may be try bare bhyvectl/bhyve (in case you run wrappers etc) Aryeh, could you please clarify what did you do and what you wanted to achieve (is your screen shot an X session?). I managed to successfully install and run Ubuntu Server 13.10 as a bhyve instance as Jonas described, without X of course. Aside form that, I found that disk partitioning with LVM (one of options during Ubuntu install) didn't work for me. -- Markiyan. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
# 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 # ifconfig bridge0 create # ifconfig bridge0 up # ifconfig bridge0 addm tap0 addm re0 # mkdir ubuntu # mv ubuntu.iso ubuntu # cat - EOF ubuntu/device.map ? (hd0) ./ubuntu/ubuntu.img ? (cd0) ./ubuntu/ubuntu.iso ? EOF # more ubuntu/device.map (hd0) ./ubuntu/ubuntu.img (cd0) ./ubuntu/ubuntu.iso # truncate -s 8G ubuntu/ubuntu.img # grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu : uninitializing+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ===++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= ==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+=== ===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== =+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ==+=+==+===++===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= =++==++===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ===+=+==+==+=+==+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+= ==+++==+==+==+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ =++==+==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== ==+=+==+=+==+=+=+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+++===+==+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ===+=+==+=+==+===+=+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==+++==+=+=+===+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+===+=+==+==+=+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ==+=+==+==+=+===+==+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= =++==+=+=+===++=+=+++==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ===+=+==+==+===+=+==+=+===+==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==++===+=+===+==+==+=+=++==+===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =+++===+=+=+=+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+ ==+=+==+=+==++===+=+=+=+=+=+==+===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== =+++==+=+==+==+===+==+=+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= ===+=+==+=++==+==+==+===+=+=+=+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== ==+++=+=+=+===+=+==+==+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Re: Linux on BHyVe in 10.0-RELEASE
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 aryeh.fried...@gmail.com: # 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 # ifconfig bridge0 create # ifconfig bridge0 up # ifconfig bridge0 addm tap0 addm re0 # mkdir ubuntu # mv ubuntu.iso ubuntu # cat - EOF ubuntu/device.map ? (hd0) ./ubuntu/ubuntu.img ? (cd0) ./ubuntu/ubuntu.iso ? EOF # more ubuntu/device.map (hd0) ./ubuntu/ubuntu.img (cd0) ./ubuntu/ubuntu.iso # truncate -s 8G ubuntu/ubuntu.img # grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu : uninitializing+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ===++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= ==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+=== ===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== =+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ==+=+==+===++===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= =++==++===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ===+=+==+==+=+==+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+= ==+++==+==+==+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ =++==+==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== ==+=+==+=+==+=+=+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+++===+==+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ===+=+==+=+==+===+=+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==+++==+=+=+===+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+===+=+==+==+=+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ==+=+==+==+=+===+==+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= =++==+=+=+===++=+=+++==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ===+=+==+==+===+=+==+=+===+==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==++===+=+===+==+==+=+=++==+===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =+++===+=+=+=+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+ ==+=+==+=+==++===+=+=+=+=+=+==+===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== =+++==+=+==+==+===+==+=+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=
Re: Linux on BHyVe in 10.0-RELEASE
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 markiyan.kush...@gmail.com: 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 aryeh.fried...@gmail.com: # 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 # ifconfig bridge0 create # ifconfig bridge0 up # ifconfig bridge0 addm tap0 addm re0 # mkdir ubuntu # mv ubuntu.iso ubuntu # cat - EOF ubuntu/device.map ? (hd0) ./ubuntu/ubuntu.img ? (cd0) ./ubuntu/ubuntu.iso ? EOF # more ubuntu/device.map (hd0) ./ubuntu/ubuntu.img (cd0) ./ubuntu/ubuntu.iso # truncate -s 8G ubuntu/ubuntu.img # grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu : uninitializing+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ===++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= ==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+=== ===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== =+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ==+=+==+===++===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= =++==++===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ===+=+==+==+=+==+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+= ==+++==+==+==+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ =++==+==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== ==+=+==+=+==+=+=+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+++===+==+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ===+=+==+=+==+===+=+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==+++==+=+=+===+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+===+=+==+==+=+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ==+=+==+==+=+===+==+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= =++==+=+=+===++=+=+++==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ===+=+==+==+===+=+==+=+===+==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==++===+=+===+==+==+=+=++==+===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =+++===+=+=+=+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+
Re: Linux on BHyVe in 10.0-RELEASE
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) = 2cbe868812a871242cdcdd8f2fd6feb9 doing the sysctl does no good -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
# 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# 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 markiyan.kush...@gmail.com: 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 aryeh.fried...@gmail.com: # 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 # ifconfig bridge0 create # ifconfig bridge0 up # ifconfig bridge0 addm tap0 addm re0 # mkdir ubuntu # mv ubuntu.iso ubuntu # cat - EOF ubuntu/device.map ? (hd0) ./ubuntu/ubuntu.img ? (cd0) ./ubuntu/ubuntu.iso ? EOF # more ubuntu/device.map (hd0) ./ubuntu/ubuntu.img (cd0) ./ubuntu/ubuntu.iso # truncate -s 8G ubuntu/ubuntu.img # grub-bhyve -r cd0 -m ./ubuntu/device.map -M 2048 ubuntu : uninitializing+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ===++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= ==+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ==+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+== =++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+=== ===+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== =+===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ ==+=+==+===++===+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= =++==++===+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ===+=+==+==+=+==+==++=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+= ==+++==+==+==+=+===+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ =++==+==++===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+== ==+=+==+=+==+=+=+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+ =+++===+==+=+=+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+= ===+=+==+=+==+===+=+=+==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ==+++==+=+=+===+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+ =+===+=+==+==+=+=++=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=== ==+=+==+==+=+===+==+=+==+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+=+===+= =++==+=+=+===++=+=+++==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+
Re: Linux on BHyVe in 10.0-RELEASE
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 aryeh.fried...@gmail.com: 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) = 2cbe868812a871242cdcdd8f2fd6feb9 doing the sysctl does no good -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 before comiting it to code in PetiteCloud the key to transporting instances back and forth between them was to keep everything as raw disk images my guess we some major hacking you could do it out of the box... the real answer though is getting kqemu or vbox working again me and Dee (personally and not as the petitecloud development team) would be willing to give $50 to anyone who can get kqemu running on 10 and/or show how to get vbox to work headless On Thu, Jan 23, 2014 at 3:37 AM, Jonas Bülow jonas.bu...@gmail.com wrote: 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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
Does using the standard file backed bhye work? On Thu, Jan 23, 2014 at 3:56 AM, Jonas Bülow jonas.bu...@gmail.com 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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 aryeh.fried...@gmail.comwrote: Does using the standard file backed bhye work? On Thu, Jan 23, 2014 at 3:56 AM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 truncate -s 10G /vms/pri/jf4aibtonk ifconfig tap202 destroy ifconfig tap202 create ifconfig tap202 up sleep 5 ifconfig bridge0 addm tap202 up /usr/sbin/bhyveload -m 512 -d /vms/cds/FreeBSD-10.0-BETA2-amd64-disc1.iso jf4aibtonk /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap202 -s 2:0,virtio-blk,/vms/pri/jf4aibtonk -s 3:0,virtio-blk,/vms/cds/FreeBSD-10.0-BETA2-amd64-disc1.iso -S 31,uart,stdio jf4aibtonk echo $!/var/run/petitecloud/jf4aibtonk ifconfig tap202 destroy ifconfig tap202 create ifconfig tap202 up sleep 5 ifconfig bridge0 addm tap202 up /usr/sbin/bhyveload -m 512 -d /vms/pri/jf4aibtonk jf4aibtonk /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap202 -s 2:0,virtio-blk,/vms/pri/jf4aibtonk -S 31,uart,stdio jf4aibtonk echo $!/var/run/petitecloud/jf4aibtonk I suggest try it via PC or some other precanned script and then debug and adopt from there (i.e. use the assumption that everything is file backed not disk backed until you can isolate the issue) On Thu, Jan 23, 2014 at 4:45 AM, Jonas Bülow jonas.bu...@gmail.com wrote: Can you elaborate more what you mean? I currently do: cp vm0 lin1 ...edit lin1 and set linux and ubuntu13.10 sh lin1 iso = failing install /J On Thu, Jan 23, 2014 at 10:38 AM, Aryeh Friedman aryeh.fried...@gmail.com wrote: Try: truncat --size 10G disk.img bhyve -d disk.img On Thu, Jan 23, 2014 at 4:37 AM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 aryeh.fried...@gmail.com wrote: Does using the standard file backed bhye work? On Thu, Jan 23, 2014 at 3:56 AM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 edi...@callfortesting.orgwrote: 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 why. What does work for me for FreeBSD VM's is to prepare /dev/zvol/zroot/vm3 using the bhyve-script approach and then boot it as usual. I will include this in an rc version of bhyve-script that I hope to release shortly. It may not be worth adding the functionality to bhyve-script as it is EOL. Michael On 1/22/14 11:26 PM, Jonas Bülow wrote: 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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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-target: Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on device) Jan 23 10:51:08 in-target: E: Can't mmap an empty file Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9: Bad file descriptor) Jan 23 10:51:08 in-target: E: The package lists or status file could not be parsed or opened. Jan 23 10:51:08 grub-installer: info: Identified partition label for /dev/vda1: msdos Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3 (pipe:[7196]) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group vda not found Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group vda Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver config: could not write /var/cache/debconf/config.dat-new: No space left on device Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring 'grub-installer' failed with error code 1 Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer' failed. Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit from 'medium' to 'low' Jan 23 10:51:09 debconf: Setting debconf/priority to low Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
On Thu, Jan 23, 2014 at 5:53 AM, Jonas Bülow jonas.bu...@gmail.com 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 linux support to bhyve running under PC (we will likely issue a CFT in a few days or so for this) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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: Reading package lists... Jan 23 10:51:08 in-target: Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on device) Jan 23 10:51:08 in-target: E: Can't mmap an empty file Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9: Bad file descriptor) Jan 23 10:51:08 in-target: E: The package lists or status file could not be parsed or opened. Jan 23 10:51:08 grub-installer: info: Identified partition label for /dev/vda1: msdos Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3 (pipe:[7196]) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group vda not found Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group vda Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver config: could not write /var/cache/debconf/config.dat-new: No space left on device Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring 'grub-installer' failed with error code 1 Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer' failed. Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit from 'medium' to 'low' Jan 23 10:51:09 debconf: Setting debconf/priority to low Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected Normally you can switch to another virtual console with Alt+F1 to F4 (IIRC), I don't know if that's also possible in bhyve. If it works, please open a shell and see with df which filesystem is full. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 Use% Mounted on none200.3M148.0K200.1M 0% /run devtmpfs995.7M 0995.7M 0% /dev /dev/sr0672.0M672.0M 0 100% /cdrom /dev/mapper/c--182--181--143--31--vg-root 960.4M936.1M 0 100% /target /dev/vda1 235.3M 29.1M194.1M 13% /target/boot /dev/mapper/c--182--181--143--31--vg-home 495.8M408.0K459.0M 0% /target/home /dev/sr0672.0M672.0M 0 100% /target/media/cdrom devtmpfs995.7M 0995.7M 0% /target/dev On Thu, Jan 23, 2014 at 12:38 PM, Lars Engels lars.eng...@0x20.net wrote: 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: Reading package lists... Jan 23 10:51:08 in-target: Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on device) Jan 23 10:51:08 in-target: E: Can't mmap an empty file Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9: Bad file descriptor) Jan 23 10:51:08 in-target: E: The package lists or status file could not be parsed or opened. Jan 23 10:51:08 grub-installer: info: Identified partition label for /dev/vda1: msdos Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3 (pipe:[7196]) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group vda not found Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group vda Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver config: could not write /var/cache/debconf/config.dat-new: No space left on device Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring 'grub-installer' failed with error code 1 Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer' failed. Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit from 'medium' to 'low' Jan 23 10:51:09 debconf: Setting debconf/priority to low Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected Normally you can switch to another virtual console with Alt+F1 to F4 (IIRC), I don't know if that's also possible in bhyve. If it works, please open a shell and see with df which filesystem is full. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization- unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to
Re: Linux on BHyVe in 10.0-RELEASE
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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.com 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
Hi Jonas, On Thu, Jan 23, 2014 at 9:34 AM, Jonas Bülow jonas.bu...@gmail.com 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 this locally based on your steps. best Neel /j 23 jan 2014 kl. 18:07 skrev Neel Natu neeln...@gmail.com: Hi Jonas, On Thu, Jan 23, 2014 at 8:00 AM, Jonas Bülow jonas.bu...@gmail.com 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 --destroy --vm=lin0 errno = 22 Hmm… can you tell what the bhyve process associated with lin0 is doing from 'top' or 'ps'? What happens if you send a SIGTERM to the bhyve process? best Neel On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
Hi Jonas, On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow jonas.bu...@gmail.com 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,ahci-cd,./vm/vm1/vm1.iso -S 31,uart,stdio vm1 vm exit[0] reason VMX rip 0x inst_length 0 error 0 exit_reason 33 qualification 0x Looks like you are running into every possible problem there is :-) Anyways, could you confirm that you are loading the guest kernel into 'vm1' using grub-bhyve before executing the command above? best Neel /J On Thu, Jan 23, 2014 at 5:00 PM, Jonas Bülow jonas.bu...@gmail.com 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 --destroy --vm=lin0 errno = 22 On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.comwrote: 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 neeln...@gmail.com wrote: Hi Jonas, On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow jonas.bu...@gmail.com 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,ahci-cd,./vm/vm1/vm1.iso -S 31,uart,stdio vm1 vm exit[0] reason VMX rip 0x inst_length 0 error 0 exit_reason 33 qualification 0x Looks like you are running into every possible problem there is :-) Anyways, could you confirm that you are loading the guest kernel into 'vm1' using grub-bhyve before executing the command above? best Neel /J On Thu, Jan 23, 2014 at 5:00 PM, Jonas Bülow jonas.bu...@gmail.com 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 --destroy --vm=lin0 errno = 22 On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.com 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during install even without it being a different vol [just assumes any FS boundaries are the host OS's problem)... you can put the disk image any where (your home directory would be fine for example) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 em0 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 ubuntu /usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s 2,virtio-blk,./ubuntu/ubuntu.img -s 3,virtio-net,tap0 -s 4,ahci-cd,./ubuntu/ubuntu.iso -S 31,uart,stdio ubuntu ...install ubuntu. bhyvectl --destroy --vm=ubuntu grub-bhyve -r hd0,msdos1 -m ./ubuntu/device.map -M 2048 ubuntu ...select ubuntu ...see some errors: error: file `/boot/grub/x86_64-emu/all_video.mod' not found. error: file `/boot/grub/x86_64-emu/gzio.mod' not found. error: file `/boot/grub/x86_64-emu/part_msdos.mod' not found. error: file `/boot/grub/x86_64-emu/ext2.mod' not found. /usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s 2,virtio-blk,./ubuntu/ubuntu.img -s 3,virtio-net,tap0 -s 4,ahci-cd,./ubuntu/ubuntu.iso -S 31,uart,stdio ubuntu ...boots ...login jonas@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy jonas@ubuntu:~$ uname -a Linux ubuntu 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Note: there is no clean way of exiting a bhyve vm other than killing it (after halt or shutdown in the guest). The vm must be destroyed before starting it again. Trying to run the same bhyve command line again just hangs (vmidle, high CPU). procstat gives: PIDTID COMM TDNAME KSTACK 2381 100531 bhyvemevent running 2381 100532 bhyvevtnet-3:0 tx mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 2381 100533 bhyvevcpu 0 mi_switch sleepq_timedwait msleep_spin_sbt vm_run vmmdev_ioctl devfs_ioctl_f kern_ioctl sys_ioctl amd64_syscall Xfast_syscall /J On Thu, Jan 23, 2014 at 10:45 PM, Neel Natu neeln...@gmail.com wrote: Hi Jonas, On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow jonas.bu...@gmail.com 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,ahci-cd,./vm/vm1/vm1.iso -S 31,uart,stdio vm1 vm exit[0] reason VMX rip 0x inst_length 0 error 0 exit_reason 33 qualification 0x Looks like you are running into every possible problem there is :-) Anyways, could you confirm that you are loading the guest kernel into 'vm1' using grub-bhyve before executing the command above? best Neel /J On Thu, Jan 23, 2014 at 5:00 PM, Jonas Bülow jonas.bu...@gmail.com 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 --destroy --vm=lin0 errno = 22 On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.com 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage to extract from it since they are often not the ones actual called. I assume the image is file backed as I have not assigned a dedicated partition to the vm (and I don't know how to do that). You can keep them anywhere no need for a special volume (mater of fact I was just reusing the name of one of the diretoriess that PC creates during
Re: Linux on BHyVe in 10.0-RELEASE
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 jonas.bu...@gmail.com wrote: 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 em0 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 ubuntu /usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s 2,virtio-blk,./ubuntu/ubuntu.img -s 3,virtio-net,tap0 -s 4,ahci-cd,./ubuntu/ubuntu.iso -S 31,uart,stdio ubuntu ...install ubuntu. bhyvectl --destroy --vm=ubuntu grub-bhyve -r hd0,msdos1 -m ./ubuntu/device.map -M 2048 ubuntu ...select ubuntu ...see some errors: error: file `/boot/grub/x86_64-emu/all_video.mod' not found. error: file `/boot/grub/x86_64-emu/gzio.mod' not found. error: file `/boot/grub/x86_64-emu/part_msdos.mod' not found. error: file `/boot/grub/x86_64-emu/ext2.mod' not found. /usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s 2,virtio-blk,./ubuntu/ubuntu.img -s 3,virtio-net,tap0 -s 4,ahci-cd,./ubuntu/ubuntu.iso -S 31,uart,stdio ubuntu ...boots ...login jonas@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy jonas@ubuntu:~$ uname -a Linux ubuntu 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Note: there is no clean way of exiting a bhyve vm other than killing it (after halt or shutdown in the guest). The vm must be destroyed before starting it again. Trying to run the same bhyve command line again just hangs (vmidle, high CPU). procstat gives: PIDTID COMM TDNAME KSTACK 2381 100531 bhyvemevent running 2381 100532 bhyvevtnet-3:0 tx mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 2381 100533 bhyvevcpu 0 mi_switch sleepq_timedwait msleep_spin_sbt vm_run vmmdev_ioctl devfs_ioctl_f kern_ioctl sys_ioctl amd64_syscall Xfast_syscall /J On Thu, Jan 23, 2014 at 10:45 PM, Neel Natu neeln...@gmail.com wrote: Hi Jonas, On Thu, Jan 23, 2014 at 1:02 PM, Jonas Bülow jonas.bu...@gmail.com 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,ahci-cd,./vm/vm1/vm1.iso -S 31,uart,stdio vm1 vm exit[0] reason VMX rip 0x inst_length 0 error 0 exit_reason 33 qualification 0x Looks like you are running into every possible problem there is :-) Anyways, could you confirm that you are loading the guest kernel into 'vm1' using grub-bhyve before executing the command above? best Neel /J On Thu, Jan 23, 2014 at 5:00 PM, Jonas Bülow jonas.bu...@gmail.com 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 --destroy --vm=lin0 errno = 22 On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager mgamsja...@gmail.comwrote: Could you elaborate what you did to get it working? On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow jonas.bu...@gmail.com 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 aryeh.fried...@gmail.comwrote: On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow jonas.bu...@gmail.com 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 used bhyve-grub personally yet I can not recommend what the correct loader command line but if bhyve-script is in anyway related to vmrun.sh I would be highly suspicious of any command lines you manage
Re: Linux on BHyVe in 10.0-RELEASE
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 the grub boot loader. That last step fails. Exiting the installer and running: #sh lin1 start Gives a grub prompt. Any hints? Best Regards, Jonas ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 gre...@freebsd.org wrote: 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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 s...@dokukino.com 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/8552418 * Fedora 20 Fedora 20 has disk image for VM, I just tried to boot it from the image: ./linuxrun.sh -d Fedora-x86_64-20-20131211.1-sda.raw fedora grub linux (hd1,msdos1)/boot/vmlinuz-3.11.10-301.fc20.x86_64 grub initrd (hd1,msdos1)/boot/initramfs-3.11.10-301.fc20.x86_64.img grub boot but bhyve dies by unhandled rdmsr: [1.676041] device-mapper: uevent: version 1.0.3 [1.676556] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-de...@redhat.com vm exit rdmsr 0xe8, cpu 0 * CentOS 6.5 Tried to install with following commands but no luck: ./linuxrun.sh centos grub linux (hd0)/isolinux/vmlinuz grub initrd (hd0)/isolinux/initrd.img grub boot Got following error: NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 32610k freed Unknown WRMSR code 391, val 200f, cpu 0 * Ubuntu 13.10 Almost boot-up but couldn't mount cdrom. ./linuxrun.sh -d ubuntu.img -I ubuntu-13.10-desktop-amd64.iso ubuntu grub linux (hd0)/casper/vmlinuz.efi grub initrd (hd0)/casper/initrd.lz grub boot Got following error, maybe it can prevents by passing root= argument? [6.380384] Btrfs loaded Scanning for Btrfs filesystems done. mount: can't read '/etc/fstab': No such file or directory Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.20.2 (Ubuntu 1:1.20.0-8.1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Any suggestions? ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 only to put in a new loader name)... the above assumes that bhyve-grub is close enough to bhyveload to not need to much more and that once loaded normal bhyve is called On Tue, Jan 21, 2014 at 10:24 PM, Matt Donovan kitchet...@gmail.com wrote: Hello On Jan 21, 2014 8:38 PM, Takuya ASADA s...@dokukino.com 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 2014/1/22 Takuya ASADA s...@dokukino.com 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/8552418 * Fedora 20 Fedora 20 has disk image for VM, I just tried to boot it from the image: ./linuxrun.sh -d Fedora-x86_64-20-20131211.1-sda.raw fedora grub linux (hd1,msdos1)/boot/vmlinuz-3.11.10-301.fc20.x86_64 grub initrd (hd1,msdos1)/boot/initramfs-3.11.10-301.fc20.x86_64.img grub boot but bhyve dies by unhandled rdmsr: [1.676041] device-mapper: uevent: version 1.0.3 [1.676556] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-de...@redhat.com vm exit rdmsr 0xe8, cpu 0 * CentOS 6.5 Tried to install with following commands but no luck: ./linuxrun.sh centos grub linux (hd0)/isolinux/vmlinuz grub initrd (hd0)/isolinux/initrd.img grub boot Got following error: NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 32610k freed Unknown WRMSR code 391, val 200f, cpu 0 * Ubuntu 13.10 Almost boot-up but couldn't mount cdrom. ./linuxrun.sh -d ubuntu.img -I ubuntu-13.10-desktop-amd64.iso ubuntu grub linux (hd0)/casper/vmlinuz.efi grub initrd (hd0)/casper/initrd.lz grub boot Got following error, maybe it can prevents by passing root= argument? [6.380384] Btrfs loaded Scanning for Btrfs filesystems done. mount: can't read '/etc/fstab': No such file or directory Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.20.2 (Ubuntu 1:1.20.0-8.1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Any suggestions? I have gotten Centos 6.5 to boot however I used the bhyve scripts which can be gotten at bhyve.org. haven't tried any other currently ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 kitchet...@gmail.com Hello On Jan 21, 2014 8:38 PM, Takuya ASADA s...@dokukino.com 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 2014/1/22 Takuya ASADA s...@dokukino.com 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/8552418 * Fedora 20 Fedora 20 has disk image for VM, I just tried to boot it from the image: ./linuxrun.sh -d Fedora-x86_64-20-20131211.1-sda.raw fedora grub linux (hd1,msdos1)/boot/vmlinuz-3.11.10-301.fc20.x86_64 grub initrd (hd1,msdos1)/boot/initramfs-3.11.10-301.fc20.x86_64.img grub boot but bhyve dies by unhandled rdmsr: [1.676041] device-mapper: uevent: version 1.0.3 [1.676556] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-de...@redhat.com vm exit rdmsr 0xe8, cpu 0 * CentOS 6.5 Tried to install with following commands but no luck: ./linuxrun.sh centos grub linux (hd0)/isolinux/vmlinuz grub initrd (hd0)/isolinux/initrd.img grub boot Got following error: NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 32610k freed Unknown WRMSR code 391, val 200f, cpu 0 * Ubuntu 13.10 Almost boot-up but couldn't mount cdrom. ./linuxrun.sh -d ubuntu.img -I ubuntu-13.10-desktop-amd64.iso ubuntu grub linux (hd0)/casper/vmlinuz.efi grub initrd (hd0)/casper/initrd.lz grub boot Got following error, maybe it can prevents by passing root= argument? [6.380384] Btrfs loaded Scanning for Btrfs filesystems done. mount: can't read '/etc/fstab': No such file or directory Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.20.2 (Ubuntu 1:1.20.0-8.1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Any suggestions? I have gotten Centos 6.5 to boot however I used the bhyve scripts which can be gotten at bhyve.org. haven't tried any other currently ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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.04b, but I've only used the server spin and not the desktop. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 Able to install, bootup! But serial console sometimes outputs AT+GCAP or something, looks like AT command? Maybe I mis-configured Debian during installation? * OpenBSD 5.4 with bhyve-scripts Hangs at virtio0 initialization: scsibus0 at vioblk0: 2 targets sd0 at scsibus0 targ 0 lun 0: VirtIO, Block Device, SCSI3 0/direct fixed sd0: 10240MB, 512 bytes/sector, 20971520 sectors virtio0: couldn't map interrupt So, only Debian had worked on my environment for now. 2014/1/22 Takuya ASADA s...@dokukino.com 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/8552418 * Fedora 20 Fedora 20 has disk image for VM, I just tried to boot it from the image: ./linuxrun.sh -d Fedora-x86_64-20-20131211.1-sda.raw fedora grub linux (hd1,msdos1)/boot/vmlinuz-3.11.10-301.fc20.x86_64 grub initrd (hd1,msdos1)/boot/initramfs-3.11.10-301.fc20.x86_64.img grub boot but bhyve dies by unhandled rdmsr: [1.676041] device-mapper: uevent: version 1.0.3 [1.676556] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-de...@redhat.com vm exit rdmsr 0xe8, cpu 0 * CentOS 6.5 Tried to install with following commands but no luck: ./linuxrun.sh centos grub linux (hd0)/isolinux/vmlinuz grub initrd (hd0)/isolinux/initrd.img grub boot Got following error: NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 32610k freed Unknown WRMSR code 391, val 200f, cpu 0 * Ubuntu 13.10 Almost boot-up but couldn't mount cdrom. ./linuxrun.sh -d ubuntu.img -I ubuntu-13.10-desktop-amd64.iso ubuntu grub linux (hd0)/casper/vmlinuz.efi grub initrd (hd0)/casper/initrd.lz grub boot Got following error, maybe it can prevents by passing root= argument? [6.380384] Btrfs loaded Scanning for Btrfs filesystems done. mount: can't read '/etc/fstab': No such file or directory Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.20.2 (Ubuntu 1:1.20.0-8.1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Any suggestions? ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
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 to detect if a modem was present. * OpenBSD 5.4 with bhyve-scripts Hangs at virtio0 initialization: scsibus0 at vioblk0: 2 targets sd0 at scsibus0 targ 0 lun 0: VirtIO, Block Device, SCSI3 0/direct fixed sd0: 10240MB, 512 bytes/sector, 20971520 sectors virtio0: couldn't map interrupt OpenBSD 5.4 doesn't have the change to use MSI interrupts for virtio devices (http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/virtio_pci.c 1.7) I built a 5.4/amd64 flashrd image with this change at http://people.freebsd.org/~grehan/flashimg.amd64-20131014.bz2 5.5 isn't displaying serial console output - I've yet to debug this; probably an issue with grub-bhyve. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
2014/1/22 Takuya ASADA s...@dokukino.com 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 ~/msr.diff cd /usr/src patch -p0 ~/msr.diff cd usr.sbin/bhyve make make install Then CentOS 6.5 worked on my machine without any problems. Since we modified source code maybe we should not call it worked on 10.0-RELEASE, actually it's good for temporally workaround. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Linux on BHyVe in 10.0-RELEASE
Thanks, I'll test your image. 2014/1/22 Peter Grehan gre...@freebsd.org 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 to detect if a modem was present. * OpenBSD 5.4 with bhyve-scripts Hangs at virtio0 initialization: scsibus0 at vioblk0: 2 targets sd0 at scsibus0 targ 0 lun 0: VirtIO, Block Device, SCSI3 0/direct fixed sd0: 10240MB, 512 bytes/sector, 20971520 sectors virtio0: couldn't map interrupt OpenBSD 5.4 doesn't have the change to use MSI interrupts for virtio devices (http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/ virtio_pci.c 1.7) I built a 5.4/amd64 flashrd image with this change at http://people.freebsd.org/~grehan/flashimg.amd64-20131014.bz2 5.5 isn't displaying serial console output - I've yet to debug this; probably an issue with grub-bhyve. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
