VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 16363)

Ticket Resolution Summary Owner Reporter
#1913 fixed xargs bug causing problems with rpm installation Nick Steffens
Description

There is an xargs bug in fedora core 8 (and possible other releases) which has been resolved in fedora rawhide (the latest development as of the date of this posting; http://fedoraproject.org/wiki/Releases/Rawhide).

Running 'xargs' on the command line produces the error:


xargs: xargs.c:445: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed. Aborted


See the bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=439593

When an rpm upgrade or install of virtualbox is run on fedora core 8, this error is thrown:


rpm -ihv VirtualBox-1.6.4_33808_fedora8-1.i586.rpm Preparing... ########################################### [100%] /var/tmp/rpm-tmp.70344: line 19: 3722 Broken pipe find /lib/modules -name "vboxdrv\.*" 2> /dev/null

3723 Aborted | xargs rm -f 2> /dev/null

error: %pre(VirtualBox-1.6.4_33808_fedora8-1.i386) scriptlet failed, exit status 134 error: install: %pre scriptlet failed (2), skipping VirtualBox-1.6.4_33808_fedora8-1

find /lib/modules -name "vboxdrv\.*" 2>/dev/null|xargs rm -f 2> /dev/null Aborted


This error is caused by this line in the rpm script: find /lib/modules -name "vboxdrv\.*" 2>/dev/null|xargs rm -f 2> /dev/null

This can be resolved by using exec instead of xargs in the rpm script.

To view the script, use: rpm --scripts -qp VirtualBox-1.6.4_33808_fedora8-1.i586.rpm

To workaround this problem, add this line

INSTALL_NO_VBOXDRV=1

to file

/etc/default/virtualbox

If this file does not exist then create it and add the line above. This workaround can be found in the rpm script.

Regards,

Nick Steffens

#1914 duplicate xargs bug causing problems with rpm installation Nick Steffens
Description

There is an xargs bug in fedora core 8 (and possible other releases) which has been resolved in fedora rawhide (the latest development as of the date of this posting; http://fedoraproject.org/wiki/Releases/Rawhide).

Running 'xargs' on the command line produces the error:


xargs: xargs.c:445: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed. Aborted


See the bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=439593

When an rpm upgrade or install of virtualbox is run on fedora core 8, this error is thrown:


rpm -ihv VirtualBox-1.6.4_33808_fedora8-1.i586.rpm Preparing... ########################################### [100%] /var/tmp/rpm-tmp.70344: line 19: 3722 Broken pipe find /lib/modules -name "vboxdrv\.*" 2> /dev/null

3723 Aborted | xargs rm -f 2> /dev/null

error: %pre(VirtualBox-1.6.4_33808_fedora8-1.i386) scriptlet failed, exit status 134 error: install: %pre scriptlet failed (2), skipping VirtualBox-1.6.4_33808_fedora8-1

find /lib/modules -name "vboxdrv\.*" 2>/dev/null|xargs rm -f 2> /dev/null Aborted


This error is caused by this line in the rpm script: find /lib/modules -name "vboxdrv\.*" 2>/dev/null|xargs rm -f 2> /dev/null

This can be resolved by using exec instead of xargs in the rpm script.

To view the script, use: rpm --scripts -qp VirtualBox-1.6.4_33808_fedora8-1.i586.rpm

To workaround this problem, add this line

INSTALL_NO_VBOXDRV=1

to file

/etc/default/virtualbox

If this file does not exist then create it and add the line above. This workaround can be found in the rpm script.

Regards,

Nick Steffens

#3595 fixed xVM and VBoxManage report virtual machine as aborted when it is running correctly Glynn Bird
Description

OK. The host is a Centos 5.2 machine. We have several Centos 5.2 (text-only) guest machines cloned from one original. All works fine unless you change the settings (in this case, the network configuration) of one of the switched off guests (keira). The xVM GUI then crashes. When it runs again, it reports one of the running machines as "aborted", even though it is running correctly (see "reese").

The offline guest whose configuration was being edited ("keira") is reported as "Powered Off", but the "settings" button is now no longer available.

A reboot of the host usually solves the problem, but this means downtime for all of the guests.

Another headache is that the guest that is marked as "aborted" can be started by clicking on the green arrow, even though it is already running! This isn't good.

An

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy