I’m back here again after coming full circle thru a school of hard knocks. Now I have a dual boot of 12.3 32-bit and 64-bit. Both are lxde desktop. I couldn’t get UEFI to work, so the 12.3-64 is also non-UEFI.
When I was here before with 12.2-64 the 11.4 Oracle vb crashed my system. Accidentally the 12.3 I bought was only 32-bits, but the 4.2.6 Oracle available from the 32-bit opensuse 12.3 community just worked.
Since, I bought a real 12.3-64 and have it installed. The opensuse 12.3-64 community repositories have virtualbox that seems to have the same version, but it isn’t the same.
12.3-32 has an Oracle entry in the lxde system tools menu. 12.3-64 has a vb-gtk entry there that I can’t make work. Only the “+” entry is active. It wants a string or an object. None of my offerings have pleased it.
Seeing the 12.3-64 choices I have now, makes me think the vb has been my 12.2-64 problem also.
I only checked on box in the yast > SW Manager virtualbox display. I took the 4.2.6-3.1.8 box, expecting that to be the the latest Oracle vb. Maybe I have it, but the stuff that came with it is obscuring it.
So finally the questions! Is there an Oracle vb download for 12.3-64 comparable to the 12.3-32 opensuse repositories?
Do I still have to download Oracle from the 11.4 repository for the 12.3-64? I don’t have much confidence in that!
Last, can I add the 12.3-32 bit repository, download the 32-bit Oracle VB and install it on 12.3-64? Heboland.
you have a 64 bit machine and to have a better performance you need to use 64 bit virtual machine according to simple logic
Then again i might be wrong!
On 2013-05-09 10:56, vazhavandan wrote:
> you have a 64 bit machine and to have a better performance you need to
> use 64 bit virtual machine according to simple logic
> Then again i might be wrong!
I think that the hosting software should be 64 bit, same as the host.
What I’m not sure about is about the guest machines inside. Both types
should work, but I have no data about which is more reliable or uses
less resources or is faster, or what differences the hosting software
makes in this respect (sp. vbox vs vmware).
I would like to know.
I have, in the past, used 32 bit guests on 64 bit hosts, thinking that
they would use less memory. Now I use 64 bit hosts, because this way I
only download one DVD image for both host and guest, and one set of
updates for all machines in the network.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I don’t think I presented my question correctly. I have a true dual boot system now with 12.3-64 and 12.3-32 on 64-bit hardware. Neither of thies are virtual machines. The only guest OS I plan to host is XP-32.
The 12.3-32 vb installed from opensuse repros is different from the 12.3-64 vb installed from opensuse repros. The 32-bit vb is the latest Oracle vb. I think the 64-bit vb is something else.
Probably I need to install something different on the 64-bit OS, but what? Four months ago I went this route on the same hw with 12.2-64 an never got a vb that would work. I’m hoping that 12.3-64 has something better. If so where would I get it?
Since the 32-bit vb works so nice, I’m wondering if I could intall that same 32-bit vb on the 64-bit OS if I can’t get a 64-bit vb to work. Heboland.
The only difference I can spot is, that you have “virtualbox-qt” on the 32-bit system, whereas you have “vboxgtk” on the 64-bit system.
Another forum user had problems with “vboxgtk” recently. (although it works fine here)
I would suggest you install “virtualbox-qt” on the 64-bit system and use that. You should then also have the “Oracle VM VirtualBox” entry in your menu that you’re missing.
Oh and btw, you can remove the virtualbox-guest-kmp-desktop on both systems. You only need those in the guest not on the host.
Meanwhile I found this which is what the vboxgtk is printing when I try to start a 12.3-64 vm:
[Bug 811221] New: I met a wrong message in virtualbox when I create a new VM From: bugzilla_noreply@xxxxxxxxxx Date: Sun, 24 Mar 2013 00:46:38 +0000 Message-id: <bug-811221-21960@http.bugzilla.novell.com/>
https://bugzilla.novell.com/show_bug.cgi?id=811221
https://bugzilla.novell.com/show_bug.cgi?id=811221#c0
Summary: I met a wrong message in virtualbox when I create a
new VM
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: ogpugr@xxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (iPad; CPU OS 6_1_3 like Mac OS X)
AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10B329 Safari/8536.25
Actually my operating system version is openSUSE 12.3, but it isn't listed
above. I installed the virtualbox at
http://software.opensuse.org/package/virtualbox . I installed the virtualbox
successfully. But in the create new VM page, I chose the Windows XP, then I
click the add button, it told me "Could not create the VM: this parameter must
be a string or Unicode object.
Reproducible: Always
Steps to Reproduce:
1.Create new VM
2.Choose Windows XP
3.Click add
Actual Results:
The machine said " Could not create the VM: this parameter must be a string or
Unicode object.
My 12.3-64 is up to date according to yast > online update. This is a virgin install, so if this bug report is real, it must not have been fixed yet. Heboland.
wolfi323, your suggestion worked to get me started with the 12.3-64 vb. With the yast > SWmanager, I uninstalled the vboxgtk and installed the virtualbox-qt. I had to add myself to the vboxusers group.
That gives me the same vb interface as the 12.3-32 vb. With this I attempted the simplest of vb creations with an XP cd that works fine on the 12.3-32 vb. None of the Oracle extension packs are installed. Right after vb starts loading XP drivers into the virtual disk, 12.3-64 crashes with black screen and reboots. Are there any other logs besides vblog to check?
This is the bottom of the vbLog:
00:00:09.369981 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
00:00:09.369988 HWACCM: VMX MSR_IA32_FEATURE_CONTROL=1
00:00:09.375287 VM: Halt method global1 (5)
00:00:09.375293 HaltedGlobal1 config: cNsSpinBlockThresholdCfg=2000
00:00:09.375296 Changing the VM state from 'CREATING' to 'CREATED'.
00:00:09.375940 Changing the VM state from 'CREATED' to 'POWERING_ON'.
00:00:09.376269 Changing the VM state from 'POWERING_ON' to 'RUNNING'.
00:00:09.399084 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={b83ee395-8679-40ca-8d60-1a0cbe724930} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:09.401789 Guest Log: BIOS: VirtualBox 4.2.6
00:00:09.401976 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:09.404636 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={b83ee395-8679-40ca-8d60-1a0cbe724930} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:09.410362 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:09.410401 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:09.410938 Guest Log: BIOS: ata0-0: PCHS=16383/16/63 LCHS=1024/255/63
00:00:09.411594 PIIX3 ATA: Ctl#0: RESET, DevSel=1 AIOIf=0 CmdIf0=0xec (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:09.411658 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:09.411729 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:09.411741 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:09.413340 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:09.420006 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007fc79199e000 w=640 h=480 bpp=32 cbLine=0xA00, flags=0x1
00:00:09.703735 2D video acceleration is disabled.
00:00:11.891544 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:11.891743 Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231
00:00:11.891972 Guest Log: BIOS: Boot from Floppy 0 failed
00:00:11.892015 Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:11.901454 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
00:00:13.325796 Guest Log: BIOS: Booting from CD-ROM...
00:00:15.576117 Guest Log: int13_harddisk: function 15, unmapped device for ELDL=81
This hardware memory has been tested and retested without a failure. That’s not to conclude the hw doesn’t have some kind of problem. I have i7-3770 on Asus P8Z77-M LK and a pair of Kingston 8GB memory modules on the approved vendor list.
I’ve been here before with the 12.2-64, but I didn’t know then that the 12.3-32 would work perfectly.
For debug purposes, can I install the 32-bit rpms the 12.3-32 is using on the 12.3-64? Heboland.
Well, you could try to update virtualbox to the latest one in the Virtualization repo. Just enter YaST->Software Repositories, select Add->Community Repositories and enable it there.
Then go into YaST->Software Management, and switch all the virtualbox packages to the versions in this repo. (click on “Versions” on the lower right)
I’m using this version and have no problems installing WinXP on my 64bit system.
This isn’t my day! My attempts to add the virtualbox build service community repository failed twice without giving a reason. It never got to the point of trusting it.
Regarding the Bios settings I have a UEFI Bios so it may know whether the OS I’m running is 64 or 32 bit. I don’t change anything myself except the grub2 boot menu selection to pick 32 or 64. Both of these OSs are non-UEFI installs.
Yes the crashes cause the host to reboot! The crash point is not predictable. Also I have two individual XP-32 CDs, one preSp1, the other SP1. Each has a vm on 12.3-32. Both crash the host on 12.3-64.
After trying to create several vms, starting from scratch each time, and deleting all the files from the previous attempt, a couple of vms ended in the XP BSOD. With these I can save more information, like the machine state and the integrity of the host is preserved.
I expect this is Oracle code that opensuse makes available for our convenience. To get a debug version of vb, it would have to come from Oracle.
There is one bright spot for me. I have both OSs at my fingertips, so I can run vb, but just not on my primary OS.
It seems to me if this is a SW problem it would have been exposed by now, since it’s so catastrophic. A subtle hw problem probably isn’t going to be fixed until some guru buys what I have and knows how to expose the problem. Heboland.
This means your CPU hardware virtualization support is disabled. You should take a look in your BIOS settings and enable it if possible.
Under Bios Advance > CPU there is a button for Intel Virtualization Technology. It was disabled. Enabling Bios virtualization makes Oracle vb work. The system behavior without that button enabled seems kind of extreme!
In my failed attempt to install 12.3-64 using UEFI, I upgraded my Bios, which set everything back to defaults. For this reason I can’t be certain that the 12.3-32 doesn’t need this setting. If it’s important to know this, I can provide it.
Please take another bow for the suggestion to add the qt front end. Maybe the gtk front end would have worked if I had been in the virtualbox group, but the qt front end was the start that led to the success!
I haven’t done well marking these threads as solved, so if my attempt is inadequate, feel free to fix it! Heboland.
Well, you don’t need it necessarily, except if you want to run 64bit guests. But it sure helps for virtualization. That said, I don’t have it on my 64bit system, because my CPU doesn’t support it yet (it’s one of the first Athlon64s). But VirtualBox runs stable for me…
Maybe the gtk front end would have worked if I had been in the virtualbox group,
No. First of all, you must be in the virtualbox group (it’s called “vboxusers”, btw.;)), otherwise VirtualBox wouldn’t work at all! You get added automatically to that group when you install the openSUSE package.
Also I had a look at vboxgtk’s code. It just doesn’t support recent vbox versions yet, it seems. It calls vbox’s SDK functions with wrong parameters.
Although it says in the changelog:
Update to version 0.8.2: + Re-added vboxgtk.desktop.in
Yes, that is the correct name for the group the Qt wants. In my case with lxde desktop. I had to add myself manually to that group.
Earlier in this post I mentioned clicking only one box in yast > SWmanagement to get the Oracle virtualbox. All the stuff I showed in the rpm -qa code came with it including the gtk, but not the Qt.
Ordinarily lxde uses yast the same way as kde. My 12.3-64 install DVD came from OnDisk, but I would expect that is a near identical copy of what you installed.
It’s great to be configuring my XP vm instead of scratching my head! Heboland.
Yes. On installation the vboxusers group is created. No user is added to it (how should YaST/zypper know which user you are when it is run as root?;)). Sorry, I mixed that up. It’s been a while since I installed it the first time.
Earlier in this post I mentioned clicking only one box in yast > SWmanagement to get the Oracle virtualbox. All the stuff I showed in the rpm -qa code came with it including the gtk, but not the Qt.
Well, virtualbox only requires a “virtualbox-gui” which is provided by both virtualbox-qt and vboxgtk. So YaST/zypper can select either one to safisfy that dependency. In your case YaST seemed to think vboxgtk is more appropriate because you use lxde, which is based on GTK. How should YaST know that it doesn’t really work?
Ordinarily lxde uses yast the same way as kde. My 12.3-64 install DVD came from OnDisk, but I would expect that is a near identical copy of what you installed.
It’s great to be configuring my XP vm instead of scratching my head! Heboland.
I didn’t install from DVD, I upgraded with zypper dup from 12.2 via the online repos. I do it that way since years now… But yes, I guess that DVD is the same that you can download from software.opensuse.org: Download openSUSE 12.3.
Great that it works for you now!
