Fedora9 VM in VirtualBox - LVM prob

[eddsza]

Hi,
I was trying to run the Fedora9 VM in Virtualbox OSE 1.5.0 and came up with an LVM error. I took a screenshot, and uploaded it at http://www.bigupload.com/files/V6HJ7YOY5A/F9-LVMprob.png.zip.html (I didn't know policies for pasting screenshots here).

Could anyone please offer ideas regarding this? Are there any kernel parameters that I could enter to change the behavior?

(If use with Virtualbox is not supported, please let me know that, too :-)

Thanks in advance,
Ed.

[smyl]

for screen shots something like upldr.us (http://beta.upldr.us) would be better...

i've never used Virtualbox so i'm not sure
all the VM's from VMplanet get tested on workstation & player..

But another forum member might have experience with getting them to work in Virtualbox...

[motsteve]

I'm kind of embarrassed to say this, but the Parallels forum seems to have a lot of people on it who do use VirtualBox. I haven't been there for a couple of days since I poofed my trial version of Parallels. Right now all of the vm managers seem to have broken tools dealing with the various distro's. I hope Fusion 2.0 fixes at least my Suse tools. That distro is starting to grow on me. I just hope that the new version coming out on 19 June doesn't break the tool if it does get fixed for Suse 10.3. : - )

[smyl]

I'm kind of embarrassed to say this, but the Parallels forum seems to have a lot of people on it who do use VirtualBox. I haven't been there for a couple of days since I poofed my trial version of Parallels. Right now all of the vm managers seem to have broken tools dealing with the various distro's. I hope Fusion 2.0 fixes at least my Suse tools. That distro is starting to grow on me. I just hope that the new version coming out on 19 June doesn't break the tool if it does get fixed for Suse 10.3. : - )

Kernel updates & glib updates break the tools

kernel updates tend to be the quicker fix =)

[motsteve]

Please read the following in its entirety and consider it to be nothing more than a positive question and comment with no intended bad-attitude, editorial meaning.

Your statement that "Kernel updates & glib updates break the tools" and that "kernel updates tend to be the quicker fix =)" is taken by me to mean that if a distro changes and breaks the tools, then the developers of the distro will have to patch the kernal and glibs to fix it. For obvious reasons this is not going to happen, so if the VMware tools can't accommodate distro changes with matching tool changes in a timely manner, then over much of the time the tools will be broken and the usefulness of VMware or Parallels or any other vm manager will be severely diminished. Is this a bad conclusion on my part?

With open source software, the good news is that the kernel and glib changes are published during the development cycle, so it seems to an outsider like me, that the vm tools could be updated to follow these changes. Or is this another bad guess on my part? (I design integrated circuits and radio factories, I'm not a software designer in any sense of the title.)

The alternative is to have two CPU's with no shared resources save an A/B switch for the monitor/mouse/keyboard and both CPU's networked and sharing files on a file server in one or the other machine. With hardware as cheap as it is and as small as it is, this is enticing, especially when you consider that your graphics capability will be at full power in both CPU's.

[tacob]

Having 2 completely separate physical systems would use more power, create more heat, and take up more space then virtualizing the different operating systems...

I know when Ubuntu 7.10 came out there was an update for workstation about a week later that provided support for the new kernel.

If all the distro's waited for software manufacturers to come out w/ updates for there software before releasing there would never be new releases.

Just w/ virtualization I can think of 5 companies that they would be waiting on.

Ahh... the joys of early adaptation eh?

[smyl]

I know when Ubuntu 7.10 came out there was an update for workstation about a week later that provided support for the new kernel.

Ahh... the joys of early adaptation eh?

and this is why i'm still running 6.06-LTS on my vmware-server host, and 7.10 on my workstation...
though, server 2.0 does run great on both 8.04 & debian4.0r3

[motsteve]

Not knowing how long it would take to accommodate the kernel changes, does the kernel change so radically from distro to distro that everything in the tool is broken and the whole tool has to be redesigned? Also, can vmware tools be put in a Linux repertoire so that we get the latest upgrade and the package manager can take out the mistakes users make in installing the tools, so the VMware tech support guys don't get silly emails sent to them from users putting the tools in wrong? There's got to be a better way to run this railroad. : - )

FYI, openSuse 11.0 comes out 11 June, I believe.

[smyl]

Not knowing how long it would take to accommodate the kernel changes, does the kernel change so radically from distro to distro that everything in the tool is broken and the whole tool has to be redesigned? Also, can vmware tools be put in a Linux repertoire so that we get the latest upgrade and the package manager can take out the mistakes users make in installing the tools, so the VMware tech support guys don't get silly emails sent to them from users putting the tools in wrong? There's got to be a better way to run this railroad. : - )

FYI, openSuse 11.0 comes out 11 June, I believe.


The distribution would need to have permission to have it in the repo's...
As far as I know none of the distro's have that, though i could be wrong.

I think Canonical had agreements w/ them, as VMware server is in some of the older releases repositories.

[motsteve]

Every time I turn around on the distro and open sites, they are begging for help from heavy hitters to prompt Linux. VMware, Parallels, etc are very big promoters of Linux even though it is not declared directly. VMware player is an obvious example of Linux friendly behaviour. It looks like a natural for a very good relationship between the vm manager developers and opensource, but I don't know the details about licensing and other such legal stuff. If, however, the most paranoid company on the planet about software licensing, Apple, can put their money where their mouth is and buy and distribute CUPS to everyone, then I wouldn't think it a problem for other companies to do the same.

[motsteve]

Huh? I think that last response lost something in a translation.

[smyl]

There's a big difference between the way apple distributes cups & Linux Distro's distributing vmware.

cups is free to redistribute, whereas vmware is not, vmware wants each user to go to there site and agree to the license, in order to download there product...
In order for the distro's to distribute parts of VMware, they would need permission...

[motsteve]

Would your bosses have a problem handing over vmtools not as open, but with a freeware type of license? I'm guessing that would be okay with the open source people.

BTW, I have a walk around for copy and paste like tools gives you, but I need help figuring out how to make the window full screen now, to make no tools tolerable. My walk around involves using ssh and transferring files instead of using the clipboard. I guarantee you of one advantage and that is speed when it comes to moving files from Mac to Linux using this versus a click and drag move if the tools were working. It works great Linux to Mac in a GUI, but Mac doesn't have ssh for its connection to other servers. The best I could do was AFP and that doesn't do it. Mac works fine for terminal kinds of manipultion, however. I can also vnc Linux to Mac, but not Mac to Linux. I'm still working on these, I just wish that I knew what I was doing. :-)

[smyl]

If my bosses owned VMware I'm not sure if they would release the tools as freeware or not.

I'm not a VMware employee though, I just deal w/ virtualization at work a lot...

A lot of the customers here have ESX boxes, and I build VM's for my coworkers to use...