[Qemu-devel] [Bug 813788] Re: PowerPC video device needs to run OpenFirmware fb8-install

2011-08-28 Thread blueswirl
QEMU video devices need no changes, this can only be fixed in OpenBIOS.

** Changed in: qemu
   Status: New = Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/813788

Title:
  PowerPC video device needs to run OpenFirmware fb8-install

Status in QEMU:
  Invalid

Bug description:
  see http://lists.openbios.org/pipermail/openbios/2011-July/006580.html
  for more information.

  OpenBIOS is saying that the QEMU video device needs to call
  fb8-install in OpenFirmware/OpenBIOS to properly initialize the
  screen?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/813788/+subscriptions



[Qemu-devel] [Bug 818645] Re: Unhandled OF service in FreeBSD loader - unimplemented service milliseconds

2011-08-28 Thread blueswirl
The bug is real but it can only be fixed in OpenBIOS.

** Changed in: qemu
   Status: New = Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818645

Title:
  Unhandled OF service in FreeBSD loader - unimplemented service
  milliseconds

Status in QEMU:
  Invalid

Bug description:
  wkoszek@wkoszek:~/bin/qemu/qemu$ git log | head -1
  commit c886edfb851c0c590d4e77f058f2ec8ed95ad1b5

  built with default settings.

  Run like that:
  /home/wkoszek/bin/qemu-dynamic/bin/qemu-system-sparc64 -m 1024 -cdrom 
~/Pulpit/iso/FreeBSD-7.4-RELEASE-sparc64-bootonly.iso -hda 
~/Pulpit/iso/freebsd_sparc64.qcow2 -nographic -boot d

  Configuration device id QEMU version 1 machine id 0
  kernel cmdline 
  CPUs: 1 x SUNW,UltraSPARC-IIi
  UUID: ----
  Welcome to OpenBIOS v1.0 built on Jul 20 2011 21:17
Type 'help' for detailed information
  Trying cdrom:f...
  Not a bootable ELF image
  Loading a.out image...
  Loaded 7680 bytes
  entry point is 0x4000

  Jumping to entry point 4000 for type 0005...
  switching to new context: entry point 0x4000 stack 0xffe86b49
   
   FreeBSD/sparc64 boot block
 Boot path:   cdrom:f
 Boot loader: /boot/loader
  Consoles: Open Firmware console  

  Booting with sun4u support.
  Boot path set to cdrom:a

  FreeBSD/sparc64 bootstrap loader, Revision 1.0
  (r...@warner.cse.buffalo.edu, Fri Feb 18 05:38:31 UTC 2011)
  bootpath=cdrom:a
  Loading /boot/defaults/loader.conf 
  /boot/kernel/kernel data=0x8d1f48+0x82f88 syms=[0x8+0x88ec0+0x8+0x76966]
  |
  Unimplemented service milliseconds ([0] -- [1])
  Hit [Enter] to boot immediately, or any other key for command prompt.
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])

  This basically loops here unless I press CTRL+C.

  Was there any OpenBIOS release that didn't have this problem?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/818645/+subscriptions



[Qemu-devel] [Bug 818647] Re: Getting segmentation fault when trying to boot FreeBSD

2011-08-28 Thread blueswirl
Fixed by 67494323f2c782fe3e65c60529fe9dfa613fc500.


** Changed in: qemu
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818647

Title:
  Getting segmentation fault when trying to boot FreeBSD

Status in QEMU:
  Fix Committed

Bug description:
  wkoszek@wkoszek:~/bin/qemu/qemu$ git log | head -1
  commit c886edfb851c0c590d4e77f058f2ec8ed95ad1b5

  wkoszek@wkoszek:~/o/freebsd/sys/boot/i386$ qemu-system-sparc64 --version
  QEMU emulator version 0.15.50, Copyright (c) 2003-2008 Fabrice Bellard

  wkoszek@wkoszek:~/o/freebsd/sys/boot/i386$ uname -a
  Linux wkoszek 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:05:41 UTC 2011 
