Bug 830363

Summary:	reboot forever freenas-8.0.4 in fedoa17-kvm when disk added
Product:	[Fedora] Fedora	Reporter:	Seiichi Nakashima <s-nakashima>
Component:	qemu	Assignee:	Fedora Virtualization Maintainers <virt-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	amit.shah, berrange, cfergeau, crobinso, dennis, dwmw2, itamar, knoel, pbonzini, scottt.tw, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-11 19:29:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Seiichi Nakashima 2012-06-09 00:54:57 UTC

Description of problem:

I use Freenas-8.0.4(guestOS) in fedora17-x64-kvm.
I make a virtual-machine in kvm(2core, 2GB memory, 2GB disk), install freenas,
it is OK, stop virtual-machine.
then I added a second disk in virtual-machi(40GB disk),
few minutes later, freenas(freebsd-8) reboot forever.
But I use Freenas-8.0.4 in fedora15-x64-kvm, these operations are OK.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1.install fedora17-x64 + kvm
2.make virtual-machine, and install freenas-8.0.4-RELEASE-p2-x64
3.virtural-machine network setting, and stop
4.add second disk to virtual-machi
5.setting freenas Storage->Voluemes->Create Volume UFS filesystem
6.few minutes later, reboot forever freenas virtual-machine.

I use amd 6core CPU, and 8GB memory machine on asrock mother.
  
Actual results:



Expected results:


Additional info:

Comment 1 Fedora End Of Life 2013-07-04 04:13:17 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Cole Robinson 2013-07-11 19:29:24 UTC

Sorry this never received a response, but this is unlikely to be fixed on F17 since it is end-of-life soon. Please see if this reproduces on F19 and if so please reopen.