ly but I don't have any MacOS systems handy to
test it against its dhcpd.
Maybe it's a good idea to include it into squeeze-p-u, and it's
definitely nice fix to have for sid. I'll apply the patch to
git later today.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-
when the system is already running) - we dropped udev rules
file and loaded module which created the device in question,
but udevd didn't see the rules file yet. But it should be
ok once udevd is restarted, like happens after reboot.
If it's not it, please show content of /lib/udev/rules.d
e not a good idea, depending on the situation that may
> not be a good idea.
>
> So qemu tries to give you some control over what to do.
>
> Closing this bug as "not a bug".
And ofcourse I forgot to mention. -drive has option onerror=report.
So you can use it.
/mjt
5 does not support booting from USB mass
storage devices. Current git version (after 0.14 release)
has some provisions for that but these are not complete.
It wont be fixed for squeeze for sure.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subje
However
it _is_ already documented, sort of: every guide will tell
you that you shouldn't use user-mode networking to start
with :) Kidding really, it _is_ a valid point.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
el.org or cdn.debian.net in place of
> ftp.us.debian.org above works just fine. So there's specific to the
> nature of the name being resolved.
Again, please verify that _first_ nameserver from your host
/etc/resolv.conf is able to resolve all names.
/mjt
--
To UNSUBSCRIBE, email t
mu-kvm 0.12 and 0.13.
So I still think its redhat kernel bug, for now - preliminary.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-usb
this is enough to trigger the problem. Omitting -usb or using some
other CD image lets it to process.
Now I'm not sure what to do really... ;) I'll try to find some time
to dig into it further.
In any way this is not "important" bug I think, since it triggers on
only on
ogether with
qemu-kvm-0.12, while it is well-tested with 0.5. In particular,
seabios-0.6 introduced native support for virtio block devices,
and for that to work properly, corresponding modifications has
to be done in qemu-kvm too.
Now while we're on it, can you please show the kvm comma
what we learn from this is that qemu-kvm-0.12 fails with
your mona.iso, while 0.13 works. Let's see, I'll post a update
to this later.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t I'm
not aware of any issues about bios. qemu-kvm-0.12 comes with
its own bios installed in /usr/share/kvm/bios.bin, it does not
use bios from /usr/share/seabios.
Thanks.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
11 matches
Mail list logo