i686 i686 i386 GNU/Linux

  Qemu built with default settings (./configure --prefix=path  make
   make install)

  I run FreeBSD ISO image:
  /home/wkoszek/bin/qemu-dynamic/bin/qemu-system-sparc64 -m 1024 -cdrom 
~/Pulpit/iso/FreeBSD-7.4-RELEASE-sparc64-bootonly.iso -hda 
~/Pulpit/iso/freebsd_sparc64.qcow2 -nographic -boot d

  Configuration device id QEMU version 1 machine id 0
  kernel cmdline 
  CPUs: 1 x SUNW,UltraSPARC-IIi
  UUID: ----
  Welcome to OpenBIOS v1.0 built on Jul 20 2011 21:17
Type 'help' for detailed information
  Trying cdrom:f...
  Not a bootable ELF image
  Loading a.out image...
  Loaded 7680 bytes
  entry point is 0x4000

  Jumping to entry point 4000 for type 0005...
  switching to new context: entry point 0x4000 stack 0xffe86b49
   
   FreeBSD/sparc64 boot block
 Boot path:   cdrom:f
 Boot loader: /boot/loader
  Consoles: Open Firmware console  

  Booting with sun4u support.
  Boot path set to cdrom:a

  FreeBSD/sparc64 bootstrap loader, Revision 1.0
  (r...@warner.cse.buffalo.edu, Fri Feb 18 05:38:31 UTC 2011)
  bootpath=cdrom:a
  Loading /boot/defaults/loader.conf 
  /boot/kernel/kernel data=0x8d1f48+0x82f88 syms=[0x8+0x88ec0+0x8+0x76966]
  |
  Unimplemented service milliseconds ([0] -- [1])
  Hit [Enter] to boot immediately, or any other key for command prompt.
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])
  Unimplemented service milliseconds ([0] -- [1])

  I press CTRL + C and I get out of the looped warning about
  unimplemented service. Then I see:

  Type '?' for a list of commands, 'help' for more detailed help.
  OK boot
  jumping to kernel entry at 0xc0078000.
  BOOTUnhandled Exception 0x0034
  PC = 0xc0637454 NPC = 0xc0637458

  I wanted to start FreeBSD debugging here - I pressed 'CTRL+A c', I was
  dropped to the monitor.

  FRom the monitor I typed:

  Stopping execution
  QEMU 0.15.50 monitor - type 'help' for more information
  (qemu) x 0xc0078000
  c0078000: Cannot access memory
  (qemu) x 0xc0637454 
  c0637454: Cannot access memory
  (qemu) x 0xc0637458
  c0637458: Cannot access memory
  (qemu) xp 0xc0078000
  Segmentation fault

  IMO it shouldn't have crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/818647/+subscriptions



[Qemu-devel] [Bug 723871] Re: qemu-kvm-0.14.0 Aborts with -vga qxl

2011-05-14 Thread blueswirl
qemu-kvm.c does not exist in QEMU.

** Changed in: qemu
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/723871

Title:
  qemu-kvm-0.14.0 Aborts with -vga qxl

Status in QEMU:
  Invalid
Status in “libvirt” package in Ubuntu:
  Triaged
Status in “qemu-kvm” package in Ubuntu:
  Fix Released

Bug description:
  Host CPU is Core i7 Q820.  KVM is from 2.6.35-gentoo-r5 kernel (x86_64).
  Host has spice-0.7.2 and spice-protocol-0.7.0.
  Guest is Windows XP SP3 with qxl driver 0.6.1, virtio-serial 1.1.6 and 
vdagent 0.6.3.

  qemu-kvm is started like so:
  qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid 
-drive 
file=/home/rick/qemu/hds/wxp.raw,if=virtio,media=disk,aio=native,snapshot=on -m 
768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl 
-device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device 
virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice 
port=1234,disable-ticketing -monitor stdio
  and crashes with:
  qemu-system-x86_64: /home/rick/qemu/src/qemu-kvm-0.14.0/qemu-kvm.c:1724: 
kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
  Aborted

  If I use -no-kvm, it works fine.  If I use -vga std, it works fine.
  -enable-kvm and -vga qxl crashes.



