Custom Query (16363 matches)
Results (1051 - 1053 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #943 | fixed | VBoxManage convertdd creates corrupted images | ||
| Description |
Using VBoxManage convertdd <myimage_of_disk_created_via_dd> output.vdi creates output.vdi with the right size and seemingly some data in there but the culprit may be that the partition table get corrupted. This was an image made via dd from a disk with a single ntfs partition. I could send you the image if needed (2.3G though and my upload is 60k) Regards Alban |
|||
| #944 | fixed | Static disks have problems configuring partitions => Fixed in SVN | ||
| Description |
This is on 64-bit Windows (XP64, Vista64) at least: When using a static disk, during an install the guest cannot properly partition the disk. Have tried Linux (Ubuntu 7.10) and FreeBSD 6.2. Using a Dynamic disc this problem does not occur. Screenshots here: http://forums.virtualbox.org/viewtopic.php?t=3204 |
|||
| #945 | fixed | VM can send but not receive traffic through TAP interface | ||
| Description |
Test procedure:
Observations:
overlord linux # tcpdump -i vbox0 tcpdump: WARNING: vbox0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on vbox0, link-type EN10MB (Ethernet), capture size 96 bytes 00:31:36.417877 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:36.431399 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:38.944662 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:38.963307 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:43.723376 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:43.743677 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:31:52.290219 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:31:52.307821 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:32:08.273038 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:32:08.284300 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548 00:32:41.006979 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:b5:a3:06 (oui Unknown), length 548 00:32:41.025565 IP 192.168.0.1.bootps > 192.168.0.10.bootpc: BOOTP/DHCP, Reply, length 548
Interpretation:
|
|||

