Bugs item #2556746, was opened at 2009-02-02 12:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2556746&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: intel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tim Knowles (knowlet)
Assigned to: Nobody/Anonymous (nobody)
Summary: FreeBSD/PC-BSD text screen corruption 

Initial Comment:
Using either kvm-83, kvm-82 or kvm-81 I am unable to install FreeBSD or PC BSD 
due to screen corruption (screenshot attached).  The initial boot menu is shown 
and is legible.  Once you have selected the boot option & the boot process 
continues the screen becomes corrupted.  I initially discovered the problem 
when setting up an LVM backed guest in virt-manager but I have attached a 
minimal cmd line below that allows you to trigger it.

1) It would appear that this problem was introduced in kvm-81 (kvm-80 does not 
exhibit the problem with FBSD or PCBSD but I have not tested any other versions 
of kvm)
2) If I use the -no-kvm switch with KVM-83 this problem does not occur.

Details:
Host: 1 x Intel Core i7 920, Fedora 10 64bit. 6GB memory (Dell Studio XPS 435)
kvm-83: self compiled - gcc version 4.3.2 20081105 (Red Hat 4.3.2-7)
cmd line:  /usr/local/bin/qemu-system-x86_64 -m 512 -cdrom 
7.1-RELEASE-amd64-dvd1.iso

Guests:
FreeBSD 7,1
PC-BSD 7.0.2

PS: I'd also like to add my thanks for creating KVM, it's fabulous tool. Many 
thanks

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2556746&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to