[Qemu-devel] [Bug 423910] Re: openbios-sparc has no installation candidate

2010-10-01 Thread blueswirl
Packaging problem in Ubuntu, not upstream.

** Also affects: qemu-kvm (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qemu
   Status: New = Invalid

-- 
openbios-sparc has no installation candidate
https://bugs.launchpad.net/bugs/423910
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid
Status in “openbios-sparc” package in Ubuntu: New
Status in “qemu-kvm” package in Ubuntu: New

Bug description:
When installing Qemu through apt-get, openbios-sparc is recommended, but,

Package openbios-sparc is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package openbios-sparc has no installation candidate





[Qemu-devel] [Bug 568053] Re: requires MSYS coreutils ext sub-package to build on Windows

2010-10-01 Thread blueswirl
pc-bios/optionrom/signrom.sh uses 'dd'.

** Changed in: qemu
   Status: New = Confirmed

-- 
requires MSYS coreutils ext sub-package to build on Windows
https://bugs.launchpad.net/bugs/568053
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Confirmed

Bug description:
When I try to build QEMU on Windows without the MSYS coreutils ext sub-package 
installed, the build fails because it cannot find dd.





[Qemu-devel] [Bug 592028] Re: sparc32plus user test failed

2010-10-01 Thread blueswirl
Cross-OS emulation is not supported for user emulators.

** Changed in: qemu
   Status: New = Invalid

** Changed in: qemu
 Assignee: (unassigned) = blueswirl (blauwirbel)

-- 
sparc32plus user test failed
https://bugs.launchpad.net/bugs/592028
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid

Bug description:
Hello,

I try to execute on linux machine sparc binary (simple hello word application) 
using qemu-sparc32plus 
and get segfault.Before test I copy all libraries and headers 
(/usr/lib, /lib/, /usr/local/lib /usr/include /usr/local/include) 
from original solaris workstation to separate directory on linux machine: 
/usr/cross/sysroot
I also copy statically builded qemu binaries and hello_world app in 
/usr/cross/sysroot/bin
and start app as:
chroot /usr/cross/sysroot qemu-sparc32plus bin/hello_world
but also I get segfault.
As I see all necessary shared libs and interpreter (/usr/lib/ld.so.1) 
exists in apropriate directories: /usr/lib, /lib/, /usr/local/lib 
under new sysroot = /usr/cross/sysroot. I also try to run simple sparc32 app
using qemu-sparc32plus but also get segfault.

After that I try to run tests from linux-user-test-0.3 packet
but they also fail with qemu-sparc32plus emulation. I try to perform such test 
on different type of systems (see further)
and several version of qemu (builded from sources qemu-0.12.4 qemu-0.11.1 with 
configure  make ).

Probably I miss something in configuration or perform some wrong step with 
qemu-sparc32plus,
could you please clarify is sparc32plus user mode emulation is sucessfuly 
exists in the latest versions of qemu?

configuration of original Solaris sparc station where I build app:

bash-3.00# uname -a
SunOS fs650 5.10 Generic_137111-07 sun4us sparc FJSV,GPUZC-M
bash-3.00# gcc --version
gcc (GCC) 3.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
bash-3.00# psrinfo -v
Status of virtual processor 0 as of: 05/27/2010 12:23:06
  on-line since 05/13/2010 18:40:47.
  The sparcv9 processor operates at 1889 MHz,
and has a sparcv9 floating point processor.
skipped 1 - 6.
Status of virtual processor 7 as of: 05/27/2010 12:23:06
  on-line since 05/13/2010 18:41:14.
  The sparcv9 processor operates at 1889 MHz,
and has a sparcv9 floating point processor.

source:

bash-3.00# cat sample.c 
#include stdio.h
int main(int argc, char* argv[])
{
printf(Hello word!\n);
return 0;
}

compilation string:

bash-3.00# g++ -m32 -mcpu=v9 sample.c 
bash-3.00# file a.out 
a.out:  ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, 
dynamically linked, not stripped, no debugging information available

configuration of 1st test machine - Debian Testing :
/home/dima# uname -a
Linux T291-2 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
/home/dima# cat /etc/issue
Debian GNU/Linux squeeze/sid

/home/dima# cat /proc/cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Pentium(R) Dual  CPU  E2160  @ 1.80GHz
stepping: 13
cpu MHz : 1799.624
cache size  : 1024 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc 
arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 
xtpr pdcm lahf_lm
bogomips: 3599.24
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
...skipped..
address sizes   : 36 bits physical, 48 bits virtual
power management:

configuration of 2nd test machine - Debian Lenny stable:

d...@debian:~/Desktop/linux-user-test-0.3$ uname -a
Linux debian 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux
d...@debian:~/Desktop/linux-user-test-0.3$ gcc --version
gcc (Debian 4.3.2-1.1) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cpu - intel q6600

configuration of 3rd test machine: vmware image of SLES 11
cat /etc/issue
Welcome to SUSE Linux Enterprise Server 11 (x86_64) - Kernel \r (\l).

cat /proc/cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Xeon(R) CPU

[Qemu-devel] [Bug 597402] Re: qemu does not call unlink() on temp files in snapshot mode

2010-10-01 Thread blueswirl
Does not seem to happen anymore:

strace -etrace=unlink -esignal= -f ./qemu -drive file=/dev/null,snapshot=on
unlink(/tmp/vl.jUbLWz)= 0


** Changed in: qemu
   Status: New = Fix Committed

-- 
qemu does not call unlink() on temp files in snapshot mode
https://bugs.launchpad.net/bugs/597402
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Fix Committed

Bug description:
== overview ==

When booting guests in snapshot mode qemu never calls unlink()
on the files storing changes to the images. This results in large amounts of
disk space being used over time.

This bug seems to have been introduced by qemu git commit 
b6ce07aa83bdee3cfd2610f270a0ce304e78df95

== steps to reproduce ==

1) Boot a guest like so:

