Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 15:57, Craig Rodrigues wrote: I'm also looking into running a Ubuntu vm. i want to test/use zoneminder, and all my FreeBSD attempts run into trouble. So I'm also still looking for grub-bhyve. grub2-bhyve is in ports: http://www.freshports.org/sysutils/grub2-bhyve/ Yup, took

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Aryeh Friedman
And I've seen discussions in other threads about reading/writing cpu registers where some bits should be 0, but trap when being set (Or something close to this...???) So it could again be due to the amdsrc tree differences? --WjW And again this is running on my AMD-board.

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Peter Grehan
vm exit rdmsr 0xc0010015, cpu 0 --- And I've seen discussions in other threads about reading/writing cpu registers where some bits should be 0, but trap when being set (Or something close to this...???) So it could again be due to the amdsrc tree differences? It's Linux accessing

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 17:40, Peter Grehan wrote: vm exit rdmsr 0xc0010015, cpu 0 --- And I've seen discussions in other threads about reading/writing cpu registers where some bits should be 0, but trap when being set (Or something close to this...???) So it could again be due to the amdsrc tree

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Peter Grehan
It's a toy box here so if anything needs to be tested, worked out. Just let me know. And I'm willing to run the risk of lost work, because using the ignore option bites me You can try the -w option. Aryeh has reported that it works for him. later, Peter.

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 17:57, Peter Grehan wrote: It's a toy box here so if anything needs to be tested, worked out. Just let me know. And I'm willing to run the risk of lost work, because using the ignore option bites me You can try the -w option. Aryeh has reported that it works for him. -w

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Peter Grehan
-w does not exist on my bhyve bhyve: illegal option -- w Hmmm, just checked and you're right. Looks like a mis-merge - this change went into CURRENT in early December, and the most recent sync for the SVM branch was from Jan 14 :( Now I'm wondering what else hasn't made it in :( later,

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 18:09, Peter Grehan wrote: -w does not exist on my bhyve bhyve: illegal option -- w Hmmm, just checked and you're right. Looks like a mis-merge - this change went into CURRENT in early December, and the most recent sync for the SVM branch was from Jan 14 :( Now I'm

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Peter Grehan
Against what current version did you merge/build the SVM branch? I'll either check that out, or try my subversion skills to see if that reduces the diff. My mistake - the sync was a r259205, which was from Dec 10 and predates the -w option (r259635, Dec 17). later, Peter.

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 17:35, Aryeh Friedman wrote: And I've seen discussions in other threads about reading/writing cpu registers where some bits should be 0, but trap when being set (Or something close to this...???) So it could again be due to the amdsrc tree differences?

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Peter Grehan
On 23-2-2014 18:26, Peter Grehan wrote: Against what current version did you merge/build the SVM branch? I'll either check that out, or try my subversion skills to see if that reduces the diff. My mistake - the sync was a r259205, which was from Dec 10 and predates the -w option (r259635,

Re: Bhyve and Ubuntu booting

2014-02-23 Thread Willem Jan Withagen
On 23-2-2014 22:12, Peter Grehan wrote: On 23-2-2014 18:26, Peter Grehan wrote: Against what current version did you merge/build the SVM branch? I'll either check that out, or try my subversion skills to see if that reduces the diff. My mistake - the sync was a r259205, which was from Dec