When I try adding a second disk to an HVM domU, I get this when I try to boot: Error: Device 5632 (vbd) could not be connected. Backend device not found. The backend device DOES exist. I''d like to use separate ZFS volumes for the boot disk and data disk on a Windows HVM so I can manage snapshots of either one independently. Is there a limitation on HVM guests to only use a single disk? -- This message posted from opensolaris.org
Chris wrote:> When I try adding a second disk to an HVM domU, I get this when I try to boot: > > Error: Device 5632 (vbd) could not be connected. Backend device not found. > > The backend device DOES exist. I''d like to use separate ZFS volumes for the boot disk and data disk on a Windows HVM so I can manage snapshots of either one independently. Is there a limitation on HVM guests to only use a single disk? >There is no such limitation. What command did you use to add the second disk? Assuming it''s a file, maybe you need to make it writable world-wide... Max
An upgrade to nv101 seems to have solved my problem. -- This message posted from opensolaris.org
Possibly Parallel Threads
- Hanging boot of solaris 11 install image as HVM
- SXCE104, Cannot boot HVM domain
- attaching 2nd vol unsupported?
- How HVM domain distingush ioemu disk and VBD disk
- Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1