qemu -m 512 -drive
file=/scratch/images/mdroth/rhel54_64_base.raw,snapshot=on

== actual results ==

/tmp/vl.* files are created and never unlinked/deleted. for example:

mdr...@illuin:~/dev/kvm/qemu-build$ x86_64-softmmu/qemu-system-x86_64 -m 512 
-drive file=/media/secondary/vm/fc12_64_base.raw,snapshot=on 
[1] 24080

mdr...@illuin:~/dev/kvm/qemu-build$ ls -l /tmp/vl*
-rw--- 1 mdroth mdroth 262144 2010-06-22 14:21 /tmp/vl.tFSAmR

mdr...@illuin:~/dev/kvm/qemu-build$ fuser /tmp/vl*
/tmp/vl.tFSAmR:  24080

== expected results ==

temporary files should immediately be unlink()'ed and not be present in the file
listing.

== system details ==

mdr...@illuin:~/dev/kvm/qemu-build$ uname -a
Linux illuin 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 
x86_64 GNU/Linux

latest commit (cada87c432e3b9cd55869a24055baf2b7bc0b70c) from qemu.git master 
branch:

mdr...@illuin:~/dev/kvm/qemu-build$ x86_64-softmmu/qemu-system-x86_64 --version
QEMU emulator version 0.12.50, Copyright (c) 2003-2008 Fabrice Bellard





[Qemu-devel] [Bug 652293] Re: Linux for SPARC does not work

2010-10-01 Thread blueswirl
** Also affects: openbios-sparc (Debian)
   Importance: Undecided
   Status: New

** Changed in: qemu
   Status: New = Invalid

** Changed in: qemu
 Assignee: (unassigned) = blueswirl (blauwirbel)

-- 
Linux for SPARC does not work
https://bugs.launchpad.net/bugs/652293
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid
Status in “openbios-sparc” package in Debian: New

