[Qemu-devel] crash (SIGSEGV)

[Qemu-devel] crash (SIGSEGV)

[Alexander Opitz]

Hi,

I'm trying to install from a debian.iso to an hdd image file inside qemu.

starting qemu:

gdb --args /a/qemu/i386-softmmu/qemu -hda /a/disc1/debian-3.0r0.img 
-cdrom/a/disc/debian.iso -boot d 

gdb output:

(gdb) run
Starting program: /a/qemu/i386-softmmu/qemu -hda /a/disc1/debian-3.0r0.img 
-cdro
[Thread debugging using libthread_db enabled]
[New Thread 1077088384 (LWP 23971)]
Connected to host network interface: tun0
Detaching after fork from child process 23975.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1077088384 (LWP 23971)]
0x09a657a0 in ?? ()
(gdb) bt
#0  0x09a657a0 in ?? ()
#1  0x08094b03 in cpu_x86_exec (env1=0x8f333d0) at /a/qemu/cpu-exec.c:545
#2  0x0804dd11 in main_loop () at /a/qemu/vl.c:2463
#3  0x0804eb3b in main (argc=-956097136, argv=0xc4e62240) at /a/qemu/vl.c:3392
(gdb)   


This happens while the debian installer tries to install the debian ground 
system.

If you need more info ... mail me ;)

Greetings Alex//

PS: Why I can't use the latest bios from bochs? If I do so, then it crashs 
with segfault.

Re: [Qemu-devel] crash (SIGSEGV)

[Hetz Ben Hamo]

Alexander Opitz wrote:
> Hi,
> 
> I'm trying to install from a debian.iso to an hdd image file inside qemu.
> 
> starting qemu:
> 
> gdb --args /a/qemu/i386-softmmu/qemu -hda /a/disc1/debian-3.0r0.img 
> -cdrom/a/disc/debian.iso -boot d 

Which version of QEMU do you use? I suggest pulling from CVS or grabbing 
my nightly snapshot for testing..

> PS: Why I can't use the latest bios from bochs? If I do so, then it crashs 
> with segfault.

Is there any reason you're looking to use it? I just looked at their 
"bios" directory in their CVS and there's no really major change 
compared to the QEMU BIOS.. Unless I missed something?

Thanks,
Hetz

Re: [Qemu-devel] crash (SIGSEGV)

[Alexander Opitz]

Am Montag, 4. Oktober 2004 03:14 schrieben Sie:
> Which version of QEMU do you use? I suggest pulling from CVS or grabbing
> my nightly snapshot for testing..

Ups, I forgett to tell ... I'm using latest from cvs :)

> Is there any reason you're looking to use it? I just looked at their
> "bios" directory in their CVS and there's no really major change
> compared to the QEMU BIOS.. Unless I missed something?

I don't know what is more actuall, the bios.diff is against rombios.c,v 1.110 
and latest one from bochs is rombios.c,v 1.119 and that's why I ask.

(Also the debian project seems to have only one bios package and try to use it 
for bochs and qemu).

Greetings Alex//

Re: [Qemu-devel] crash (SIGSEGV)

[Alexander Opitz]

Hi,

this time all worked, I've choose to format the partition ext2 and not 
ext3 ... system is now installed and updated to debian unstable, network 
works ... YEAH :)

But the partition was to small :/ so I msut do it again.

I've the feeling that disc and iso file read/writes are very slow :(


To the bios of bochs. The only adventures of the bios.diff to the latest 1.119 
rombios of bochs is the floppy ... all other thinks from the diff are already 
integrated into latest rombios.c ... but also if I add the floppy thinks to 
the rombios, I've no success. Maybe I will try to downgrade to rombios.c,v 
110 and try to compile and hope I success ... maybe it is also a problem of 
my compile tools setup.

Greetings Alex//

Resizing partitions - was Re: [Qemu-devel] crash (SIGSEGV)

[Brad Campbell]

Alexander  wrote:
> Hi,
> 
> this time all worked, I've choose to format the partition ext2 and not 
> ext3 ... system is now installed and updated to debian unstable, network 
> works ... YEAH :)
> 
> But the partition was to small :/ so I msut do it again.
> 

where your partition file is xx.file

dd if=/dev/zero bs=1M count=1000 >> xx.file (will add an extra gig to the file size)

 From within the VM, booting off a floppy or other image file.

fdisk /dev/xxx and delete then re-create the parition with the same starting block but to fill the 
rest of the partition.

e2resize /dev/xxx (whatever you use).

I did a dodgy by copying my image.

Loading both of them in qemu, expanding the non-mounted second one, then restarting the vm with the 
second one as the root disk.

Schweet Moite!

Save you a full re-install.

(Works for UML's too)

Brad