This bug has been fixed now https://code.launchpad.net/~tinco-
andringa/vmbuilder/vmbuilder/+merge/242076 has been merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio
This bug has been fixed now https://code.launchpad.net/~tinco-
andringa/vmbuilder/vmbuilder/+merge/242076 has been merged.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
** Changed in: vm-builder (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions
** Changed in: vm-builder (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes
What has Ubuntu Lucid to do with this bug? Isn't it in any version of
Ubuntu that ships with this software?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block
What has Ubuntu Lucid to do with this bug? Isn't it in any version of
Ubuntu that ships with this software?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: vm-builder (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: vm-builder (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Branch linked: lp:tinco-vm-builder/virtio-uuid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions
** Branch linked: lp:tinco-vm-builder/virtio-uuid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions disappear in
KVM/QEMU
Is anyone watching this issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions disappear in
KVM/QEMU
Is anyone watching this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions disappear in
KVM/QEMU (using vmbuilder and
Hi guys,
I'm stuck on this, so I've made a patch. I'm not sure how to test it,
perhaps someone give me some pointers? I tried out this bzr thing and
it's super crazy. I can't find out how to fork and submit a pull
request. I browsed through the commands of bzr and there was some
launchpad stuff
The attachment patch seems to be a patch. If it isn't, please remove
the patch flag from the attachment, remove the patch tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any
Hi guys,
I'm stuck on this, so I've made a patch. I'm not sure how to test it,
perhaps someone give me some pointers? I tried out this bzr thing and
it's super crazy. I can't find out how to fork and submit a pull
request. I browsed through the commands of bzr and there was some
launchpad stuff
The attachment patch seems to be a patch. If it isn't, please remove
the patch flag from the attachment, remove the patch tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any
Yeah, UUID seems like a better idea.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions disappear in
Yeah, UUID seems like a better idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions disappear in
KVM/QEMU (using vmbuilder
I agree with Paul Sladen -- if this used the UUID mechanism it would be
simpler to change. That's also what most of the kvm docs indicate. So
why isn't vmbuilder using it?
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
I agree with Paul Sladen -- if this used the UUID mechanism it would be
simpler to change. That's also what most of the kvm docs indicate. So
why isn't vmbuilder using it?
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
** Also affects: vm-builder (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
** Changed in: vm-builder (Ubuntu Lucid)
Milestone: ubuntu-10.04 = None
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
** Also affects: vm-builder (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
** Changed in: vm-builder (Ubuntu Lucid)
Milestone: ubuntu-10.04 = None
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
Surely the problem here, is that for the standard method of mount-by-
UUID is being overridden?
If mount-by-UUID is in use then it doesn't matter whether a device shows
up as /dev/{sd,hd,hv}*
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder
Surely the problem here, is that for the standard method of mount-by-
UUID is being overridden?
If mount-by-UUID is in use then it doesn't matter whether a device shows
up as /dev/{sd,hd,hv}*
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder
** Changed in: vm-builder (Ubuntu)
Milestone: None = ubuntu-10.04
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
** Changed in: vm-builder (Ubuntu)
Milestone: None = ubuntu-10.04
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
You are right of course, /etc/fstab on the guest contains /dev/sdXY
entries. These get generated by
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned.
After changing all /dev/sdXY to /dev/vdXY I can indeed boot happily
:)
What threw me off was that QEMU did not (and does
** Package changed: libvirt (Ubuntu) = vm-builder (Ubuntu)
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder
You are right of course, /etc/fstab on the guest contains /dev/sdXY
entries. These get generated by
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned.
After changing all /dev/sdXY to /dev/vdXY I can indeed boot happily
:)
What threw me off was that QEMU did not (and does
Thanks for the comment, but how do you figure? I did not change anything
after the fact, I modified the template used for installation and setup
of the guest domain.
First, it seems to depend on the bus type whether the virtual disks are
at all visible to QEMU, as can be seen from the
On Fri, 5 Feb 2010, Andreas Ntaflos wrote:
So I don't think that is the problem here, but I will try again. Thanks
for the comment, again!
I think if you look inside your guest image you will see 'sdaX' in
/etc/fstab. Disks that are presented to the booted system as virtio will
be named
Thanks for the comment, but how do you figure? I did not change anything
after the fact, I modified the template used for installation and setup
of the guest domain.
First, it seems to depend on the bus type whether the virtual disks are
at all visible to QEMU, as can be seen from the
On Fri, 5 Feb 2010, Andreas Ntaflos wrote:
So I don't think that is the problem here, but I will try again. Thanks
for the comment, again!
I think if you look inside your guest image you will see 'sdaX' in
/etc/fstab. Disks that are presented to the booted system as virtio will
be named
** Attachment added: Domain definition for guest foo, using virtio for block
devices
http://launchpadlibrarian.net/38748978/foo.xml
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You
the mountall failed messages fail because there *is* no /dev/sdX* and
your /etc/fstab says to mount them.
You've changed to /dev/vda* , /etc/fstab will need to be updated.
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
** Attachment added: Domain definition for guest foo, using virtio for block
devices
http://launchpadlibrarian.net/38748978/foo.xml
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You
the mountall failed messages fail because there *is* no /dev/sdX* and
your /etc/fstab says to mount them.
You've changed to /dev/vda* , /etc/fstab will need to be updated.
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
37 matches
Mail list logo