Bug description:
I tried to use debian for sparc. I downloaded Debain Lenny 5.06 sparc netinst 
(file name: debian-506-sparc-netinst.iso). I tried to boot it by command:
qemu-system-sparc -cdrom debian-506-sparc-netinst.iso -boot d
It printed some messages to screen. The last 2 was:
entry point is 0x4000
Jumping to entry point...
I tried to run it as sparc64 (debian.org sais that debian runs fine on sparc32, 
but i tried):
qemu-system-sparc64 -cdrom debian-506-sparc-netinst.iso -boot d
It loaded SILO. When i press enter or print kernel commandline, it starts 
booting, writes, that it loaded kernel 2.6.26, initrd, and after it i get black 
screen. System does not boot.

I went to google and found that debian lenny can not run on sparc32 (it uses 
sparc64 kernel, but 32-bit userspace). People recomended me to try debian 4. I 
downloaded file debian-40r8-sparc-netinst.iso. But i got the same bug with 
qemu-system-sparc. With sparc64 i did not get black screen.It finished by 
string:
Remapping the kernel... done.

What is it?

QEMU 0.12.5, from debian repositories. i386 and x86-64 emulation works fine.
My computer: Celeron 1.8 Ghz, DDR 1.25 Gb, NVIDIA GeForce 4 MX.
As host i use debian squeeze (kernel updated to 2.6.35).





Re: [Qemu-devel] [Bug 636315] [NEW] configure and build errors on Solaris 10 due to /bin/sh usage

2010-09-14 Thread blueswirl
On Sun, Sep 12, 2010 at 10:02 PM, Andreas Färber andreas.faer...@web.de wrote:
 Am 12.09.2010 um 23:05 schrieb Blue Swirl:

 On Sun, Sep 12, 2010 at 5:58 PM, Andreas Färber andreas.faer...@web.de
 wrote:

 Am 12.09.2010 um 19:47 schrieb Blue Swirl:

       nfields=$((nfields + 1))

 ./tracetool: syntax error at line 53: `nfields=$' unexpected

 That looks like fully standards compliant, so Solaris' /bin/sh is not.
 Can you try what happens with /usr/xpg4/bin/sh?

 Works fine! Must've done something wrong when testing that earlier today.

 configure, create_config and tracetool with your fix are silent when
 /usr/xpg4/bin is in the $PATH.
 If you commit it, we can close this ticket. Thanks for your help, Blue.

Does /usr/xpg4/bin/sh work without the patch?

-- 
configure and build errors on Solaris 10 due to /bin/sh usage
https://bugs.launchpad.net/bugs/636315
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
Running `LANG=C LC_ALL=C ./configure --prefix=... --install=/usr/ucb/install` 
on Solaris 10 amd64 results in the following errors:

./configure: bad substitution
./configure: !: not found
./configure: curl-config: not found
./configure: curl-config: not found

Error: invalid trace backend
Please choose a supported trace backend.


Unfortunately it doesn't print the line numbers of the errors. It must be 
somewhere after the check for `install`.

The first few can be resolved by running `bash ./configure ...` instead. 

The check if trace backend exists hardcodes `sh $source_path/tracetool ...` 
in configure. Replacing sh with bash makes it work.

`gmake` complains Makefile:331: no file name for -include, which is a filter 
for *.d files.
`create_config` gets the 'bad substitution' error as well. Replacing sh with 
bash in rules.mak works.
etc.

To sum it up,
a) there are shell script incompatibilities with Solaris 10's /bin/sh shell, and
b) hardcoding 'sh' in configure or Makefiles seems like a bad idea.

QEMU Git 73d7434279e3905164afd02360eebe4b43c7fa (ESP: fix ESP DMA access...)

$ uname -a
SunOS sonnengoettin 5.10 Generic_142901-03 i86pc i386 i86pc

# No banner output for /bin/sh

$ bash --version
GNU bash, version 3.00.16(1)-release (i386-pc-solaris2.10)
Copyright (C) 2004 Free Software Foundation, Inc.





Re: [Qemu-devel] [Bug 618533] Re: OpenSolaris guest fails to see the Solaris partitions of a physical disk in qemu-kvm-9999 (GIT)

2010-08-28 Thread blueswirl
On Fri, Aug 27, 2010 at 3:57 PM, devsk 618...@bugs.launchpad.net wrote:
 what's the list address? All the lists at the kvm main page are for kvm
 only.

 --
 OpenSolaris guest fails to see the Solaris partitions of a physical disk in 
 qemu-kvm- (GIT)
 https://bugs.launchpad.net/bugs/618533
 You received this bug notification because you are a member of qemu-
 devel-ml, which is subscribed to QEMU.

 Status in QEMU: New

 Bug description:
 # qemu-kvm --version
 QEMU emulator version 0.13.50 (qemu-kvm-devel), Copyright (c) 2003-2008 
 Fabrice Bellard

 The following disk is presented to guest as IDE disk with /dev/sdd as path.

 # fdisk -l /dev/sdd

 Disk /dev/sdd: 750.2 GB, 750156374016 bytes
 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x7f3a03aa

   Device Boot      Start         End      Blocks   Id  System
 /dev/sdd1              63     7887914     3943926   1b  Hidden W95 FAT32
 /dev/sdd2         7887915   980736119   486424102+  83  Linux
 /dev/sdd3   *   980736120  1083150494    51207187+  bf  Solaris
 /dev/sdd4      1083150495  1465144064   190996785    5  Extended
 /dev/sdd5      1083150558  1107746009    12297726   83  Linux
 /dev/sdd6      1107746073  1465144064   178698996    7  HPFS/NTFS

 The prtvtoc output is attached from both VirtualBox and Qemu-KVM. As can be 
 seen in the screenshots, a valid Solaris partition table (which is inside the 
 /dev/sdd3, marked 'bf' in Linux fdisk output) is not seen in Qemu but seen in 
 Virtualbox.

 This makes the guest unbootable in Qemu because the root FS is not found but 
 its bootable in Virtualbox.

Sorry, I missed that this was for qemu-kvm. Anyway, the patch is
probably applicable to QEMU as well and you actually filed the bug to
Qemu.

qemu-devel list information can be found in
http://lists.nongnu.org/mailman/listinfo/qemu-devel

-- 
OpenSolaris guest fails to see the Solaris partitions of a physical disk in 
qemu-kvm- (GIT)
https://bugs.launchpad.net/bugs/618533
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
# qemu-kvm --version
QEMU emulator version 0.13.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice 
Bellard

The following disk is presented to guest as IDE disk with /dev/sdd as path.

# fdisk -l /dev/sdd

Disk /dev/sdd: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7f3a03aa

   Device Boot  Start End  Blocks   Id  System
/dev/sdd1  63 7887914 3943926   1b  Hidden W95 FAT32
/dev/sdd2 7887915   980736119   486424102+  83  Linux
/dev/sdd3   *   980736120  108315049451207187+  bf  Solaris
/dev/sdd4  1083150495  1465144064   1909967855  Extended
/dev/sdd5  1083150558  110774600912297726   83  Linux
/dev/sdd6  1107746073  1465144064   1786989967  HPFS/NTFS

The prtvtoc output is attached from both VirtualBox and Qemu-KVM. As can be 
seen in the screenshots, a valid Solaris partition table (which is inside the 
/dev/sdd3, marked 'bf' in Linux fdisk output) is not seen in Qemu but seen in 
Virtualbox.

This makes the guest unbootable in Qemu because the root FS is not found but 
its bootable in Virtualbox.





[Qemu-devel] [Bug 556346] Re: build errors with GCC-4.2.4-1ubuntu4

2010-06-02 Thread blueswirl
Fixes committed: 98835fe30fa7d50695f037e84f76f9f139c59c7e
and aacf4563878cac2afbbdc9818d810d2a3b075c6a.

** Changed in: qemu
   Status: New = Fix Committed

** Changed in: qemu
 Assignee: (unassigned) = blueswirl (blauwirbel)

-- 
build errors with GCC-4.2.4-1ubuntu4
https://bugs.launchpad.net/bugs/556346
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Fix Committed

Bug description:
When building with the old restrictive GCC of Ubuntu Hardy, there are 4 
warnings in e1000.c and microblaze-dis.c.

Patch is attached.